10.6.22

Stable

April 11, 2025

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, 2025** ### Improvements * We mitigated CVE-2024-38374 by upgrading the CycloneDX Gradle plugin to 1.10.0. The CVE does not pose risk for Mendix customers. (Ticket 243005) * We improved the performance of published OData services that use a **Read** microflow. When the client asks to expand associations, the runtime now performs a database query per association, rather than per object. (Ticket 234607) * We now use generated BOM-refs for managed dependencies in the SBOM. - We improved deployment speed for non-progressive web applications. - We made the administration of running application nodes more stable. We improved the logging in this area. This makes the execution of tasks from the queue more reliable. - We now include Java 21 instead of Java 11 in the installer. - New projects will now use Java 21 by default. - We updated the bundled JDK to version 21.0.5.11. ### Fixes * We fixed [CVE-2025-30280](https://docs.mendix.com/releasenotes/security-advisories/#30280). - We fixed an issue in **Message** definitions where custom names were reset on expansion of a node. (Tickets 222597, 227958, 236152, 232930, 240806, 241561, 244349) - We fixed an issue where Chrome incorrectly displayed a prompt to install a progressive web app (PWA) for non-PWA apps. (Ticket 230439) - We fixed an issue where retrieving an external entity with a non-sortable key attribute resulted in an error. (Ticket 236093) - We decreased the chance for database transaction deadlocks when updating the **LastActive** attribute for System.Session instances. (Ticket 240094) - We changed when we send back hash updates for object changes. This should solve the hash conflict errors when running flows in parallel with a microflow that both Read/Write the same object. (Tickets 240118, 240696, 241168) - We fixed an issue where an error was thrown if a change to an object was done after the object had been deleted by another process. (Ticket 240247) - We fixed the navigation profile selection. When using an iPad, it will now correctly use the tablet navigation profile if available. (Ticket 241824) - We upgraded the Netty dependency to 4.1.118. (Ticket 242071) - We fixed a Studio Pro crash which happened when logging a list of strings from a Java action. (Ticket 243124) * We improved the stability of Studio Pro when debugging nanoflows. - We modified how runtime reports errors when a non-existing entity used when instantiating or querying objects. * In the logic editors, we fixed an **Oops** pop-up window that sometimes occurred when deleting a microflow or nanoflow. * We fixed an issue in consumed web services where selecting a WSDL from a network drive that required authentication but did not return a WWW-Authenticate header resulted in an error. * We fixed an issue in consumed OData services where the HTTP response from downloading metadata from a URL was not cleaned up correctly. - We fixed an issue where an unexpected exception occurred in Studio Pro when you close the app while Studio Pro was checking it for consistency errors. - We fixed an issue in the published OData service editor in Studio Pro where showing the list of published enumerations resulted in an unexpected exception. - We install the dotnet runtime x64 on Arm64 computers again, since the Console tools still requires the x64 in this Studio Pro version. We had previously stopped including it, which was the cause of the issue. * We fixed the checkbox **Show inactive threads (wait/park)** in the **Runtime Threads** window of Studio Pro. - We fixed an issue where attempting to convert nanoflow or microflow in the system module resulted in an error. This option is now disabled for the **System** module. * We fixed an issue with updating module roles in the **Module Security** dialog box that occurred after moving a document between modules. ### Deprecations * We have deprecated Java 11 and 17. These versions will not be supported in 10.21 and above. We recommend to update to Java 21 before migrating. ### Breaking Changes * We removed the `PhoneUserAgentRegEx` and `TabletUserAgentRegEx` custom runtime settings as today user agents are no longer enough to identify the type of device. We moved the device type detection to the client which can use more than just the user agent to determine the type of device. ### Known Issues * 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. * Fixed in [10.17.0](https://docs.mendix.com/releasenotes/studio-pro/10.17/#fix-finished-parallel-split). * Importing a module containing workflows makes all running workflow instances incompatible. (Ticket 234084) * Fixed in [10.21.0](https://docs.mendix.com/releasenotes/studio-pro/10.21/#fix-workflow-instances). * There is a positioning error in the logic editors when you are dragging a large element, such as a loop, into a sequence flow, it overlaps with the existing elements. * Fixed in [10.12.12](https://docs.mendix.com/releasenotes/studio-pro/10.12/#fix-positioning-error) and in [10.14.0](https://docs.mendix.com/releasenotes/studio-pro/10.14/#fix-positioning-error). * 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. * Fixed in [10.18.0](https://docs.mendix.com/releasenotes/studio-pro/10.18/#fix-line-endings).