9.24.17

Stable

March 14, 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: March 14, 2024** ### Improvements * We upgraded Swagger UI from 4.10.3 to 5.11.7. The runtime uses this to show and interact with the OpenAPI documents of published OData services and published REST services. (Tickets 208761, 208854) * We added the `com.mendix.core.ScheduledEventsCleanupBatchSize` and `com.mendix.core.ProcessedTasksCleanupBatchSize` runtime settings to configure the batch size for the periodic cleanup of `ScheduledEventInformation` and `ProcessedTasks`. ### Fixes * We fixed an issue where a concurrency error happened when retrieving a session while optimistic locking was enabled. (Tickets 183769, 198138) * We fixed a scenario when multiple sign-in dialogs were displayed after leaving Studio Pro running without any user interaction or working offline without any sign-in related user actions. (Ticket 205784) * We fixed an issue where restarting the leader node while follower nodes were still executing scheduled events caused the leader node to fail startup. (Ticket 206827) * We fixed an issue where custom content in pluggable widgets, e.g. Data grid 2 or selectable objects for the Combo box, were including the objects of the data source in **Save changes** and **Cancel changes** actions, even when it was only used for display. (Ticket 207911) * We improved the memory consumption in Studio Pro by resolving a memory leak caused by checkable menu items. (Ticket 207357) * We fixed an issue where importing a JSON string with a length greater than 20000000 resulted in a runtime exception. We added the `mapping.import.MaxJsonReadingLength` runtime setting to manually configure the maximum length of a JSON string to resolve this issue. (Tickets 208462, 211077) * We fixed an issue where in the Swagger UI pages of published REST services and published OData services when using a `default-src` content security policy. The use of inline style on these pages resulted in an empty page in the browser and a message on the console: *"Refused to apply inline style because it violates the following Content Security Policy directive: ..."*. (Ticket 208922) * We fixed the issue that where a document was opened or created in Studio Pro, but the document tab did not receive the keyboard focus. * We fixed an issue where dates were wrongly converted when selecting a date using the datepicker in a web app with its language set to Thai on iOS devices using the **Buddhist** calendar setting. (Ticket 206988) * We fixed an issue where resolving a consistency error for a mapping document ran the whole consistency check instead of only the impacted documents. ### Known Issues * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](https://docs.mendix.com/refguide9/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](https://docs.mendix.com/refguide9/version-control-menu/#show-changes) dialog box. * Workaround: For details, see [this section](https://docs.mendix.com/refguide9/troubleshoot-git-issues/#css-error) in *Troubleshooting Version Control*. * When the `com.mendix.storage.azure.BlobEndpoint` runtime setting contains the container name as a suffix (for example, https://account.blob.core.windows.net/example-container/), files stored in Azure will be stored at the top-level without a directory hierarchy. Previously they would have been stored in a directory hierarchy which means that the app can no longer access previously-stored files. (Ticket 210679)