11.8 SP Release Notes

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

@@ -0,0 +1,130 @@
+---
+title: "11.8"
+url: /releasenotes/studio-pro/11.8/
+description: "The release notes for Mendix Studio Pro 11.8 (including all patches) with details on new features, bug fixes, and known issues."
+weight: 92
+---
+
+## 11.8.0 {#1180}
+
+**Release date: Febuary ___, 2026**
+
+{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.8.0" text="Go to Marketplace" title="Download version 11.8.0 from the Marketplace" %}}
+
+For more guidance, see the official [11.8 Mendix release blog](____________).
+
+### New Features
+
+#### Unified Maia Experience: Maia Make
+
+With Mendix 11.8, we are introducing [Maia Make](/refguide/maia-make/), a unified conversational interface within Studio Pro that consolidates all AI-assisted development capabilities into a single chat experience. Start a conversation, describe what you need in natural language, and Maia generates the necessary artifacts for you—data structures, overview pages, microflows, and more. Whether you are creating new documents or iterating on existing work, Maia Make provides a streamlined, task-based approach to building applications with AI assistance.
+
+The following Maia capabilities have been seamlessly moved to the new Maia Make experience:
+
+* [Maia for Domain Model](/refguide/maia-for-domain-model/): Generate domain models from natural language descriptions
+* [Maia for Pages](/refguide/maia-for-pages/): Generate overview pages from natural language descriptions
+* [Maia Chat](/refguide/maia-chat/) in Studio Pro: Conversational assistance for general development queries
+* [Maia Explain](/refguide/maia-expain/): Get clear explanations of your logic and pages
+
+Maia Make also introduces the following new capabilities to accelerate your development:
+
+* [Maia for Microflows](/refguide/maia-for-microflows/): Generate microflows including XPath constraints and expressions, and more
+* [MCP Client](/refguide/maia-mcp/): Connect to compatible MCP Servers to leverage tools such as Playwright or Figma
+* User Story Linking: Select an existing story and let Maia help you realize it
+
+Maia Make is enabled by default. It is possible to disable it in Studio Pro **Preferences**, via the **Maia** tab. For more information, see [Maia Make](/refguide/maia-make/).
+
+#### Other New Features
+
+- We added a **Cancel synchronization** nanoflow activity to stop synchronization.
+- We added a `reloadApp` function to the `mx-api/ui` Client API that allows you to reload your application. By passing the optional `withState` parameter, you can preserve the application's state during the reload. This method is not supported on native mobile. For more information, refer to the [Client API documentation](/apidocs-mxsdk/apidocs/client-api/).
+- We added non-interrupting event sub-processes to the workflow editor. This allows users to trigger optional process flows at any point during a workflow's execution. By using the `notify workflow` mechanism and targeting the sub-process's start event, these additional flows can be initiated without interrupting the main workflow.
+- We added a `allowUpload` flag on `file` and `image` properties that provides upload capabilities to progressive web apps. We added new types `EditableFileValue` and `EditableImageValue` to provide upload related methods (such as `setValue`, `setValidator`, and other typical ones). This flag is optional to ensure backwards compatibility, with the default value being `false`. Native widgets do not currently support this feature.
+
+### Improvements
+
+- The `OQL DELETE FROM` statement now supports associations with on delete behavior:
+    * **Delete associated objects as well**
+    * **Delete the object only if there are no associated objects**
+- We removed unnecessary transaction savepoints created by the runtime when committing or deleting multiple objects.
+- We added a configurable option **Use new string behavior** in the Runtime tab that controls how null and undefined values are handled for string attributes in the client. The new behavior (on by default for new projects) keeps these values as null to maintain consistency between nanoflows and microflows, while the old behavior converts them to empty strings. This option provides backward compatibility and gives developers time to migrate to the new more consistent behavior.
+- [Date Picker](/refguide/date-picker/) now shows placeholder (or date format if placeholder is empty) even if the widget is in read only state. This makes the date picker widget consistent with other input widgets.
+
+### Updated Language Codes for Hebrew and Indonesian
+
+We updated the ISO 639 language codes for **Hebrew** and **Indonesian** to align with the current standard:
+ - **Hebrew**: Changed from `iw_IL` (deprecated) to `he_IL` (current standard)
+ - **Indonesian**: Changed from `in_ID` (deprecated) to `id_ID` (current standard)
+
+#### Impact
+
+If your app uses **Hebrew** or **Indonesian**, these languages will be marked with an asterisk in your project, and you will see a deprecation warning.
+
+#### Migration Steps
+
+To migrate to the updated language codes:
+ - Add the non-deprecated version of the language to your app (one without asterisk)
+ - Move existing translations from the deprecated language to the new version using **Language** > **Language Operations**
+ - Remove the deprecated language version (marked with asterisk) from your app
+
+This ensures your app uses the current ISO 639 standard and avoids future compatibility issues.
+
+#### Other Improvements
+
+- We improved performance for repeatable containment widgets that contain an input widget, when not running the React client. This improvement is particularly noticeable in scenarios where a DG2 has multiple columns configured with custom content containing input widgets. (Ticket 251521)
+- When the progress dialog only has one step, we now only show the progress bar.
+- We improved performance for mx.exe diff command. Now the command consumes less memory and executes faster.
+- The macOS installer now includes the Mendix Version Selector. This enhancement allows macOS Studio Pro users to open applications directly from Sprintr, double-click MPR/MPK files to open them, and utilize the 'Start from Maia' feature within the Mendix Portal.
+- The Studio Pro on macOS was renamed to Mendix Studio Pro.
+- We improved the error message in case the database does not contain a pre-analysis migration version. That can happen only when upgrading from a Mendix version earlier than 5.10.
+- We have removed redundant button "Maia Explain" from the logic editors in favor of "Maia Explain" item in the context menu of the App Explorer.
+- We simplified Maia preferences by adding a single toggle to enable or disable all Maia features at once.
+- We fixed the issue in OData Exists queries where an XPath constraint with nested-associations would result in incorrect OData filter (Ticket 261698).
+- The OpenAPI documentation pane in Studio Pro now allows you to copy text using Ctrl+C.
+- We improved the Gradle settings in the Preferences. The Gradle location will now not be hidden if Gradle synchronization is disabled.
+- We clarified an error message when cloning or checking out a branch into a directory with a long path.
+- We increased the width of scrollbars on editors and some of the panes to increase usability.
+- We introduced an opt-in runtime setting `MaxRetrieveAmount` that limits the maximum amount of objects retrieved by database datasource operation. (Tickets 236618, 247111)
+- We improved the `reloadApp` function in the `mx-api/ui` Client API to better handle sessionStorage quota exceeded errors. When `withState` is `true` and the browser's sessionStorage quota is exceeded, it now throws a `ReloadStateQuotaExceededError` that you can catch and handle. For more information, refer to the [Client API documentation](apidocs-mxsdk/apidocs/client-api-11/). When re-running an app in development and the sessionStorage quota is exceeded, the reload gracefully falls back to reloading without preserving state. (Ticket 264656)
+- We improved the `Set all to` toggle in the entity access rules editor so that when some members have access rights and others don't, the toggle now disables all rights instead of enabling them. This prevents the `Write` toggle from unexpectedly affecting read access.
+
+### Fixes
+
+- We fixed an issue when studio pro was not able to find git after fresh installation if it was run from installer. (Tickets 232343, 232540, 232452, 234800, 231989)
+- We fixed an issue that when document was modified on one source and deleted on other during combination process user had no option to resolve a conflict by deleting a document. (Ticket 263119)
+- We fixed an issue where an Oops dialog appeared with conditional editability settings when a page contains multiple widgets with the same name, for example as a side effect of a merge. (Ticket 264502)
+- We fixed an issue in offline apps that could result in errors like "[Synchronization] SQLiteError: table mx10414574138294561$_guidToTable has no column named inaccessibleAttrs" by ensuring database migrations happen properly for all users in the client database. (Tickets 264910, 265393, 269740)
+- We fixed the NullPointerException which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403)
+- In the logic editors, we fixed an issue when Show Message activity could have an empty caption after initial loading of the microflow. (Ticket 268024)
+- We fixed an issue that caused setting the image of a building block to show an error dialog instead of resizing the image. (Ticket 268856)
+- In the logic editors, we fixed an issue when Extracting submicroflow the sequence flow in the original microflow had invalid condition value, and extracted microflow was missing one. (Ticket 269233).
+- We fixed an issue where a long-running after startup microflow causes the node to be assumed crashed by other nodes. (Ticket 269993)
+- We fixed an issue where an Oops dialog appeared with conditional editability settings when a widget referenced a default variable. (Ticket 270420)
+- We fixed an issue where an Oops pop-up window was displayed when a widget with a data source contained expressions referring to unavailable variables. (Ticket 270865)
+- We fixed an issue where, when downloading a widget from the Marketplace or updating a widget via the widget updater, the widget MPK file would become corrupted. This corruption led to an error dialog appearing in Studio Pro when attempting to read the widget package. (Ticket 270889, 271134)
+- We fixed an issue where deleting an external object with a local association to it that uses the direct association storage format would fail with an exception.
+- We fixed an issue in workflow user tasks, where having no fallback outcome in majority or threshold criteria with a single outcome would prevent the runtime from starting.
+- We fixed an issue in the modernized app explorer where pressing the DEL key in the search input would trigger document deletion instead of text deletion.
+- We fixed an issue in the modernized app explorer where the version number of an add-on module would not show.
+- We fixed the issue in the modernized App Explorer where the visibility icon was not displayed when the export level was set to 'Usable'.
+- We fixed an issue in the modernized App Explorer where pressing [Escape] would not clear the search query.
+- We fixed an issue in the modernized App Explorer where the hotkey SHIFT+F10 for opening the context menu did not work.
+- We fixed an issue in the modernized App Explorer where a Domain Model node with View Entity documents as children would automatically expand on double click.
+- We fixed an issue in several right click context menu's where for MacOS several hotkey combinations were displayed wrong.
+- We fixed SQLite Error 5: 'database is locked' error.
+- We fixed an issue where 'access denied' exceptions could occur during rebase, merge, cherry-pick, revert, or feature branch merge operations.
+- Fixed an issue where Maia explain for Microflows crashes sometimes.
+- We fixed an issue in Maia chat causing it to crash when a Studio Pro version attribute was missing in a reference.
+- We fixed scenarios in Android where navigating fields of a Dataview, of different types, would not be possible using an external keyboard.
+- We fixed an issue in the call external action activity in Studio Pro where resolving inconsistencies would clear additional attributes.
+- We fixed an issue in the OpenAPI documents of published REST services. The dates used in examples now use correct values.
+- The consumed REST service editor in Studio Pro is now available in all languages that Studio Pro supports, not just English.
+- We fixed `com.mendix.systemwideinterfaces.core.IUser::getUserName` which was always returning the user name at the time of login. It's now returning the actual user name after a cached session has been revalidated.
+- Resolved an OS command injection vulnerability in the Git process runner reported by Veracode.
+- Resolved an issue where partially cloned apps were mistakenly identified as fully cloned during the cloning process, potentially leading to a 128 error.
+- We fixed an issue on macOS where some views would behave in unwanted ways when scrolling.
+- We fixed an issue in the React client where enabling autofocus on a popup that only contained focusable elements in the header or footer resulted in no element being focused.
+- We fixed an issue where autofocus was not enabled for login dialogs and popups shown by the `Show message` action.
+- We fixed an issue where logging in with incorrect credentials would throw an error in the client console instead of showing a validation message. This was caused by the Runtime not returning a 401 response for authentication failures. We also fixed the same issue for license-related errors where a 402 response was not being returned. (Ticket 268509)
+- Fixed TabContainer not updating the active tab attribute or firing the onChange nanoflow on tab switch when the TabContainer entity is passed as a nanoflow argument.
+- We fixed an issue where an Oops pop-up window appeared when page actions with return value mappings were copied and pasted or extracted to a snippet.