From 22e36865cccd966c7e8592fdf528715cc905dff5 Mon Sep 17 00:00:00 2001 From: ConnorLand Date: Tue, 17 Feb 2026 10:53:40 +0100 Subject: [PATCH 01/12] Upload RNs --- .../docs/releasenotes/studio-pro/11/11.8.md | 110 ++++++++++++++++++ 1 file changed, 110 insertions(+) create mode 100644 content/en/docs/releasenotes/studio-pro/11/11.8.md diff --git a/content/en/docs/releasenotes/studio-pro/11/11.8.md b/content/en/docs/releasenotes/studio-pro/11/11.8.md new file mode 100644 index 00000000000..f01b500d95e --- /dev/null +++ b/content/en/docs/releasenotes/studio-pro/11/11.8.md @@ -0,0 +1,110 @@ +--- +title: "11.7" +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 + +- We introduced a new API for accessing runtime functionality from web extensions, which allows you to execute preview actions and monitor the runtime connection status. It is available under studioPro.app.runtime in the web extensibility API. +- We added a cancel synchronization nanoflow activity and action 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've 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 `allowUpload` flag on `file` and `image` property that provides upload capabilities to a PW. We added new types `EditableFileValue` and `EditableImageValue` to provide upload related methods, such as `setValue`, `setValidator`, etc. This flag is optional to ensure backwards compatibility, with default value `false`. Native widgets do not receive support for this feature as of now. + +### Improvements + +- The OQL DELETE FROM statement now supports associations with On Delete Behavior "Delete associated objects as well" and "Delete the object only if there are no associated objects". + +- We removed some 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 (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 now shows placeholder (or date format if placeholder is empty) even if the widget is in read only state. This makes Date picker widget consistent with other input widgets. + +### Updated Language Codes for Hebrew and Indonesian + +We've 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'll 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. +- We've 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. (Ticket 236618, Ticket 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 in workflow user tasks, where having no fallback outcome in majority or threshold criteria with a single outcome would prevent the runtime from starting. +- 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, 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) +- 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 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 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 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 an issue when studio pro wasn’t able to find git after fresh installation if it was run from installer. (Ticket 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 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. + +- We fixed an issue where an Oops dialog appeared with conditional editability settings when a widget referenced a default variable. (Ticket 270420) +- Fixed an issue where Maia explain for Microflows crashes sometimes. + +- 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 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 that caused setting the image of a building block to show an error dialog instead of resizing the image. (Ticket 268856) +- 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. +- We fixed the NullPointerException which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403) +- We fixed an issue where a long-running after startup microflow causes the node to be assumed crashed by other nodes. (Ticket 269993) +- 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 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 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. From 007764b7ec608766f7a2004551fd0ea66d99b799 Mon Sep 17 00:00:00 2001 From: ConnorLand Date: Tue, 17 Feb 2026 10:54:52 +0100 Subject: [PATCH 02/12] Change title --- content/en/docs/releasenotes/studio-pro/11/11.8.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.8.md b/content/en/docs/releasenotes/studio-pro/11/11.8.md index f01b500d95e..e3ad53422ad 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.8.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.8.md @@ -1,5 +1,5 @@ --- -title: "11.7" +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 From 4ab1a8c539e10a52131f1bb567cf43b9e1854cc3 Mon Sep 17 00:00:00 2001 From: ConnorLand Date: Tue, 17 Feb 2026 11:04:02 +0100 Subject: [PATCH 03/12] Edit --- .../docs/releasenotes/studio-pro/11/11.8.md | 20 ++++++++----------- 1 file changed, 8 insertions(+), 12 deletions(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.8.md b/content/en/docs/releasenotes/studio-pro/11/11.8.md index e3ad53422ad..7ac5fbb4c68 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.8.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.8.md @@ -15,16 +15,15 @@ For more guidance, see the official [11.8 Mendix release blog](____________). ### New Features -- We introduced a new API for accessing runtime functionality from web extensions, which allows you to execute preview actions and monitor the runtime connection status. It is available under studioPro.app.runtime in the web extensibility API. +- We introduced a new API for accessing runtime functionality from web extensions, which allows you to execute preview actions and monitor the runtime connection status. It is available under `studioPro.app.runtime` in the Web Extensibility API. - We added a cancel synchronization nanoflow activity and action 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've 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 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 `allowUpload` flag on `file` and `image` property that provides upload capabilities to a PW. We added new types `EditableFileValue` and `EditableImageValue` to provide upload related methods, such as `setValue`, `setValidator`, etc. This flag is optional to ensure backwards compatibility, with default value `false`. Native widgets do not receive support for this feature as of now. ### Improvements - The OQL DELETE FROM statement now supports associations with On Delete Behavior "Delete associated objects as well" and "Delete the object only if there are no associated objects". - - We removed some 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 (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. @@ -32,7 +31,7 @@ For more guidance, see the official [11.8 Mendix release blog](____________). ### Updated Language Codes for Hebrew and Indonesian -We've updated the ISO 639 language codes for **Hebrew** and **Indonesian** to align with the current standard: +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) @@ -48,7 +47,7 @@ To migrate to the updated language codes: - 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. -- We've 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) +- 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. @@ -61,7 +60,7 @@ This ensures your app uses the current ISO 639 standard and avoids future compat - 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. (Ticket 236618, Ticket 247111) +- 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. @@ -70,8 +69,7 @@ This ensures your app uses the current ISO 639 standard and avoids future compat - 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. - 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, 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) -- 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). - +- 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 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 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 in the modernized app explorer where pressing the DEL key in the search input would trigger document deletion instead of text deletion. @@ -81,14 +79,12 @@ This ensures your app uses the current ISO 639 standard and avoids future compat - 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 an issue when studio pro wasn’t able to find git after fresh installation if it was run from installer. (Ticket 232343,232540,232452,234800,231989) +- We fixed an issue when studio pro wasn’t 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 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. - - We fixed an issue where an Oops dialog appeared with conditional editability settings when a widget referenced a default variable. (Ticket 270420) - Fixed an issue where Maia explain for Microflows crashes sometimes. - - 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 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. @@ -106,5 +102,5 @@ This ensures your app uses the current ISO 639 standard and avoids future compat - 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 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 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 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. From 93766ffad6dec68900f2c04c3ba1d4bc89f18cf9 Mon Sep 17 00:00:00 2001 From: ConnorLand Date: Tue, 17 Feb 2026 11:21:35 +0100 Subject: [PATCH 04/12] Reorder fixes --- .../docs/releasenotes/studio-pro/11/11.8.md | 29 ++++++++++--------- 1 file changed, 16 insertions(+), 13 deletions(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.8.md b/content/en/docs/releasenotes/studio-pro/11/11.8.md index 7ac5fbb4c68..f1471352fc7 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.8.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.8.md @@ -47,6 +47,9 @@ To migrate to the updated language codes: - 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. @@ -65,13 +68,21 @@ This ensures your app uses the current ISO 639 standard and avoids future compat - 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 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 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) -- 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 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 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 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'. @@ -79,22 +90,15 @@ This ensures your app uses the current ISO 639 standard and avoids future compat - 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 an issue when studio pro wasn’t 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 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. -- We fixed an issue where an Oops dialog appeared with conditional editability settings when a widget referenced a default variable. (Ticket 270420) - Fixed an issue where Maia explain for Microflows crashes sometimes. -- 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 Maia chat causing it to crash when a studio pro version attribute was missing in a reference. +- 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 that caused setting the image of a building block to show an error dialog instead of resizing the image. (Ticket 268856) - 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. -- We fixed the NullPointerException which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403) -- We fixed an issue where a long-running after startup microflow causes the node to be assumed crashed by other nodes. (Ticket 269993) - 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. @@ -102,5 +106,4 @@ This ensures your app uses the current ISO 639 standard and avoids future compat - 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 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 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. From cfbe93f325eb760424b3825c27eb2a198c980bb4 Mon Sep 17 00:00:00 2001 From: ConnorLand Date: Tue, 17 Feb 2026 13:43:48 +0100 Subject: [PATCH 05/12] Edit --- .../docs/releasenotes/studio-pro/11/11.8.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.8.md b/content/en/docs/releasenotes/studio-pro/11/11.8.md index f1471352fc7..77c18b55795 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.8.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.8.md @@ -16,18 +16,19 @@ For more guidance, see the official [11.8 Mendix release blog](____________). ### New Features - We introduced a new API for accessing runtime functionality from web extensions, which allows you to execute preview actions and monitor the runtime connection status. It is available under `studioPro.app.runtime` in the Web Extensibility API. -- We added a cancel synchronization nanoflow activity and action to stop synchronization. +- We added a **Cancel synchronization** nanoflow activity and action 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 `allowUpload` flag on `file` and `image` property that provides upload capabilities to a PW. We added new types `EditableFileValue` and `EditableImageValue` to provide upload related methods, such as `setValue`, `setValidator`, etc. This flag is optional to ensure backwards compatibility, with default value `false`. Native widgets do not receive support for this feature as of now. +- 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" and "Delete the object only if there are no associated objects". -- We removed some 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 (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 now shows placeholder (or date format if placeholder is empty) even if the widget is in read only state. This makes Date picker widget consistent with other input widgets. +- 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 @@ -37,7 +38,7 @@ We updated the ISO 639 language codes for **Hebrew** and **Indonesian** to align #### Impact -If your app uses **Hebrew** or **Indonesian**, these languages will be marked with an asterisk in your project, and you'll see a deprecation warning. +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 From 782161c74371e8bbc924d11e41e022d91327cf41 Mon Sep 17 00:00:00 2001 From: Quinn Tracy <142489060+quinntracy@users.noreply.github.com> Date: Tue, 17 Feb 2026 15:16:18 +0100 Subject: [PATCH 06/12] Remove RN --- content/en/docs/releasenotes/studio-pro/11/11.8.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.8.md b/content/en/docs/releasenotes/studio-pro/11/11.8.md index 77c18b55795..03a745a465c 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.8.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.8.md @@ -15,7 +15,6 @@ For more guidance, see the official [11.8 Mendix release blog](____________). ### New Features -- We introduced a new API for accessing runtime functionality from web extensions, which allows you to execute preview actions and monitor the runtime connection status. It is available under `studioPro.app.runtime` in the Web Extensibility API. - We added a **Cancel synchronization** nanoflow activity and action 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. From 0d2187a80b8798440d9d2c6efdb0e69c18286d82 Mon Sep 17 00:00:00 2001 From: Yiyun Liao Date: Fri, 20 Feb 2026 17:20:06 +0100 Subject: [PATCH 07/12] Add Maia Make RN --- .../docs/releasenotes/studio-pro/11/11.8.md | 25 +++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.8.md b/content/en/docs/releasenotes/studio-pro/11/11.8.md index 03a745a465c..4cdfdc49683 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.8.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.8.md @@ -14,8 +14,29 @@ weight: 92 For more guidance, see the official [11.8 Mendix release blog](____________). ### New Features - -- We added a **Cancel synchronization** nanoflow activity and action to stop synchronization. + +#### 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. From e0af8242324f1d16badab295eaebc9380bbd521b Mon Sep 17 00:00:00 2001 From: Yiyun Liao Date: Fri, 20 Feb 2026 17:23:37 +0100 Subject: [PATCH 08/12] Small style fix --- content/en/docs/releasenotes/studio-pro/11/11.8.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.8.md b/content/en/docs/releasenotes/studio-pro/11/11.8.md index 4cdfdc49683..f196acbdb5b 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.8.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.8.md @@ -32,7 +32,7 @@ Maia Make also introduces the following new capabilities to accelerate your deve * [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/). +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 From c62f3306eab4dcdd21e0eb5acb9e98ee198c2d14 Mon Sep 17 00:00:00 2001 From: Yiyun Liao Date: Fri, 20 Feb 2026 17:33:44 +0100 Subject: [PATCH 09/12] Update the Preferences dialog --- .../refguide/modeling/menus/edit-menu/preferences-dialog.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md b/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md index e46ee663d8e..40b960e86c7 100644 --- a/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md +++ b/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md @@ -108,7 +108,9 @@ You can specify which repositories to use for Gradle. The content of this field ### Generative AI -The **Generative AI** section contains the following settings: +* **Enable Maia** - When enabled, you can access all Maia capabilities in Studio Pro. It is enabled by default. + +In Studio Pro 11.7 and below, the **Generative AI** section contains the following settings: * **Enable Start with Maia** – When enabled, you can use the **Start with Maia** starting point in Studio Pro to help you create an app. For more information on how to use this feature, see [Start with Maia](/refguide/start-with-maia/). It is enabled by default. * **Enable Maia Explain** – When enabled, you can use it to explain a microflow or a nanoflow in the logic editors. For more information on how to use this feature, see [Maia Explain](/refguide/maia-explain/). It is enabled by default. From fd929f1226961be63826d19e7821f0ba1698a8fb Mon Sep 17 00:00:00 2001 From: Yiyun Liao Date: Fri, 20 Feb 2026 18:02:00 +0100 Subject: [PATCH 10/12] Add an info alert to each incorporated Maia capability --- .../modeling/mendix-ai-assistance/maia-chat.md | 12 ++++++++---- .../modeling/mendix-ai-assistance/maia-explain.md | 8 +++++++- .../mendix-ai-assistance/maia-for-domain-model.md | 8 ++++++-- .../modeling/mendix-ai-assistance/maia-for-pages.md | 8 +++++++- .../mendix-ai-assistance/maia-for-workflows.md | 4 ++++ 5 files changed, 32 insertions(+), 8 deletions(-) diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-chat.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-chat.md index fcf60788859..d69e4cf3033 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-chat.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-chat.md @@ -17,9 +17,7 @@ Maia Chat is also available in the Mendix Portal. For more information, refer to {{% alert color="info" %}} To use Maia Chat, an internet connection and signing in to Studio Pro are required. -{{% /alert %}} -{{% alert color="info" %}} Maia Chat does not use any project, customer, or company information. It only uses the data that you have entered in the Chat to fulfill the user request. Please do not enter any personal or sensitive data! {{% /alert %}} @@ -36,7 +34,13 @@ See below a list of Maia Chat's data sources: ## Using Maia Chat in Studio Pro -There are two ways to access Maia Chat in Studio Pro: +{{% alert color="info" %}} +In Studio Pro 11.8 and above, Maia Chat is incorporated into the unified [Maia Make](/refguide/maia-make/) interface. There is no dedicated interface only for Maia Chat. With Maia Make, you can ask questions, ask Maia to explain your logic and pages, and let it generate development artifacts such as data structures, overview pages, and microflows for you. + +Maia Make is enabled by default. It is possible to disable it in Studio Pro **Preferences**, via the **Maia** tab. +{{% /alert %}} + +In Studio Pro 11.7 and below, there are two ways to access Maia Chat in Studio Pro: * Click the **Maia** ({{% icon name="sparkles" %}}) icon to the right of the top bar. * Go to the **View** menu and click **Maia**. @@ -49,7 +53,7 @@ You can start using Maia Chat by clicking one of the demo questions. Alternative For more information on Maia Chat features in Studio Pro, see the sub-sections below. -If Maia is not giving you a good answer, check the [best practices](/portal/maia/#best-practices) in *Maia in Mendix Portal*. If you still can't get a good answer, please see [Giving Feedback](#feedback), below for information on how to let Mendix know. +If Maia is not giving you a good answer, check the [best practices](/portal/maia/#best-practices) in *Maia in Mendix Portal*. If you still can not get a good answer, please see [Giving Feedback](#feedback), below for information on how to let Mendix know. ### Maia Chat Features in Studio Pro diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-explain.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-explain.md index 0a75fa2bb31..2074d0471f7 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-explain.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-explain.md @@ -12,9 +12,15 @@ description: "Describes the features in Maia Explain." To use Maia Explain, an internet connection and signing in to Studio Pro are required. {{% /alert %}} +{{% alert color="info" %}} +In Studio Pro 11.8 and above, Maia Explain is incorporated into the unified [Maia Make](/refguide/maia-make/) interface. There is no dedicated interface only for Maia Explain. With Maia Make, you can ask questions, ask Maia to explain your logic and pages, and let it generate development artifacts such as data structures, overview pages, and microflows for you. + +Maia Make is enabled by default. It is possible to disable it in Studio Pro **Preferences**, via the **Maia** tab. +{{% /alert %}} + Maia Explain helps you easily understand a microflow or a nanoflow. It explains the general purpose of the logic and highlights specific technical details to help you understand the logic further. -## Using Maia Explain +## Using Maia Explain in Studio Pro 11.7 and Below Maia Explain is enabled by default. If you want to disable this feature, go to **Edit** > **Preferences** > the **Maia** tab and clear the **Enable Maia Explain** checkbox. diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-domain-model.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-domain-model.md index 67f999ee73c..bffa85966bf 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-domain-model.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-domain-model.md @@ -18,9 +18,13 @@ Maia for Domain Model helps you generate new [domain model](/refguide/domain-mod ## Using Maia for Domain Model -Maia for Domain Model is enabled by default. +{{% alert color="info" %}} +In Studio Pro 11.8 and above, Maia for Domain Model is incorporated into the unified [Maia Make](/refguide/maia-make/) interface. There is no dedicated interface only for Maia for Domain Model. With Maia Make, you can ask questions, ask Maia to explain your logic and pages, and let it generate development artifacts such as data structures, overview pages, and microflows for you. + +Maia Make is enabled by default. It is possible to disable it in Studio Pro **Preferences**, via the **Maia** tab. +{{% /alert %}} -You can find it in the the toolbar of a domain model: +In Studio Pro 11.7 and below, Maia for Domain Model is enabled by default. You can find it in the the toolbar of a domain model: {{< figure src="/attachments/refguide/modeling/mendix-ai-assistance/maia-for-domain-model/maia-for-domain-model.png" max-width=80% >}} diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-pages.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-pages.md index 943b507ef98..a4675c51fdc 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-pages.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-pages.md @@ -18,7 +18,13 @@ Maia for Pages helps you generate a [page](/refguide/page/) by adding and config ## Using Maia for Pages -To enable Maia for Pages, go to **Edit** > **Preferences** > the **Maia** tab and select **Enable Maia for Pages**. +{{% alert color="info" %}} +In Studio Pro 11.8 and above, Maia for Pages is incorporated into the unified [Maia Make](/refguide/maia-make/) interface. There is no dedicated interface only for Maia for Pages. With Maia Make, you can ask questions, ask Maia to explain your logic and pages, and let it generate development artifacts such as data structures, overview pages, and microflows for you. + +Maia Make is enabled by default. It is possible to disable it in Studio Pro **Preferences**, via the **Maia** tab. +{{% /alert %}} + +In Studio Pro 11.7 and below, to enable Maia for Pages, go to **Edit** > **Preferences** > the **Maia** tab and select **Enable Maia for Pages**. Once enabled, you can find it in the the toolbar of a page: diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-workflows.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-workflows.md index f78c2d17755..2c56237023c 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-workflows.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-workflows.md @@ -12,6 +12,10 @@ description: "Describes the features in Maia for Workflows." To use Maia for Workflows, an internet connection and signing in to Studio Pro are required. {{% /alert %}} +{{% alert color="info" %}} +In Studio Pro 11.8, Maia for Workflows is not available. +{{% /alert %}} + Maia for Workflows helps you generate a [workflow](/refguide/workflows/). It can also provide explanations or further improvements based on the generated elements. The current version has some known limitations. For example, it is currently intended only for use with empty workflows. Generated elements are appended to the end of the workflow, which may result in incorrectly modeled workflows if the workflow is not empty. For more details, see the [Limitations](#limitation) section below. ## Using Maia for Workflows From 4ffdad022e0f3d332b985259df77a0c2488bd2be Mon Sep 17 00:00:00 2001 From: Yiyun Liao Date: Fri, 20 Feb 2026 18:08:40 +0100 Subject: [PATCH 11/12] Revert "Add an info alert to each incorporated Maia capability" This reverts commit fd929f1226961be63826d19e7821f0ba1698a8fb. --- .../modeling/mendix-ai-assistance/maia-chat.md | 12 ++++-------- .../modeling/mendix-ai-assistance/maia-explain.md | 8 +------- .../mendix-ai-assistance/maia-for-domain-model.md | 8 ++------ .../modeling/mendix-ai-assistance/maia-for-pages.md | 8 +------- .../mendix-ai-assistance/maia-for-workflows.md | 4 ---- 5 files changed, 8 insertions(+), 32 deletions(-) diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-chat.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-chat.md index d69e4cf3033..fcf60788859 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-chat.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-chat.md @@ -17,7 +17,9 @@ Maia Chat is also available in the Mendix Portal. For more information, refer to {{% alert color="info" %}} To use Maia Chat, an internet connection and signing in to Studio Pro are required. +{{% /alert %}} +{{% alert color="info" %}} Maia Chat does not use any project, customer, or company information. It only uses the data that you have entered in the Chat to fulfill the user request. Please do not enter any personal or sensitive data! {{% /alert %}} @@ -34,13 +36,7 @@ See below a list of Maia Chat's data sources: ## Using Maia Chat in Studio Pro -{{% alert color="info" %}} -In Studio Pro 11.8 and above, Maia Chat is incorporated into the unified [Maia Make](/refguide/maia-make/) interface. There is no dedicated interface only for Maia Chat. With Maia Make, you can ask questions, ask Maia to explain your logic and pages, and let it generate development artifacts such as data structures, overview pages, and microflows for you. - -Maia Make is enabled by default. It is possible to disable it in Studio Pro **Preferences**, via the **Maia** tab. -{{% /alert %}} - -In Studio Pro 11.7 and below, there are two ways to access Maia Chat in Studio Pro: +There are two ways to access Maia Chat in Studio Pro: * Click the **Maia** ({{% icon name="sparkles" %}}) icon to the right of the top bar. * Go to the **View** menu and click **Maia**. @@ -53,7 +49,7 @@ You can start using Maia Chat by clicking one of the demo questions. Alternative For more information on Maia Chat features in Studio Pro, see the sub-sections below. -If Maia is not giving you a good answer, check the [best practices](/portal/maia/#best-practices) in *Maia in Mendix Portal*. If you still can not get a good answer, please see [Giving Feedback](#feedback), below for information on how to let Mendix know. +If Maia is not giving you a good answer, check the [best practices](/portal/maia/#best-practices) in *Maia in Mendix Portal*. If you still can't get a good answer, please see [Giving Feedback](#feedback), below for information on how to let Mendix know. ### Maia Chat Features in Studio Pro diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-explain.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-explain.md index 2074d0471f7..0a75fa2bb31 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-explain.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-explain.md @@ -12,15 +12,9 @@ description: "Describes the features in Maia Explain." To use Maia Explain, an internet connection and signing in to Studio Pro are required. {{% /alert %}} -{{% alert color="info" %}} -In Studio Pro 11.8 and above, Maia Explain is incorporated into the unified [Maia Make](/refguide/maia-make/) interface. There is no dedicated interface only for Maia Explain. With Maia Make, you can ask questions, ask Maia to explain your logic and pages, and let it generate development artifacts such as data structures, overview pages, and microflows for you. - -Maia Make is enabled by default. It is possible to disable it in Studio Pro **Preferences**, via the **Maia** tab. -{{% /alert %}} - Maia Explain helps you easily understand a microflow or a nanoflow. It explains the general purpose of the logic and highlights specific technical details to help you understand the logic further. -## Using Maia Explain in Studio Pro 11.7 and Below +## Using Maia Explain Maia Explain is enabled by default. If you want to disable this feature, go to **Edit** > **Preferences** > the **Maia** tab and clear the **Enable Maia Explain** checkbox. diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-domain-model.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-domain-model.md index bffa85966bf..67f999ee73c 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-domain-model.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-domain-model.md @@ -18,13 +18,9 @@ Maia for Domain Model helps you generate new [domain model](/refguide/domain-mod ## Using Maia for Domain Model -{{% alert color="info" %}} -In Studio Pro 11.8 and above, Maia for Domain Model is incorporated into the unified [Maia Make](/refguide/maia-make/) interface. There is no dedicated interface only for Maia for Domain Model. With Maia Make, you can ask questions, ask Maia to explain your logic and pages, and let it generate development artifacts such as data structures, overview pages, and microflows for you. - -Maia Make is enabled by default. It is possible to disable it in Studio Pro **Preferences**, via the **Maia** tab. -{{% /alert %}} +Maia for Domain Model is enabled by default. -In Studio Pro 11.7 and below, Maia for Domain Model is enabled by default. You can find it in the the toolbar of a domain model: +You can find it in the the toolbar of a domain model: {{< figure src="/attachments/refguide/modeling/mendix-ai-assistance/maia-for-domain-model/maia-for-domain-model.png" max-width=80% >}} diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-pages.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-pages.md index a4675c51fdc..943b507ef98 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-pages.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-pages.md @@ -18,13 +18,7 @@ Maia for Pages helps you generate a [page](/refguide/page/) by adding and config ## Using Maia for Pages -{{% alert color="info" %}} -In Studio Pro 11.8 and above, Maia for Pages is incorporated into the unified [Maia Make](/refguide/maia-make/) interface. There is no dedicated interface only for Maia for Pages. With Maia Make, you can ask questions, ask Maia to explain your logic and pages, and let it generate development artifacts such as data structures, overview pages, and microflows for you. - -Maia Make is enabled by default. It is possible to disable it in Studio Pro **Preferences**, via the **Maia** tab. -{{% /alert %}} - -In Studio Pro 11.7 and below, to enable Maia for Pages, go to **Edit** > **Preferences** > the **Maia** tab and select **Enable Maia for Pages**. +To enable Maia for Pages, go to **Edit** > **Preferences** > the **Maia** tab and select **Enable Maia for Pages**. Once enabled, you can find it in the the toolbar of a page: diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-workflows.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-workflows.md index 2c56237023c..f78c2d17755 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-workflows.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-for-workflows.md @@ -12,10 +12,6 @@ description: "Describes the features in Maia for Workflows." To use Maia for Workflows, an internet connection and signing in to Studio Pro are required. {{% /alert %}} -{{% alert color="info" %}} -In Studio Pro 11.8, Maia for Workflows is not available. -{{% /alert %}} - Maia for Workflows helps you generate a [workflow](/refguide/workflows/). It can also provide explanations or further improvements based on the generated elements. The current version has some known limitations. For example, it is currently intended only for use with empty workflows. Generated elements are appended to the end of the workflow, which may result in incorrectly modeled workflows if the workflow is not empty. For more details, see the [Limitations](#limitation) section below. ## Using Maia for Workflows From a9ff1416325df7bc15141ef78974862337ac4c9f Mon Sep 17 00:00:00 2001 From: Yiyun Liao Date: Fri, 20 Feb 2026 18:14:06 +0100 Subject: [PATCH 12/12] Revert "Update the Preferences dialog" This reverts commit c62f3306eab4dcdd21e0eb5acb9e98ee198c2d14. --- .../refguide/modeling/menus/edit-menu/preferences-dialog.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md b/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md index 40b960e86c7..e46ee663d8e 100644 --- a/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md +++ b/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md @@ -108,9 +108,7 @@ You can specify which repositories to use for Gradle. The content of this field ### Generative AI -* **Enable Maia** - When enabled, you can access all Maia capabilities in Studio Pro. It is enabled by default. - -In Studio Pro 11.7 and below, the **Generative AI** section contains the following settings: +The **Generative AI** section contains the following settings: * **Enable Start with Maia** – When enabled, you can use the **Start with Maia** starting point in Studio Pro to help you create an app. For more information on how to use this feature, see [Start with Maia](/refguide/start-with-maia/). It is enabled by default. * **Enable Maia Explain** – When enabled, you can use it to explain a microflow or a nanoflow in the logic editors. For more information on how to use this feature, see [Maia Explain](/refguide/maia-explain/). It is enabled by default.