10.12.3

Stable

August 13, 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 13, 2024** ### Improvements * We added `mx.exe`, `mxbuild.exe`, `mxutil.exe`, `MprTool.exe`, and `MendixConsoleLog.exe` tools to the Windows x64 and ARM64 portable installers. (Ticket 202611) * We fixed several memory leaks that happened when closing the **Open App** dialog box. * We added a link to the documentation for the translation generator experimental feature (that can be enabled in the **New Features** tab). * We improved the performance of retrieving many objects for certain data sources, such as a microflow data source. ### Fixes * We fixed the issues in the **Open App** dialog box that sometimes a Team Server app was not be listed, or that sometimes the application icon displayed the default image instead of the customized image. (Tickets 205781, 205798) * We fixed listening between widgets to continue after hiding the selecting widget, such as data grid 2, with conditional visibility. (Ticket 206642) * We fixed an issue in the Dojo client that occurred when calling a microflow that closed all pages before showing a new page. (Ticket 219072) * We fixed an issue where for online apps, anonymous users with an invalid session did not trigger an application reload, which led to unexpected client behavior. (Tickets 219683, 223328, 224791, 225004) * We fixed an issue where Studio Pro crashed when searching for unused items or when searching for externally used microflows. (Ticket 219388) * We fixed an issue where the runtime hung during start up due to an issue with microflow optimization. (Ticket 221620) * We fixed an issue where, in some cases, a microflow or nanoflow call triggered a refresh on an already closed page resulting in a client error. (Ticket 222015) * We fixed an issue where the runtime failed to start with a NullPointerException due to an issue with microflow optimization. (Ticket 223394) * We fixed an issue when an application did not load in Studio Pro if it had run configuration with an empty name. (Ticket 224152) * We fixed an issue where an on-change action for a reference selector or an input reference set selector configured with a microflow or a nanoflow did not give a consistency error when the parameter mapping needed to be refreshed. (Ticket 224223) * We fixed an issue where a microflow database retrieve action with range "first" took longer to run than a custom range with limit of 1. (Ticket 224668) * We fixed an issue where selecting an argument to fix the consistency error "no argument selected for parameter {Name} and no default is available" resulted in an **Oops** dialog box. ### 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.