Mendix Studio pro

9.24.2
Stable
May 04, 2023
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: May 4th, 2023** ### Improvements * We improved data encryption in mobile apps. (Ticket 181442) * We reduced the amount of output of Java compilation errors during deployment. ### Fixes * We fixed [CVE-2023-29017](https://www.cve.org/CVERecord?id=CVE-2023-29017). * We fixed [CVE-2023-30547](https://www.cve.org/CVERecord?id=CVE-2023-30547). * We fixed an issue where the debugger threw an error and disconnected after 30 seconds of inactivity. (Tickets 151937, 169696, 175161, 175542, 178553, 180332) * We fixed an issue where non-localized date/time attributes in XPath constraints were not handled correctly, producing incorrect queries. (Ticket 176850) * We fixed an issue where an object validation was removed incorrectly. (Ticket 180011) * We fixed an issue where the language-sensitive parts on pages were not fully updated when you changed the language via the [Language Selector](https://docs.mendix.com/appstore/widgets/language-selector/) widget. (Tickets 180130, 180670, 180824, 181274, 181713, 181974) * We fixed an issue that occurred when opening multiple modal pop-up windows at the same time and it was not possible to focus widgets in the pop-up widget that was on top. (Ticket 180137) * We fixed an issue where an inherited association could not be published in a published OData service that used links as object IDs. (Ticket 181474) * We fixed an issue in XPath constraint suggestions that gave incorrect suggestions when there were whitespace characters after comparison operators (`=`,`<`,`>`,`<=`,`=>`,`!=`). (Tickets 181673, 181908) * We fixed a crash that occurred during login that blocked some users from logging in. (Tickets 181864, 183014) * We fixed an issue that caused the attribute of conditional visibility settings or the text template parameters of a button inside a reference set selector to not be selectable, which resulted in a consistency error. (Ticket 182203) * We fixed an issue in the OpenAPI contract of published REST services where operations that used an import mapping had a schema defined for the other parameters but not the type. (Ticket 182615) * We fixed an issue in the OpenAPI contract of published OData services where `GET` operations no longer specified the `$expand` parameter when there were no associations to expand. (Ticket 182627) * We fixed an issue where deployment failed on the Linux operating system when module names contained upper-case letters. (Tickets 183841, 183872) * We fixed an issue where clicking **Load more** on a list view triggered the on-click event on a surrounding widget. (Ticket 365439) * We fixed an issue where creating a non-persistable entity led to errors when attributes were read-only. * We fixed an issue that triggered a consistency error on a text template of a pluggable widget inside a snippet with multiple parameters if the template had parameters based on an attribute. * We fixed an issue with text controls where the text was sometimes undesirably reverted. * We fixed an issue in the grid control where selecting multiple cells using Shift was inconsistent when clicking on the interactable control itself in the cell (meaning, the check box). * We fixed an issue in XPath constraint suggestions that gave incorrect suggestions when there were multiple predicates (meaning, expressions between the square brackets [`[`, `]`]).