Add 11.12.4 Studio Pro Release Notes

content/en/docs/releasenotes/studio-pro/11/11.12.md

@@ -12,6 +12,51 @@ weight: 88
 
 {{% 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.4 {#11124}
+
+**Release date: August ___, 2026**
+
+{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.12.4" text="Go to Marketplace" title="Download version 11.12.4 from the Marketplace" %}}
+
+### Improvements
+
+* We added a new context menu item to links in Maia Chat messages to open them in your default browser via the **Open link in browser** context menu item.
+* We improved the alignment between different loading states in **Maia Chat**.
+* We updated Maia Agent's visual design to align with EU AI Act compliance guidelines for improved transparency and readability.
+* We improved React client bundling diagnostics with clearer reporting for memory-related bundler failures.
+
+### Fixes
+
+* We fixed an issue where Eclipse showed `cannot be resolved to a type` errors for Java actions in protected modules. (Ticket 235055)
+* We fixed an issue where design properties from an excluded module incorrectly triggered an error that they had been renamed. (Ticket 281790)
+* We fixed an issue where session cleanup did not succeed and kept retrying indefinitely when an optimistic locking error occurred. (Ticket 282375)
+* We fixed an issue where placing a widget with a selection, such as a **Combobox**, inside a repeatable container widget (for example, the **Gallery** widget) prevented expressions from using `$currentObject` or caused a client error when selecting an attribute from the data source. (Tickets 283186, 283708)
+* We fixed an issue where JavaScript actions with npm dependencies installed in their `actions/node_modules` folder failed to bundle in the React client, for both the Rollup and Rspack bundlers. (Ticket 283840)
+* We fixed an issue where text box values filled in by a password manager were not registered. (Tickets 284395, 283505)
+* We fixed an issue where expanding a folder in a document selector (for example, while selecting a microflow, nanoflow, or JSON structure) showed it as expanded but without its contents. (Ticket 284451)
+* We fixed an issue where configuring the image property on a widget was not correctly reflected in the widget properties. (Ticket 284848)
+* We addressed some situations where the page editor did not use the correct font for an icon from an icon collection. (Ticket 284860)
+* We fixed an issue where importing CSV data for an icon collection failed for icons whose names start with an underscore. (Ticket 285041)
+* We fixed an issue where a progress bar remained visible when opening a page while the homepage was still loading.(Ticket 285253)
+* We fixed an issue where opening the **Customize offline synchronization** dialog of a navigation profile resulted in an error when an entity with a custom synchronization configuration was used on a page and had specializations of its own. (Ticket 285791)
+* We fixed an application startup error when a direct association from an entity to a specialization of itself was removed and the parent of the association was either removed or was no longer a generalization of the child of the association. (Ticket 285998)
+* We fixed an issue where Studio Pro froze while a progress dialog is shown, for example, while opening an app.
+* We fixed an issue where the active document's tab got scrolled out of view after opening many documents in a row.
+* We fixed an issue where renaming in Studio Pro (for example, a module or an entity) led to consistency errors in microflow expressions.
+* We fixed an issue where Java proxy classes for an entity and its related entities were not regenerated after changing the entity's generalization.
+* We fixed an issue causing repeated log warnings `A MeterFilter is being configured...`, even when the metrics configuration had not changed.
+* The fix to remove renamed design properties can now be applied to all design properties in a module.
+
+### Known Issues
+
+* The Maia Chat panel may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**.
+  * Workaround: Manually close the panel when it appears.
+* When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning.
+  * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty.
+* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat.
+  * Workaround: Click **New Chat** to make the **Skills** button appear without requiring a full restart. Note that **New Chat** is only available when the chat is not empty.
+* When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue.
+
 ## 11.12.3 {#11123}
 
 **Release date: August 14, 2026**
@@ -73,7 +118,7 @@ weight: 88
     * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty.
 * The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat.
     * Workaround: Click **New Chat** to make the **Skills** button appear without requiring a full restart. Note that **New Chat** is only available when the chat is not empty.
-* <a id="ki-guids-are-not-restored"></a> When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (App > **Import module or Download from Marketplace**) is not affected by this issue.
+* <a id="ki-guids-are-not-restored"></a> When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue.
 
 ## 11.12.2 {#11122}