10.6.11

Stable

June 26, 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: June 26, 2024** ### Fixes * We fixed a known issue where the workflow’s user task was not passed correctly as a parameter to the user task’s microflow decision method. * We made some performance improvements when checking whether the local running app can be updated without stopping it first. * We fixed an issue where building would fail if the project path contained quotes. ### Known Issues * When using a microflow decision method for a multi-user task in workflows, the `System.WorkflowUserTask` is always `empty`. * Fixed in [10.6.11](https://docs.mendix.com/releasenotes/studio-pro/10.6/#fix-workflow-parameter) and [10.12](https://docs.mendix.com/releasenotes/studio-pro/10.12/#fix-workflow-parameter) * 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.