9.11

Last modified: February 22, 2024

9.11.1

Release date: March 10, 2022

Go to Marketplace

Fixes

  • We fixed a known issue for expression editors. (Tickets 135420, 143395, 143436, 143466, 143474, 143536, 143608, 143758, 143760, 143925)

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)
  • When you double-click a multi-column tree (for example, in the Debug Windows > Variables pane), the grid view does not select the line (except if clicked in the first column), which makes it hard to copy the variable value.
  • The stories shown in the Related stories tab in the Commit dialog box are not filtered by their completed status. Their text is also wrapped and aligned incorrectly. Finally, double-clicking a story in the Stories pane does not show the Story Details pop-up window with the story information.

9.11.0

Release date: February 23, 2022

Go to Marketplace

New Features

  • We added the option to enable Dark mode preview to the New features tab in Preferences. Note that not all screens support dark mode yet, and some parts of Studio Pro can be displayed in light mode when dark mode is enabled.

  • In published OData resources, you can now override the default behavior of the update capability by specifying a microflow. You can use the Validation feedback activity to report custom validation errors in that microflow, for example.

Improvements

  • We fixed CVE-2022-27241.
  • We improved the reaction time of an idle task queue.
  • We added the new MxAssist Logic Bot best practice MXP013 – Negating XPaths in Access Rules.
  • We prioritized the Check if object exists decision recommendation after the retrieve-object operation in the MxAssist Logic Bot menu.
  • We improved the text input focus behavior in native apps. Previously, tapping outside the input committed the value but did not blur the input or call the on-leave event. In some cases (for example, when the input was part of a form wrapped in a scroll view), the input could retake focus from any other element the user might have tapped, triggering unexpected platform-dependent behavior. From now on, tapping outside the input will trigger an on-blur event on the native component and trigger the on-leave event. This allows for more coherent platform-independent behavior when a text input is blurred by tapping outside of it. (Ticket 140065)
  • We added support to autocomplete XPath and OQL with the Tab key.
  • We improved the error message that was shown when trying to use a Commit object activity on an external object. A suggestion is added to use the Send external object activity instead, whenever the external entity allows for updates.
  • We added a new setting to specify the BCrypt cost of the BCrypt hash algorithm. This can be a value from 10 (the default) to 30.
  • We added the possibility to specify the BCrypt cost when configuring the HashAlgorithm via a custom setting. This will override the value from the model. To do this, use the value BCRYPT:cost for the setting HashAlgorithm, where cost can be a value from 10 to 30. If you only specify the value BCRYPT, a default cost value will be used.
  • When user tasks are opened they are now assigned automatically .
  • User tasks can only be completed by the person who is assigned to the task.
  • We added a checkbox in the user targeting section of a workflow user task that enables automatically assigning a user task when a single user is targeted. For more information, see the Auto Assign When Result Is One User section in User Task.

Fixes

  • We fixed a known issue where you could not copy, paste, or delete using keyboard shortcuts in the Properties pane. (Tickets 126003, 139441, 141303)
  • We fixed an issue where the target namespace in XML schema import was not stored in the app, resulting in the failure of XML validation during import and export mappings in Mendix Runtime. (Ticket 123183)
  • We fixed an issue in consumed OData services for XPaths of external entities. XPaths that specified more than one filter on the same associated entity generated the wrong OData query. The result was that the XPath returned more objects than expected. (Ticket 129497)
  • We fixed an issue where the REST Service dialog box shifted upwards when adding a new resource. (Ticket 130238)
  • We fixed an issue where synchronizing objects in an offline-first progressive web app failed along with an “Autocommitted objects detected at end of transaction for long-lived user session” message that was logged. (Tickets 133154, 136135, 137319)
  • We fixed sorting by multiple attributes in an Excel export of the data grid. (Ticket 136239)
  • We fixed an issue where selecting the bottom item in a tree led to selecting a wrong item due to auto-scroll behavior. (Ticket 136374)
  • We fixed an issue with retrieving a binary entity that has a binary attribute. Now, we can better differentiate between a binary OData property and the binary attribute that represents the stream. (Ticket 136937)
  • 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 an issue where changed objects that had a reference to a system attribute were not garbage-collected when no longer in use. (Ticket 138167)
  • We fixed an issue where documentation generation crashed if there was a cross-association in the app. (Tickets 138637, 139672, 140523, 140714, 141072, 141202, 141636).
  • We fixed an issue where you could not type a space in a text box widget wrapped by a container widget with an on-click event. (Ticket 139090)
  • We fixed an issue where a trial license warning was issued when call-home licensing was configured. (Ticket 140289)
  • We fixed an issue in the page editor where an error was shown when changing the layout type of a page to a type for which there are no layouts. (Ticket 140450)
  • We fixed an issue where blocked users were unblocked too quickly. (Ticket 140549)
  • Refreshing a parameter mapping for a Java or JavaScript call action resulted in an exception. This has been fixed. (Ticket 141112)
  • We fixed an issue for published OData services where navigating via an association threw an exception when the entity was not the owner of that association. (Ticket 141357)
  • We fixed an issue where Studio Pro became unresponsive if compiling the app’s theme never finished.
  • We fixed a bug that allowed for setting null values to attributes with the Can be empty box cleared while performing an OData PATCH request.
  • We fixed a bug where the validation for creating branches in Subversion apps was not being called.
  • We fixed an issue where the context menu in the microflow editor to publish the microflow as a web service operation asked for a microflow to be selected rather than asking for a web service to be selected.
  • We fixed the missing Content-Type header in HTTP requests performed by the Send external object activity.
  • We made the Create Variable dialog box resizable.
  • We fixed an issue where a double-click on the vertical scroll bar of a tree led to activating the selected item.
  • We fixed an issue where the passwords of demo users did not update when changing the password policy.
  • We fixed a bug that caused an error when trying to publish an entity as an OData resource while including system members owner or changedBy as attributes. We also made sure these system attributes are listed in NonUpdatable(Navigation)Properties in the service metadata XML.
  • We fixed an issue in updatable published OData resources for exposed system members. Now, these members are properly listed in the NonUpdatable(Navigation)Properties in the metadata, and the runtime gives a clear error message when a client attempts to update them.
  • We fixed an issue in the Call REST service activity where the data entered for a custom request template disappeared.
  • We fixed an issue where a pluggable widget data source having XPath-based constraints where a member did not have read access resulted in an error.
  • We fixed an issue with the tab container where its content was not updating upon switching tabs with visibility constraints.

Breaking Changes

  • The FeedbackHelper class now throws an exception when trying to open a form that does not exist.

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)
  • When you double-click a multi-column tree (for example, in the Debug Windows > Variables pane), the grid view does not select the line (except if clicked in the first column), which makes it hard to copy the variable value.
  • The stories shown in the Related stories tab in the Commit dialog box are not filtered by their completed status. Their text is also wrapped and aligned incorrectly. Finally, double-clicking a story in the Stories pane does not show the Story Details pop-up window with the story information.
  • In expression editors, an expression displayed as valid might be interpreted as invalid later (for example, upon clicking OK on the Edit Change Item dialog box, the grid in the Change Object dialog box that was initially opened from a microflow object marks the valid expression as invalid, accompanied with an error icon in the grid). This affects the user data consisting of this expression field (which is saved into storage with an invalid escaped character, causing the expression field to be interpreted as an invalid one even when restarting Studio Pro). In addition, the auto-completion list pop-up window of a text editor might display no suggestions or incorrect suggestions as hints for auto-completing an expression.