9.10

Last modified: February 22, 2024

9.10.4

Release date: April 1, 2022

Go to Marketplace

Fixes

  • We fixed a NullPointerException during startup that occurred after renaming a module with an external entity that was created before Studio Pro 9.6.3. (Ticket 142150)

Known Issues

  • There is a known issue for the scenario where there are multiple instances of the same identical object (meaning, with the same ID) assigned to different microflow variables, this object has a one-to-one association to another entity, and no changes have been made to the associated object. When you then set the association to the same value, only a single microflow variable points correctly to the new association, and the other variables have an empty association. (Ticket 168024)
  • In the Properties pane, you cannot copy, paste, or delete using keyboard shortcuts.

9.10.3

Release date: March 25, 2022

Go to Marketplace

Fixes

  • We fixed an issue that occurred with the document export of a dynamic label when the Render XHTML option was enabled. (Tickets 144111, 141843, 142237, 142342, 142378)

Known Issues

  • There is a known issue for the scenario where there are multiple instances of the same identical object (meaning, with the same ID) assigned to different microflow variables, this object has a one-to-one association to another entity, and no changes have been made to the associated object. When you then set the association to the same value, only a single microflow variable points correctly to the new association, and the other variables have an empty association. (Ticket 168024)
  • In the Properties pane, you cannot copy, paste, or delete using keyboard shortcuts.

9.10.2

Release date: February 24, 2022

Go to Marketplace

Improvements

  • We now use statement parameters when querying for associated objects and specializations.

Known Issues

  • There is a known issue for the scenario where there are multiple instances of the same identical object (meaning, with the same ID) assigned to different microflow variables, this object has a one-to-one association to another entity, and no changes have been made to the associated object. When you then set the association to the same value, only a single microflow variable points correctly to the new association, and the other variables have an empty association. (Ticket 168024)
  • In the Properties pane, you cannot copy, paste, or delete using keyboard shortcuts.

9.10.1

Release date: February 2, 2022

Go to Marketplace

Fixes

  • We fixed a known issue where styling file changes did not trigger a recompilation of the app styling anymore.
  • We applied a fix to prevent an “Oops” (exception) pop-up window from appearing upon clicking the Check All and Uncheck All buttons in a grid’s toolbar.

Known Issues

  • There is a known issue for the scenario where there are multiple instances of the same identical object (meaning, with the same ID) assigned to different microflow variables, this object has a one-to-one association to another entity, and no changes have been made to the associated object. When you then set the association to the same value, only a single microflow variable points correctly to the new association, and the other variables have an empty association. (Ticket 168024)
  • In the Properties pane, you cannot copy, paste, or delete using keyboard shortcuts.

9.10.0

Release date: January 25, 2022

Go to Marketplace

New Features

  • We added support for an automatic retry on task queue tasks in Studio Pro.
  • We added the ability to set the platform for a Javascript action. This allows you to create JavaScript actions specific to web or native applications.
  • The merge/port fix feature has now been implemented for Git apps, and it is available available via Version Control > Merge Changes Here > Port Fix.
  • Workflows are no longer in beta in Studio Pro, which means the workflow functionality is now supported and can be deployed to production environments.
  • We added a new microflow activity Retrieve Workflow Context to retrieve the selected workflow context object.

Improvements

Data Source Variable Improvements

When building more complex UIs, it is common to have nested widgets depending on objects shown in the outer widgets (for example, when only showing the order lines of a current order). XPath source can already express some of these dependencies with the help of entity path or the [%CurrentObject%] token.

With this release, we are making this functionality more simple and powerful. From now on, XPath sources of a list view widget, Data Grid 2 widget, and many other widgets have access to the same variables as page expressions! That means XPath constraints can refer to the objects of all surrounding data widgets as well as to their attributes. For example, your list view can show all Module.Kittens satisfying the [Cuteness > $ownerDataView/CutenessThreshold] constraint. Such a list view will be automatically updated whenever the mentioned CutenessThreshold is changed. This makes creating XPath constraints easier and more powerful while reducing the need for microflow- or nanoflow-based sources. For more information, see the XPath Constraint section of XPath Source.

Other Improvements

  • We added Finished and Duration attributes to System.ProcessedTaskQueue that capture the duration of the task’s execution.
  • We added the new MxAssist Performance Bot best practice MXP012 for a repeatedly committed variable in a microflow.
  • We added a check command to the mx tool to check your app for errors, warnings, and deprecations.
  • We added a name check on metrics that are created from a microflow or through the Java API.
  • We added the five most common widgets used when editing pages, page templates, snippets, and building blocks to the top toolbar.
  • We changed the way dangling references are handled during the synchronization process. A dangling reference error can occur when trying to synchronize a committed object that is associated with an uncommitted object. Synchronization used to be prevented from starting if the set of objects to be synchronized contained an object with a dangling reference, and an error message was then shown on the device. Now, synchronization is not stopped when such an error occurs. Instead, all objects are synchronized except ones with dangling references, for which System.SynchronizationError records are created in the runtime database that contain the data of the uncommitted objects.
  • We upgraded the Microsoft.OData.Edm library to version 7.9.4.

