10.12.2

Stable

August 01, 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: August 1, 2024** ### Improvements - We upgraded the JDBC driver for Microsoft SQL Server to version 12.6.3. If you connect to SQL Server using integrated security in a module such as [Database Connector](https://docs.mendix.com/appstore/modules/database-connector/), you may need to update the JDBC driver in `userlib` as well. - We improved performance when typing in the expression editor. - We added an [`mx show-java-version` command](https://docs.mendix.com/refguide/mx-command-line-tool/app/#show-java-version) to the mx command-line tool. This command shows the configured Java version of the app. ### Fixes - We fixed an issue where *vendorlib-sbom.json* is updated unnecessarily. (Tickets 218152, 222102, 221123, 220419, 219994, 219344, 218992, 218899, 218855, 223095) - We fixed an error in database synchronization which affected setting an existing entity with a decimal attribute as a generalization of another entity. (Ticket 219731) - We fixed an issue where, in applications with both PWA and native profiles, the PWA could potentially attempt and fail to pre-cache a native page if it was reachable through subnanoflows. (Ticket 220165) - We fixed an issue where the Metrics.ApplicationTags configuration value was not used for some of the [built-in metrics](https://docs.mendix.com/refguide/metrics/#7-list-of-metrics). (Ticket 220260) - We fixed an issue in the domain model when dragging an association between two entities did not work when the starting point on the first entity is roughly the same as the ending point on the second entity. (Ticket 222377) - We fixed an issue in the Dojo client where the `mx.data.callNanoflow` API did not return the result from the nanoflow. (Ticket 222682) - We fixed an issue when an error dialog was displayed after opening an app in the Mendix Portal when the user was signed in and there was no Internet connection. - We fixed a memory leak related to running an app. - We fixed an issue where changing an [event action](https://docs.mendix.com/refguide/text-box/#events) or a list view [on click](https://docs.mendix.com/refguide/list-view/#on-click) or [pull down](https://docs.mendix.com/refguide/list-view/#pull-down) action from a microflow to another type of action resulted in an **Oops** dialog. - We fixed an issue where the name of a `userlib` dependency in the SBOM was incorrect. - We fixed an issue in the React client where the page did not load when navigating back from a page that had been opened by a microflow that closed all pages. * We fixed an issue in the External Database Connector where the Date and Time parameter was not working for PostgreSQL. ### 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. * 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. * Studio Pro on Mac loads user settings from the previous version of the application. * When importing Marketplace modules with Studio Pro, their version numbers do not represent the module's version. Instead they mention the current Studio Pro version. This does not affect previously imported Marketplace modules