10.6.4

Stable

February 20, 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: February 20, 2024** ### Improvements * We improved the performance during a consistency check for a mapping document. (Ticket 205772) * We introduced new custom Runtime settings: `ConnectionPoolingTestOnBorrow`, `ConnectionPoolingTestOnCreate`, `ConnectionPoolingTestOnReturn` and `ConnectionPoolingTestWhileIdle`. They are `false` by default and may be set to `true` to validate connections when borrowed from a pool, created or returned to the pool or when the idle connection evictor runs. * We added the custom Runtime setting `com.mendix.storage.s3.ResourceNamePrefix`, which value will be prepended to the key when retrieving or storing files from and to Amazon S3. * We made importing widget modules more resilient by skipping the import of widgets that were referenced from the *package.xml* but which had been previously deleted from the MPK. * We increased the default BCrypt cost for new apps to 12. * We improved microflow, nanoflow, and rule editor performance. ### Fixes * We fixed a [known issue](https://docs.mendix.com/releasenotes/studio-pro/10.6/#ki-expression-editor) where the new expression editor did not work well with non-ASCII characters. (Tickets 205072, 205761, 206502, 206632, 207386, 208264) * We fixed an issue where a **Select** button on a data grid threw an error. (Ticket 203690) * We fixed an issue when an association property is configured with the same data source for selectable objects and source properties. (Ticket 205039) * We fixed an error when a font size in a Document Template had been set to 0. (Ticket 205807) * We fixed an issue where Studio Pro suddenly shut down while using an Expression or XPath editor (text editor control). As a result, the accessibility cursor is not supported by the control anymore. (Ticket 205853) * We fixed an issue where **Send external object** action was failing to update the remote-key mapping when **Refresh in client** was turned off. (Ticket 206073) * We fixed an issue with breaking glyph fonts on some machines. (Ticket 206544, 207012) * We reduced the chance for concurrency issues on scheduled events when server nodes are restarted and still executing scheduled events. (Ticket 206827) * We fixed an issue where a database connection that was closed from outside of the Runtime remained registered as active. (Ticket 207645) * We fixed an issue where an empty module-level theme settings file caused an error. * We fixed an issue in logic editors where dragging objects into and out of loops moved the objects to the wrong place. * We changed the minimum object size in the logic editors. * We fixed the output variable name that the Logic Bot generated for **Create list** and **Retrieve single from database** recommendations. * We fixed an issue where an *Unsupported specification version: 1.5* error was shown if mxbuild was used with the `--generate-sbom` flag. If you still encounter this issue, it may be solved by restarting Studio Pro to re-generate the *vendorlib-sbom.json* file. ### Deprecations * We deprecated the usage of slashes in bucket names for Amazon S3 storage. You can now use the new `com.mendix.storage.s3.ResourceNamePrefix` custom setting which value will be prepended to the key when retrieving or storing files from and to Amazon S3. ### Known Issues * For some activities in the logic editors, the types of variables are shown as **Not set**. This is only a visual bug. (Tickets 205751, 207251) * Workaround: You can switch back to the classic logic editors via **Preferences** > [New Features](https://docs.mendix.com/refguide/preferences-dialog/#new-features). * Studio Pro might crash when using the new expression editor in combination with accessibility tools (for example, enabling the text cursor indicator). * Workaround: You can switch back to the old editor via **Preferences** > [New Features](https://docs.mendix.com/refguide/preferences-dialog/#new-features). * The new expression editor does not work well with non-ASCII characters. * Workaround: You can switch back to the old editor via **Preferences** > [New Features](https://docs.mendix.com/refguide/preferences-dialog/#new-features). * 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*. * In some cases, even if you are already logged in to Studio Pro, you might still need to click **Sign in** under the **MendixChat** tab to make MendixChat available for use. * 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.