10.12.7

Stable

October 11, 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: October ____, 2024** ### Improvements * We added support for PostgreSQL 17. * We added the possibility to collect helpful information for support about the current Studio Pro process and overall status of the of process, such as CPU, memory usage, child processes, threads. * We updated the **Show Image** option (for instance, in the page editor) to select the corresponding image in the **Image Collection** that opens. * We added a new setting in **Preferences** > **Deployment** that disables the synchronization of managed Java dependencies. This can be used to start an application even if Gradle synchronization fails, for example in an air-gapped environment. Note that this may result in compilation errors if Java dependencies are missing, and you must handle duplication and version conflicts manually. SBOM generation is not supported when synchronization is disabled. * We now include Java dependencies in exported app and module packages. These are used if Gradle synchronization is disabled. ### Fixes * We fixed [CVE-2023-49069](https://docs.mendix.com/releasenotes/security-advisories/#49069). * We fixed an exception (an **Oops** dialog) that occurred in a data grid when the user released the mouse button over a grid or a tree, such as the App Explorer. (Ticket 221458). * We fixed an issue when trying to filter by an attribute of an associated entity when the association is self-referencing many-to-one. (Ticket 224145) * We fixed an issue where a named user with multiple tabs open containing changes attempted to execute a runtime operation after session expiry. While one tab reloaded correctly on executing the action, the other tabs did not reload and retained invalid read-only change hashes which resulted in invalid hash errors. (Ticket 228140, 228296) * We fixed an issue that made it impossible to start Studio Pro for the first time when there was no internet connection available. * We fixed an issue when you selected an app and the loading spinner stayed visible forever even when loading apps had finished. * We fixed an issue where bottom bar navigation was not working as expected. * We fixed an error that happened when switching tabs in the Published OData service. * We fixed some spurious foreign key constraint violation errors when using the built-in database (HSQLDB) and workflows with multiple threads. * We fixed an issue where an incorrectly configured template (or data) broke page navigation. ### Known Issues * 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. * Fixed in [10.14.0](https://docs.mendix.com/releasenotes/studio-pro/10.14/#fix-marketplace-modules). * 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.