10.6.7

Stable

April 11, 2024

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: April 11, 2024** ### New Features #### Java 17 In a first step towards Java 21 support, we have made the following changes: * We added the option to select between Java 11 and 17 in the app Runtime settings. * Targeting Java 17 allows the app to use language constructs and APIs that were introduced with Java 17. * If you choose to run on JDK 17 you should not have to update your apps. If you have any unexpected issues, please revert to Java 11 if possible and wait for Java 21 support to be introduced. Mendix recommends you keep older apps and Marketplace modules on Java 11 for now, and upgrade them to Java 21 when that version is supported in a future Mendix 10 release. Note that new apps are currently still configured to target Java 11. ### Fixes * We fixed an issue when versioned MDA creation downloaded an app from the server (which took a long time) instead of using a local clone. (Ticket 202414) * We fixed an issue where you were not redirected to the page you were initially trying to access after loging in via a modeled login page. (Tickets 205091, 212002) * We fixed an issue which occurred when a conditional visibility or editability was configured with an attribute which was not of Boolean or enumeration type. (Ticket 205450) * We fixed an issue where the **Status** bar about the merge did not appear after the solution upgrade, so it was impossible to commit without a Studio Pro restart. (Ticket 206204) * We fixed an issue when the application closed when an entry to the entities grid in the OData service was added. (Tickets 210516, 211779) * We fixed an issue when the selection dialog where you can choose a pane (**Active Tools Windows** and **Active Files** dialog box) did not work on Windows if a microflow, nanoflow, rules or workflow editor was opened. (Ticket 211576) * We fixed an issue where changing the association of an association property in a pluggable widget, for example, a Combo box, threw an error. This occurred when the current selected association was referring to a snippet parameter which was no longer available or referring to a data view no longer in scope. (Ticket 212822) * We changed the default setting of the Best Practice bot to disabled by default as a workaround for performance issues. The user can change this setting in the current session, but the bot will be disabled again in the next startup of Studio Pro. * We fixed an issue where importing an OData contract containing an action referencing an entity type as a parameter caused an error. ### Deprecations * We will drop support for MariaDB 10.4 after July 1 2024, as the vendor has announced the end of support for that version. ### Known Issues * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](https://docs.mendix.com/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](https://docs.mendix.com/refguide/version-control-menu/#show-changes) dialog box. * Workaround: For details, see [this section](https://docs.mendix.com/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*. * A finished parallel split path that is removed from a running workflow instance wrongly leads to a versioning conflict. Please note that "path" was called "branch" in earlier versions.