7.5

5 minutes to read Download PDF Edit

7.5.1

Release date: July 26th, 2017

Download

Atlas-Based Apps

  • When creating a new Atlas-based app from the Desktop Modeler, it’s now also possible to edit the app in the beta version of the Web Modeler. Formerly, this was only possible when the app was created from the Mendix Portal. For details about the Web Modeler, see How-to Build an Employee Directory App and Mendix 7 Atlas Release: Bringing Design Thinking to Low-Code App Development.
  • In 7.5.0, it was not possible to use the Generate page functionality for buttons in the Responsive profile. The Create Page dialog box showed no selectable page templates for this profile. We fixed this.
  • We now provide several form pages that can be used for page generation.

Other Fixes

  • The Map automatically button that generates domain model entities now always generates a mapping parameter in export mappings.

Known Issues

  • For Atlas-based apps, it is not possible to use the Generate page functionality for buttons in the Tablet and Phone profiles. The Create Page dialog box shows no selectable page templates for these profiles.
  • In some situations, an object associated to another object cannot be committed during the execution of a before/after commit event, resulting in an error such as “Object of type ‘MyModule.MyEntity’ with guid ‘12345’ cannot be updated, as it does not exist anymore.” For example, consider two new objects A and B, wherein A (parent) is associated with B (child) and A has a before- or after-commit event. In this event, B will be changed and committed. If you then commit A, B will be marked as ‘autocommitting’. Because of this, committing B in the before- or after-commit event of A will fail, as it expects A to already exist in the database, which is not yet the case. (Tickets 59099, 59288)
    • Workaround 1 – don’t commit (a child) in a before-commit event, as the child will already be autocommitted by Mendix.
    • Workaround 2 – commit the child object before committing the parent object.
  • Some users working on Windows 7 and 8.1 might experience issues during installation of the .NET Framework bundled with the Modeler installer. Installing .NET Framework from the official Microsoft website resolves these issues.
  • Disallowing concurrent execution of microflows in a multi-node cluster environment does not work. The feature still works on a single node.

7.5.0

Release date: July 12th, 2017

Download

Export Mappings

We introduced a new way of getting Mendix objects in export mappings: from parameter.

This has always been the default (unseen) value for the root element, but it can now be chosen anywhere in the mapping. As a result, the input to an export mapping may be a list of Mendix objects (whereas before, it always had to be a single Mendix object).

Fixes

  • We fixed the ability to use a client certificate for a web or REST service that has a server certificate signed by a non-standard authority. (Tickets 52427, 52937)
  • We fixed the default sort order for drop-down search fields in grids to be the selected attribute path. (Ticket 53810)
  • We fixed the issue that occurred when a logout from a hybrid app would be stuck with a loader.
  • We fixed the exception that occurred during the creation of a web service user when project security was disabled. (Ticket 53128)
  • We now populate the Size attribute of file documents without commit events. (Ticket 54099)
  • We fixed the issue when a redirect from a normal index page to index-rtl (for right-to-left languages) failed.
  • We fixed the life cycle for widgets inside conditionally hidden containers (they were not being destroyed properly, which led to performance issues). (Ticket 53719)
  • When a conditionally visible widget was re-displayed, it displayed stale values. We fixed this for you. (Tickets 52466, 53719)
  • We fixed downloading FileDocuments (images) from S3, which also broke Mendix Cloud V4. (Ticket 54304)

Known Issues

  • The Mendix Web Modeler is not enabled when you create an Atlas UI-based app in the Mendix Desktop Modeler.
  • For Atlas-based apps, it is not possible to use the Generate page functionality for buttons. The Create Page dialog box shows no selectable page templates for these profiles.
  • In some situations, an object associated to another object cannot be committed during the execution of a before/after commit event, resulting in an error such as “Object of type ‘MyModule.MyEntity’ with guid ‘12345’ cannot be updated, as it does not exist anymore.” For example, consider two new objects A and B, wherein A (parent) is associated with B (child) and A has a before- or after-commit event. In this event, B will be changed and committed. If you then commit A, B will be marked as ‘autocommitting’. Because of this, committing B in the before- or after-commit event of A will fail, as it expects A to already exist in the database, which is not yet the case. (Tickets 59099, 59288)
    • Workaround 1 – don’t commit (a child) in a before-commit event, as the child will already be autocommitted by Mendix.
    • Workaround 2 – commit the child object before committing the parent object.
  • Some users working on Windows 7 and 8.1 might experience issues during installation of the .NET Framework bundled with the Modeler installer. Installing .NET Framework from the official Microsoft website resolves these issues.
  • Disallowing concurrent execution of microflows in a multi-node cluster environment does not work. The feature still works on a single node.