Skip to content
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 45 additions & 0 deletions content/en/docs/releasenotes/studio-pro/11/11.12.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,55 @@ weight: 88
# KI: "Maia Chat panel issue": MID-317
# KI: "BYO LLM": SPAM-435
# KI: "Maia Skills button": SPAM-434
# KI: "When opening, editing, or creating": Zendesk Problem 282636
Comment thread
ConnorLand marked this conversation as resolved.
Outdated
---

{{% alert color="info" %}}For highlights of this release, see the [Mendix Release 11.12](https://www.mendix.com/blog/mendix-release-11-12/) blog post.{{% /alert %}}

## 11.12.1 {#11121}

**Release date: July __, 2026**

{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.12.1" text="Go to Marketplace" title="Download version 11.12.1 from the Marketplace" %}}

### New Features

- We added ability to see documents affected by Maia in 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 removed GuidMapping documents from the **Changes** pane.
- We fixed an issue where extracting a submicroflow from activities that referenced a predefined variable (such as `$currentUser`) would create a parameter with the same reserved name on the new submicroflow, resulting in a "Variable name is reserved" error. Predefined variables are now skipped when generating the parameters of the extracted submicroflow, since they are already globally in scope. (Ticket 281319)
- We fixed an issue where the Extensions setting was visible for all module types instead of only for add-ons.
- 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 the `t is not a function` crash in Microflow and Workflow editors, introduced by the recent Microsoft update for WebView. (Ticket 282617, 282634, 282668)
- 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 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 building an application would give the following error: "System.FormatException: The input string '' was not in a correct format". (Tickets 282176, 282223)
- We resolved the issue that Studio Pro would hang on "Updating original app" step when opening a project.
- We resolved the issue in Studio Pro that *.java files do not get generated when deploying for Eclipse. (Ticket 282363)
Comment thread
ConnorLand marked this conversation as resolved.
Outdated
- We fixed an issue in the modernized app explorer where too many nodes could be selected at once.
- Fixed an issue when calling `mx.ui.openForm` in the Dojo client
- A missing *progress message* on a blocking progress bar no longer causes a crash during deployment.
- Fixed an issue with PWAs using Rspack where the service worker would sometimes not be created correctly. (Ticket 282616, 282601)
- We fixed an issue in React client mode where navigating between pages with the same layout left widgets unresponsive. (Ticket 276710)
- We fixed an issue where **Settings** would not be correctly loaded when upgrading a app to 11.12.

### Deprecations

- We dropped support for the following database versions that are no longer supported by the vendors:
- PostgreSQL 13
- MariaDB 10.6

### Known Issues


## 11.12.0 {#1112}

**Release date: June 30, 2026**
Expand Down
Loading