10.12.4

Stable

August 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: August 27, 2024** ### Improvements - We improved error messages for connection errors when an action or a data source is triggered. (Ticket 218338) - We improved the [Download from Version Control Server](https://docs.mendix.com/refguide/download-from-version-control-dialog/) dialog box to provide much more information about clone process progress. - We updated the system to store log files for up to 30 days, compared to the previous duration of seven days. - We updated the Oracle .Net Library to 23.5.1 to fix the TAF exception. (Ticket 225454) ### Fixes - We fixed an issue where attribute updates were being triggered before any associations were updated. (Ticket 193881) - We fixed an issue where cached session data was retained even after a new user logged in to offline applications. Now, the cached session data is cleared upon each login. (Ticket 201728) - We fixed bundling issues in large apps using the React client. (Ticket 221389) - We fixed an issue where an **Oops** dialog box was shown when opening the **Edit Datasource** dialog box for Data grid 2 after editing an expression, e.g. when editing the expression for the **Option caption** of the [association filter](https://docs.mendix.com/appstore/modules/data-grid-2/#association-filter). - We fixed an issue that showed an **Oops** dialog box when switching a template parameter from an attribute to an expression if the attribute no longer existed in the domain model. - We fixed an issue where Maia Chat threw an error when receiving references that were not known beforehand. - When debugging in the logic editors, clicking a microflow in the **Debugger** pane did not always work. This is changed to double-click to make it work reliably. - We fixed the rebase issue that occurred when there was no *user.name* and *user.email* set in *.gitconfig*. - We fixed several memory leaks that happened when closing the Domain model editor. - We fixed how the commits with time offsets are handled in the **History** dialog box. - We fixed an issue with the External Database Connector where the app broke due to mismatched capitalization for a parameter name. (Ticket 223739) ### 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.