8.18.16

Stable

February 21, 2022

Mendix Studio Pro is our low-code IDE for professional developers. It's a powerful visual model-driven development environment to build apps on the Mendix Platform. With Studio Pro you can easily create, change, integrate, test and deploy your applications, all in one place. Moreover, you can manage branch lines and security as well as extend your app with custom code using the built-in editors. Click 'Download Studio Pro' to get the installer for free (Windows OS required*). Learn more about the installation and the Studio Pro capabilities in our documentation. Not a professional developer? Learn How Mendix supports different developer profiles .Before installing, please read the Release Notes to learn about improvements, bug fixes, backwards compatibility, breaking changes and known issues. *If you are using a Mac, check out these instructions first.

Release Notes - **Release date: February 21st, 2022** ### Improvements * We prioritized the **Check if object exists** decision recommendation after the retrieve-object operation in the [MxAssist Logic Bot](https://docs.mendix.com/refguide8/mx-assist-studio-pro) menu. * MxAssist Logic Bot now always shows a parameterized list for the **Calculate from a list** menu item. * We added the possibility to specify the BCrypt cost when configuring the hash algorithm via a custom setting. 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. * We changed the way [dangling references](https://docs.mendix.com/refguide8/offline-first#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. ### Fixes * We upgraded the Cloud Foundry client (`mx-cf-client`) by updating Apache Log4j libraries to 2.17.1 to address [CVE-2021-45105](https://cert-portal.siemens.com/productcert/pdf/ssa-501673.pdf) and [CVE-2021-44832](https://cert-portal.siemens.com/productcert/pdf/ssa-784507.pdf). * We fixed an issue where the target namespace in [XML schema import](https://docs.mendix.com/refguide8/xml-schema-support) was not stored in the Mendix app, resulting in the failure of XML validation during import and export mappings in Mendix Runtime. (Ticket 123183) * 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 fixed an issue where client certificates with empty passwords could not be used. (Ticket 137950) * We fixed a bug with the [Auto-synchronize](https://docs.mendix.com/refguide8/on-click-event#save-changes) 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](https://docs.mendix.com/refguide8/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 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 in MxAssist Logic Bot where the [Microflow call](https://docs.mendix.com/refguide8/microflow-call) activity could not be inserted if the exposed microflow existed in the app. * We fixed an issue where MxAssist Logic Bot generateed an incorrect aggregate action for the calculate maximum and calculate minimum suggestions. * We fixed an issue where the MxAssist Logic bar toggle was shown for non-editable microflows. * We fixed an issue where a change inside a document did not show up in the the updated [Find Usages](https://docs.mendix.com/refguide8/find-and-find-advanced#find-usages) results until another change occurred or the app was reopened. ### Breaking Changes * When accessing the contents of file documents, access rules on the **Contents** attribute are now checked instead of relying entity access alone. ### Known Issues * When you update a [consumed OData service](https://docs.mendix.com/refguide8/consumed-odata-service) with a new version from [Mendix Data Hub](https://docs.mendix.com/data-hub/) but close the document without saving, the blue arrow icon will no longer be shown to notify you about the available update for that service. * Workaround: Closing your app and opening it again fixes this issue.