10.6.9

Stable

May 27, 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: May 27, 2024** ### New Features We now support Java 21 in Studio Pro: * You can configure your application to use Java 21 in the **App Settings**. * In Studio Pro Preferences you can configure a different JDK for each supported version of Java. * Targeting Java 21 allows the app to use language constructs and APIs that were introduced with Java 21. We recommend that you upgrade apps and Marketplace modules to Java 21. ### Improvements * We changed the log level of the "tasks cannot be executed anymore due to model changes" message in the task queue from "critical" to "error". (Ticket 199565) * We ensure that the `vendorlib-sbom.json` file does not change when dependencies do not change, reducing the number of git conflicts related to this file. (Ticket 208993) * We have made a couple of small performance improvements to the Logic Bot. * We fixed memory leaks that happened when closing and opening applications in Studio Pro. * We added a Support Tools submenu to the **Help** menu, this submenu contains the following tools (Performance logging, Profiling, and Optimize MPR). * We made some performance improvements when finding usages in protected modules. * We made some performance improvements when finding usages of a module. ### Fixes * We have fixed the tab functionality in the new expression editor. (Ticket 205514) * We fixed an issue in the new expression editor where the cursor was jumping to the end of the expression upon typing. This cursor issue could also lead to unexpected behaviour with IME characters. (Ticket 205514, 216915) * We fixed an issue where an error in the client occurred when a client side expression which used a selection variable was used in a snippet. (Ticket 207899) * We resolved an issue causing files with special characters in their names to download with incorrect file names. (Ticket 213587) * We fixed an issue where disabling a Scheduled Event through Model Options in the Developer Portal would not work. (Ticket 214392, 215703, 215843) * We have fixed an issue where the new expression editor was getting stuck upon selecting a long suggestion in the auto completion popup. * We fixed an issue where, when migrating a column from Float to Decimal, the default value was converted to Float before being inserted, which caused improper rounding to happen. * We fixed an issue where Data Grid 2 did not show data in some columns when different columns were configured with an attribute path using the same association but with different specialization or generalization entities. (Ticket 203959) * We fixed an issue where a pluggable widget with a [selection property](https://docs.mendix.com/apidocs-mxsdk/apidocs/pluggable-widgets-property-types/#selection) linked to a [datasource property](https://docs.mendix.com/apidocs-mxsdk/apidocs/pluggable-widgets-property-types/#datasource), which was not required, resulted in an exception when the datasource was not configured. * We fixed an exception that happened upon closing a non-version-controlled app (after we previously opened a version-controlled app and did not restart Studio Pro). ### 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*. * Disabling Custom Scheduled Events in the **App Settings** > **Configurations** has no effect and they will still run on their scheduled time. Toggling on a disabled Scheduled Event will also have no effect. * Workaround: Making a small change to the model in Studio Pro, such as adding a comment to a microflow, and then redeploying and restarting the app will update the status of the Scheduled Events. * 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.