Fixes

  • We upgraded the Cloud Foundry client (mx-cf-client) by updating Apache Log4j libraries to 2.17.1 to address CVE-2021-45105 and CVE-2021-44832.
  • We fixed an issue that occurred with an import mapping that was not committed when the mapping method was Find by key and the child objects could not be retrieved by association. (Ticket 126464)
  • We added support for the Kazakh language. (Ticket 130166)
  • We fixed an issue where re-rendering a widgets property linked to the datasource of a pluggable widget no longer rendered its contents properly. (Tickets 132842, 134061)
  • We fixed an issue where buttons from the Save Changes pop-up window went off-screen if there were a lot of unsaved changes. (Ticket 134136)
  • We fixed an issue where user credentials containing spaces caused unexpected failures when committing changes for Git private server apps. (Ticket 136237)
  • We fixed the autocomplete pop-up window that got stuck upon closing the text editor (for example, for an XPath constraint). Now, this window is closed once the text editor loses focus. (Tickets 136553, 137368)
  • We fixed an issue where setting multiple entity access rules at the same time resulted in an error where no access rights were defined. (Ticket 136705)
  • We fixed an issue that caused the Workflow Engine to hang in a parallel split with huge workflow definitions. (Ticket 137269)
  • We fixed a NullPointerException that occurred when retrieving data from an external entity after an app restart. (Ticket 137565)
  • We fixed an issue where client certificates with empty passwords could not be used. (Ticket 137950)
  • We fixed an issue where changes to an app theme with many files were no longer automatically reloaded in the client. (Ticket 137980)
  • We fixed a bug with the Auto-synchronize option in online profiles that caused a crash when the action was used. (Ticket 138115)
  • We fixed a bug where deployment failed when a List operation activity with a sort operation was used in a nanoflow. This bug occurred when the list was sorted based on an attribute defined in one of the generalizations of the sorted entity. (Ticket 138310)
  • We fixed an issue where switching between tab pages with the Refresh on show property set to Yes did not display its contents correctly. (Ticket 139078)
  • We fixed an issue that occurred with a sort order with more than four attributes in XPath queries. (Ticket 141117)
  • We fixed an issue where a change inside a document did not show up in the updated Find Usages results until another change occurred or the app was reopened.
  • We fixed an issue in the domain model mapping wizard where web services in Marketplace modules could not be selected.
  • We fixed an issue in published OData services that occurred while generating metadata XML. The Name property in the EntityContainer section can no longer contain a slash (/).
  • We fixed a bug that allowed for setting null values on attributes with the Can be empty option cleared while performing an OData PATCH request.
  • We fixed an issue that allowed for attempting to export the metadata XML of a published OData service when related domain model entities had been changed or removed, which in turn threw an error.
  • We fixed an issue that prevented a one-to-one navigational property from being updated from the child side in a published OData service.
  • We fixed an issue where the Mendix Runtime returned the HTTP status code 500 when an invalid entity ID was provided as a new value for a single-valued navigational property in an OData PATCH request.
  • We fixed a backward-compatibility issue where a native mobile app made with a version below 9.4.0 did not start up when connecting to Mendix Runtime version 9.4.0 or above.
  • We fixed an issue in the client-server synchronization protocol where the rollback values of related objects were not always communicated back to the browser when an object was deleted, and as a consequence, more data was updated in the browser cache.
  • We fixed an issue with native mobile apps that prevented an app from starting when a user had unsynchronized changes and was implicitly logged out. In such a case, it was possible for startup synchronization to fail to complete due to user access rights with no actionable mitigation path.
  • We fixed an issue where calling microflows from offline-first apps failed with an error logged on the server with the following message: “invalid jsonrequest jsonobject[“guid”] is not a long”.
  • We fixed an issue in MxAssist Logic Bot where the Microflow call action could not be inserted if the exposed microflow existed in the app.
  • We fixed an issue that occurred when a module was at the app level and the user received an error when trying to update the access rules.
  • We fixed an issue where the Branch Line Manager closed when an empty area was clicked and the Open App dialog box froze.
  • We fixed a bug where the validation for creating branches in Subversion apps was not being called.
  • We fixed an issue where Studio Pro became unresponsive if compiling the app’s theme never finished.
  • We fixed a small visual issue that occurred while rendering context menu items.

Breaking Changes

Modifications to the Workflow Data Model

We introduced workflows as a beta feature in Studio Pro 9.0 and have received great feedback from our community since then. You were eager to test it out and provide us with your point of view on how to further improve the functionality, and we introduce improvements in this release.

The following changes are introduced to the System module:

  • Tasks do not require the WorkflowUserTask entity specialization anymore compared to 9.6-9.9
  • Workflows do not require the Workflow entity specialization anymore compared to 9.6-9.9
  • The WorkflowUserTask.Reason attribute is removed
  • Changes are made to the WorkflowUserTaskState enumeration
  • After a workflow user task is completed it is automatically deleted from System.WorkflowUserTask
  • Entity access rules are changed for WorkflowUserTask and Workflow

For more information on how to migrate the app with the workflow functionality, see Migrating Workflow Apps.

Other Breaking Changes

  • When accessing the contents of file documents, access rules on the Contents attribute are now checked instead of relying on entity access alone.

Known Issues

  • There is a known issue for the scenario where there are multiple instances of the same identical object (meaning, with the same ID) assigned to different microflow variables, this object has a one-to-one association to another entity, and no changes have been made to the associated object. When you then set the association to the same value, only a single microflow variable points correctly to the new association, and the other variables have an empty association. (Ticket 168024)
  • In the Properties pane, you cannot copy, paste, or delete using keyboard shortcuts.
  • The auto-compilation of app styling (when changing styling files while running your app locally) does not work.