11.12.1

LTS

July 15, 2026

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: July 15, 2026** ### New Features - We added ability to see documents affected by Maia in the **Changes** pane. - We added **Maia Explain** and **Solve problem with Maia Chat** context menu options to the error list to help you understand and resolve consistency errors directly with Maia. ### Improvements - Maia now receives detailed information about errors inside microflow expressions it generates, so it can correct them more accurately. - Embedded applications now support optional parameters for the home page and home microflow. ### Fixes - We fixed the `t is not a function` crash in microflow and workflow editors, introduced by the recent Microsoft update for WebView. If you have no other affected Studio Pro installations, we recommend that you revert the workaround to prevent future compatibility issues. (Tickets 282617, 282634, 282668) - We fixed an issue in React client mode where navigating between pages with the same layout left widgets unresponsive. (Ticket 276710) - On SQL Server, when a unique constraint or foreign key constraint is dropped, we now use `IF EXISTS`. This avoids an automatic rollback of the synchronization transaction in case the constraint does not exist. (Ticket 279545) - We fixed an issue where runtime fails to finish executing a queued task started by a user if the user is deleted during task execution. (Ticket 279891) - We fixed an issue where extracting a sub-microflow from activities that referenced a predefined variable (such as `$currentUser`) created a parameter with the same reserved name on the new sub-microflow, resulting in a `Variable name is reserved` error. Predefined variables are now skipped when generating the parameters of the extracted sub-microflow, since they are already globally in scope. (Ticket 281319) - We fixed an issue where building an application gave the following error: `System.FormatException: The input string '' was not in a correct format`. (Tickets 282176, 282223) - We resolved the issue in Studio Pro that Java files do not get generated when deploying for Eclipse. (Ticket 282363) - We fixed an issue with PWAs using Rspack where the service worker was not be created correctly. (Ticket 282616, 282601) - We removed GuidMapping documents from the **Changes** pane. - We fixed an issue where the **Extensions** setting was visible for all module types instead of only for add-ons. - We fixed an issue in the **Call Web Service** activity and in consumed OData services that consume services using OData version 3. The XML parser now rejects DTD declarations and external entities, because a compromised server might exploit those features. - We resolved an issue where Studio Pro hung on the **Updating original app** step when opening an app. - We fixed an issue in the modernized App Explorer where too many nodes could be selected at once. - We fixed an issue when calling `mx.ui.openForm` in the Dojo client. - We fixed an issue so that now, missing *progress message* on a blocking progress bar no longer causes a crash during deployment. - We fixed an issue where **Settings** were not be correctly loaded when upgrading a app to 11.12. - We fixed an issue where the MCP Server settings intermittently caused an Oops dialog to appear. ### Deprecations - We dropped support for the following database versions that are no longer supported by the vendors: - PostgreSQL 13 - MariaDB 10.6