From 8a74211603acf6ad9ccd2805907c403b45ec1020 Mon Sep 17 00:00:00 2001 From: ConnorLand <47385345+ConnorLand@users.noreply.github.com> Date: Mon, 17 Aug 2026 15:45:29 +0200 Subject: [PATCH 1/8] Upload 11.14 RNs --- .../docs/releasenotes/studio-pro/11/11.14.md | 128 ++++++++++++++++++ 1 file changed, 128 insertions(+) create mode 100644 content/en/docs/releasenotes/studio-pro/11/11.14.md diff --git a/content/en/docs/releasenotes/studio-pro/11/11.14.md b/content/en/docs/releasenotes/studio-pro/11/11.14.md new file mode 100644 index 00000000000..46a5a625655 --- /dev/null +++ b/content/en/docs/releasenotes/studio-pro/11/11.14.md @@ -0,0 +1,128 @@ +--- +title: "11.14" +url: /releasenotes/studio-pro/11.14/ +description: "The release notes for Mendix Studio Pro 11.14 (including all patches) with details on new features, bug fixes, and known issues." +weight: 86 +# KI: "Maia Chat panel issue": MID-317 (check if fixed in 11.14) +# KI: "BYO LLM": SPAM-435 (check if fixed in 11.14) +# KI: "Maia Skills button": (check if fixed in 11.14) +--- + +{{% alert color="info" %}}For highlights of this release, see the [Mendix Release 11.14](https://www.mendix.com/blog/mendix-release-11-14/) blog post.{{% /alert %}} + +## 11.14.0 {#11140} + +**Release date: August ___, 2026** + +{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.14.0" text="Go to Marketplace" title="Download version 11.14.0 from the Marketplace" %}} + +### New Features + +- We added support for updating a module from a file for module packages created before 11.12.0. After you provide the .mpk files, Studio Pro attempts to map documents by name. The update then runs the merge algorithm and, if needed, conflict resolution, so you can keep any customizations made to the module. +- Maia now supports working with Change Data Capture documents. +- We now prefix versioned deployment packages with the branch name they were created with: {BranchName}-{AppName}_{Version}.mda +- A module ID can now be passed to the element selector for the `selectedElementId` property, and the corresponding module will be preselected and expanded. This will allow the user to directly create a new document of the desired type in that module. +- Added a capability to **Clear from device** nanoflow action that removes specific objects from the offline device storage. You can now select individual objects or object lists to clear, in addition to clearing all objects of an entity. + +#### Java 25 + +We now support Java 25 in Studio Pro. +- This release ships with Java Development Kit (JDK) 25 and Gradle 9.5.1. +- You can now configure your application to use Java 25 in the project settings. +- In the Studio Preferences you can configure a different JDK for each supported version of Java. +- Targeting Java 25 allows the project to use language constructs and APIs that were introduced with Java 25. +- Newly created projects will be configured to use Java 25 by default. +- Gradle 9.5.1 supports both Java 21 and 25. Java 25 requires Gradle 9.1+. +- Support for Java 21 is deprecated. + +We recommend that projects and marketplace modules upgrade to Java 25. +You can now create a branch directly from a specific commit in the History pane by right-clicking the commit and selecting **Create branch...**. +- We added a **Branch line** filter to the History pane toolbar. You can now select any branch from a searchable dropdown to view its commit history without switching your working branch. The filter can be cleared with the **×** button or the **Reset filters** button. The **Revert Commit** option is hidden when viewing the history of a branch other than the current one. +- Maia can now answer basic questions about your version control history and commit and push changes to the server. +- We added the ability to filter out the on disk changes on comparison pane. +- We introduced new fields to the package manifest of module packages. The manifest now indicates the type of the module (source, add-on, or solution) and whether the module contains extensions or AI skills. For more information, see [Package Manifest](/refguide/module-settings/#package-manifest). +- The `mx` command line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (Add-on and Solution) modules. The System module remains excluded. +- The `mx` command line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from the Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy. + +### Improvements + +#### Performance + +- We improved build performance and reduced memory usage of the React client when bundling with Rspack. (Ticket 282716, 282165, 282605) + +#### Other Improvements + +- Items in the Comparison pane are now sorted by default, first by module and then by document type. +- We now delete the log files generated by Studio Pro that are older than 7 days. +- We added support for the following database versions: + - MariaDB 12.3 + - MySQL 9.7 +- In the logic editors, we improved the way sequence flow arrows are drawn +- In the logic editors, Maia now tries to enforce best practices more strictly. +- We added 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 **Maia Skills** pane by updating the filter toggle to use a clearer label ("Show errors only") and more appropriate icons. +- We updated Maia Agent's visual design to align with EU AI Act compliance guidelines for improved transparency and readability. +- We changed the JSON Structure document editor to open in a tab and not in a dialog. If you encounter any issues, you can revert to the previous editor by deselecting Preferences > New Features > Use the modernized editor for JSON Structure. +- When logging HTTP requests and responses, the runtime now omits the value of headers Authorization, Cookie, Proxy-Authorization, Set-Cookie, X-Auth-Token and X-Auth-Token where before it only omitted the value of the Authorization header. +- We improved the sort function in `ListOperation` activity. We now use ICU4J library instead of Java's built-in Collator for sorting lists in Microflows. This ensures consistent sorting results in both Microflows and Nanoflows. (Ticket 263311) +- We added new `BiConsumer` overloads to `ListenersRegistry`, `ActionListener`, and `EventActionInfo` so that event listener callbacks now receive the active `IContext` alongside the object. The existing `Consumer` methods are deprecated and will be removed in Mendix 12. +- We have upgraded the Java Migration Tool that is downloaded by the Studio Pro installer to version 1.0.2. This versions adds a recipe to fix the deprecated `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the various `ListenersRegistry.register*Listener` methods. + +- You can now use Enter to navigate between Maia's questions and submit your answers without reaching for the mouse. +- We updated Rspack to version 2.1, which reduces bundle times by up to 25%. +- We improved React client bundling diagnostics with clearer reporting for memory related bundler failures. +- We reduced the exported bundle size for the React and Native clients when a translatable text (such as a Caption or text template) contains parameters. Only the parts of the text that actually differ between languages are now translated, instead of duplicating the entire text for every language. + +### Fixes + +- We fixed an issue where opening the Git preferences would throw an unexpected error when Studio Pro could not load your Git configuration (for example when Git was not installed or its location was set incorrectly). Studio Pro now shows a clear message explaining how to resolve it instead. +- Fixed an issue where activities in microflows generated by Maia showed the default caption **Activity** instead of a caption describing the activity. +- We fixed an issue in React client mode, where snippets would not load properly when navigating to a page with the same snippet. (Ticket 281906) +- We fixed an issue where Studio Pro could incorrectly go into offline mode at startup due to a transient SSL connection failure when fetching the OpenID configuration. +- Fixed an issue where Maia did not create sufficient spacing before and after loops within microflows. +- We fixed an issue where Studio Pro could freeze while a progress dialog is shown, for exammple while opening an app. + +- We fixed an issue where pressing Ctrl+F in the CSS editor or JavaScript editor would open the global Find dialog instead of the editor's built-in search on Windows. (Ticket 283730) +- We fixed an issue where Studio Pro could freeze for up to several seconds during copy operations when another process held a lock on the clipboard. +- We fixed an issue where Studio Pro incorrectly displayed consistency errors after opening an app. +- We fixed an issue where Studio Pro would not update the Java proxies during deployment after renaming a Module. (Ticket #282363) +- We fixed an issue where expanding a folder in a document selector (for example while selecting a microflow, nanoflow, or JSON structure) would show it as expanded but without its contents. (Ticket #284451) +- We fixed an issue where the active document's tab could get scrolled out of view after opening many documents in a row. +- We fixed an issue where renaming in Studio Pro of e.g. a module or an entity could lead to consistency errors in Microflow expressions. +- We fixed an issue where Maia named single objects returned from a **Retrieve Action** as "{entity}List". +- Fixed custom icon visibility for exposed microflow, Java and Javascript actions based on icon availibility and selected Studio Pro theme. +- Fixed an issue where attribute references in microflow expressions were not updated when the attribute was renamed in the **Domain Model**. (Tickets 282373, 282363) +- Fixed an issue where the in-editor Recommender dialog still appeared for empty microflows, nanoflows, and rules after all Recommender features were disabled in **Preferences → AI**. +- Fixed an issue where the content of the Microflow editor and Domain Model editor (Beta) canvas could appear blurry after scrolling or zooming. +- We fixed an issue where the "Push your changes" notification bar was incorrectly shown after a merge or cherry-pick that produced no actual model changes. Studio Pro now detects this scenario and shows an informational message instead. +- We fixed an issue where some grid cells in Studio Pro would become empty while scrolling the grid. +- Fixed an issue where concurrent git operations could fail with an "index is locked" error when the version control status bar polled for conflict information at the same time as write operations such as reset or checkout. +- We resolved an issue where using **Undo All** in the Changes pane did not remove the overview pages generated by **Start with Maia**. +- Fixed Maia's inability to create While loops. +- We fixed an issue in the MCP settings panel where the **Enable all** and **Disable all** buttons remained clickable even when all tools were already in that state. The buttons are now disabled when they would have no effect. +- We have fixed an issue where text box values filled in by a password manager were not registered. (Ticket 284395, 283505) +- Fixed an error in offline-first (PWA) apps when a list view with an association data source was opened for a context object that had not been synchronized yet. (Ticket #283531) +- Fixed an error in offline-first (PWA) apps on iOS 26.5.2 and later, where synchronizing a newly added image or file document failed because its contents were not included in the upload. (Ticket #248368) +- We removed the theme.compiled.css.map from the deployment package due to privacy and security concerns +- We fixed an issue where date filters sent to OData services with DateTimeOffset attributes contained the wrong date format, causing the remote service to reject the request. +- We fixed an issue in Studio Pro where publishing a microflow in a new a REST service allowed adding that service to read-only modules such as the System module. +- We fixed an issue that when opening a non version controlled application after version controlled one, comparison pane was showing old comparison data. +- We fixed an issue where Studio Pro could appear frozen when marking or unmarking a module as a UI resources module. A progress dialog is now shown while the app is synchronized with the file system. +- We fixed an issue in the modernized App Explorer where Studio Pro could appear unresponsive after moving documents or folders. A progress dialog is now shown until the App Explorer has finished updating. +- Fixed an issue in the modernized Find Results panel where closed result sets could reappear and the displayed number of open result sets could be incorrect. +- We fixed an issue in the modernized App Explorer where actions triggered with keyboard shortcuts could apply to the previously selected node. +- We fixed an issue where JavaScript actions with npm dependencies installed in their `actions/node_modules` folder could fail to bundle in the React client, for both the Rollup and Rspack bundlers. (Ticket 283840) +- We fixed an issue where pressing Escape to close a modal dialog would also close the sidebar. +- Fixed an issue in the microflow editor where sometimes the loop would be selected when trying to select elements inside of the loop. +- We fixed an issue where an editable condition set to Never could be lost during widget conversion. (Ticket 283552) + +### Deprecations + +- We have deprecated support for Java 21. Support for Java 21 will be dropped in the future. We recommend to use Java 25. +- The `Consumer` overloads of `ListenersRegistry.register*Listener`, `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the matching `EventActionInfo` constructors are deprecated since Mendix 11.14.0 and will be removed in Mendix 12. Use the `BiConsumer` overloads instead, which also provide the active context to the callback. + +### Breaking Changes + +- Requests to servlets registered via `Core.addDevelopmentServlet` now require authentication. The M2EE admin password must be provided in the `X-M2EE-Authentication` header (Base64-encoded). + +### Known Issues \ No newline at end of file From af7b5ed1d6e32aefe00d406abf38416c7d70cd88 Mon Sep 17 00:00:00 2001 From: "MENDIXDOMAIN\\Maria.Shaposhnikova" Date: Tue, 18 Aug 2026 10:36:57 +0200 Subject: [PATCH 2/8] Review new features --- .../docs/releasenotes/studio-pro/11/11.14.md | 25 +++++++++---------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.14.md b/content/en/docs/releasenotes/studio-pro/11/11.14.md index 46a5a625655..4a83b8fcbd9 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.14.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.14.md @@ -8,8 +8,6 @@ weight: 86 # KI: "Maia Skills button": (check if fixed in 11.14) --- -{{% alert color="info" %}}For highlights of this release, see the [Mendix Release 11.14](https://www.mendix.com/blog/mendix-release-11-14/) blog post.{{% /alert %}} - ## 11.14.0 {#11140} **Release date: August ___, 2026** @@ -18,11 +16,18 @@ weight: 86 ### New Features -- We added support for updating a module from a file for module packages created before 11.12.0. After you provide the .mpk files, Studio Pro attempts to map documents by name. The update then runs the merge algorithm and, if needed, conflict resolution, so you can keep any customizations made to the module. -- Maia now supports working with Change Data Capture documents. +- We added support for updating a module from a file for module packages created below Studio Pro 11.12.0. After you provide the *.mpk* files, Studio Pro attempts to map documents by name. The update then runs the merge algorithm and, if needed, conflict resolution, so you can keep any customizations made to the module. +- Maia now supports working with **Change Data Capture** documents. - We now prefix versioned deployment packages with the branch name they were created with: {BranchName}-{AppName}_{Version}.mda - A module ID can now be passed to the element selector for the `selectedElementId` property, and the corresponding module will be preselected and expanded. This will allow the user to directly create a new document of the desired type in that module. -- Added a capability to **Clear from device** nanoflow action that removes specific objects from the offline device storage. You can now select individual objects or object lists to clear, in addition to clearing all objects of an entity. +- We added a capability to **Clear from device** nanoflow action that removes specific objects from the offline device storage. You can now select individual objects or object lists to clear, in addition to clearing all objects of an entity. +- You can now create a branch directly from a specific commit in the History pane by right-clicking the commit and selecting **Create branch...**. +- We added a **Branch line** filter to the **History** pane toolbar. You can now select any branch from a searchable dropdown to view its commit history without switching your working branch. The filter can be cleared with the **×** button or the **Reset filters** button. The **Revert Commit** option is hidden when viewing the history of a branch other than the current one. +- Maia can now answer basic questions about your version control history and commit and push changes to the server. +- We added the ability to filter out the on disk changes on the **Comparison** pane. +- We introduced new fields to the package manifest of module packages. The manifest now indicates the type of the module (source, add-on, or solution) and whether the module contains extensions or AI skills. For more information, see [Package Manifest](/refguide/module-settings/#package-manifest). +- The `mx` command line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (Add-on and Solution) modules. The System module remains excluded. +- The `mx` command line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from the Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy. #### Java 25 @@ -35,14 +40,8 @@ We now support Java 25 in Studio Pro. - Gradle 9.5.1 supports both Java 21 and 25. Java 25 requires Gradle 9.1+. - Support for Java 21 is deprecated. -We recommend that projects and marketplace modules upgrade to Java 25. -You can now create a branch directly from a specific commit in the History pane by right-clicking the commit and selecting **Create branch...**. -- We added a **Branch line** filter to the History pane toolbar. You can now select any branch from a searchable dropdown to view its commit history without switching your working branch. The filter can be cleared with the **×** button or the **Reset filters** button. The **Revert Commit** option is hidden when viewing the history of a branch other than the current one. -- Maia can now answer basic questions about your version control history and commit and push changes to the server. -- We added the ability to filter out the on disk changes on comparison pane. -- We introduced new fields to the package manifest of module packages. The manifest now indicates the type of the module (source, add-on, or solution) and whether the module contains extensions or AI skills. For more information, see [Package Manifest](/refguide/module-settings/#package-manifest). -- The `mx` command line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (Add-on and Solution) modules. The System module remains excluded. -- The `mx` command line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from the Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy. +We recommend that projects and Marketplace modules upgrade to Java 25. + ### Improvements From 43bdf68b6885960bd07d02f9819019cff00557ef Mon Sep 17 00:00:00 2001 From: "MENDIXDOMAIN\\Maria.Shaposhnikova" Date: Tue, 18 Aug 2026 12:37:52 +0200 Subject: [PATCH 3/8] Review Improvements --- .../docs/releasenotes/studio-pro/11/11.14.md | 47 ++++++++++--------- 1 file changed, 24 insertions(+), 23 deletions(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.14.md b/content/en/docs/releasenotes/studio-pro/11/11.14.md index 4a83b8fcbd9..e0bd662db20 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.14.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.14.md @@ -15,19 +15,6 @@ weight: 86 {{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.14.0" text="Go to Marketplace" title="Download version 11.14.0 from the Marketplace" %}} ### New Features - -- We added support for updating a module from a file for module packages created below Studio Pro 11.12.0. After you provide the *.mpk* files, Studio Pro attempts to map documents by name. The update then runs the merge algorithm and, if needed, conflict resolution, so you can keep any customizations made to the module. -- Maia now supports working with **Change Data Capture** documents. -- We now prefix versioned deployment packages with the branch name they were created with: {BranchName}-{AppName}_{Version}.mda -- A module ID can now be passed to the element selector for the `selectedElementId` property, and the corresponding module will be preselected and expanded. This will allow the user to directly create a new document of the desired type in that module. -- We added a capability to **Clear from device** nanoflow action that removes specific objects from the offline device storage. You can now select individual objects or object lists to clear, in addition to clearing all objects of an entity. -- You can now create a branch directly from a specific commit in the History pane by right-clicking the commit and selecting **Create branch...**. -- We added a **Branch line** filter to the **History** pane toolbar. You can now select any branch from a searchable dropdown to view its commit history without switching your working branch. The filter can be cleared with the **×** button or the **Reset filters** button. The **Revert Commit** option is hidden when viewing the history of a branch other than the current one. -- Maia can now answer basic questions about your version control history and commit and push changes to the server. -- We added the ability to filter out the on disk changes on the **Comparison** pane. -- We introduced new fields to the package manifest of module packages. The manifest now indicates the type of the module (source, add-on, or solution) and whether the module contains extensions or AI skills. For more information, see [Package Manifest](/refguide/module-settings/#package-manifest). -- The `mx` command line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (Add-on and Solution) modules. The System module remains excluded. -- The `mx` command line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from the Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy. #### Java 25 @@ -42,6 +29,21 @@ We now support Java 25 in Studio Pro. We recommend that projects and Marketplace modules upgrade to Java 25. +#### Other New Features + +- We added support for updating a module from a file for module packages created below Studio Pro 11.12.0. After you provide the *.mpk* files, Studio Pro attempts to map documents by name. The update then runs the merge algorithm and, if needed, conflict resolution, so you can keep any customizations made to the module. +- Maia now supports working with **Change Data Capture** documents. +- We now prefix versioned deployment packages with the branch name they were created with: {BranchName}-{AppName}_{Version}.mda +- A module ID can now be passed to the element selector for the `selectedElementId` property, and the corresponding module will be preselected and expanded. This will allow the user to directly create a new document of the desired type in that module. +- We added a capability to **Clear from device** nanoflow action that removes specific objects from the offline device storage. You can now select individual objects or object lists to clear, in addition to clearing all objects of an entity. +- You can now create a branch directly from a specific commit in the History pane by right-clicking the commit and selecting **Create branch...**. +- We added a **Branch line** filter to the **History** pane toolbar. You can now select any branch from a searchable dropdown to view its commit history without switching your working branch. The filter can be cleared with the **×** button or the **Reset filters** button. The **Revert Commit** option is hidden when viewing the history of a branch other than the current one. +- Maia can now answer basic questions about your version control history and commit and push changes to the server. +- We added the ability to filter out the on disk changes on the **Comparison** pane. +- We introduced new fields to the package manifest of module packages. The manifest now indicates the type of the module (source, add-on, or solution) and whether the module contains extensions or AI skills. For more information, see [Package Manifest](/refguide/module-settings/#package-manifest). +- The `mx` command line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (Add-on and Solution) modules. The System module remains excluded. +- The `mx` command line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from the Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy. + ### Improvements @@ -51,26 +53,25 @@ We recommend that projects and Marketplace modules upgrade to Java 25. #### Other Improvements -- Items in the Comparison pane are now sorted by default, first by module and then by document type. +- We improved the sort function in **ListOperation** activity. We now use ICU4J library instead of Java's built-in Collator for sorting lists in microflows. This ensures consistent sorting results in both microflows and nanoflows. (Ticket 263311) +- Items in the **Comparison** pane are now sorted by default, first by module and then by document type. - We now delete the log files generated by Studio Pro that are older than 7 days. - We added support for the following database versions: - MariaDB 12.3 - MySQL 9.7 -- In the logic editors, we improved the way sequence flow arrows are drawn -- In the logic editors, Maia now tries to enforce best practices more strictly. +- In the logic editors, we improved the way sequence flow arrows are drawn. +- In the logic editors, Maia now enforces best practices more strictly. - We added 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 **Maia Skills** pane by updating the filter toggle to use a clearer label ("Show errors only") and more appropriate icons. +- We improved the **Maia Skills** pane by updating the filter toggle to use a clearer label (*Show errors only*) and more appropriate icons. - We updated Maia Agent's visual design to align with EU AI Act compliance guidelines for improved transparency and readability. -- We changed the JSON Structure document editor to open in a tab and not in a dialog. If you encounter any issues, you can revert to the previous editor by deselecting Preferences > New Features > Use the modernized editor for JSON Structure. +- We changed the **JSON Structure** document editor to open in a tab and not in a dialog. If you encounter any issues, you can revert to the previous editor by deselecting **Preferences** > **New Features** > **Use the modernized editor for JSON Structure**. - When logging HTTP requests and responses, the runtime now omits the value of headers Authorization, Cookie, Proxy-Authorization, Set-Cookie, X-Auth-Token and X-Auth-Token where before it only omitted the value of the Authorization header. -- We improved the sort function in `ListOperation` activity. We now use ICU4J library instead of Java's built-in Collator for sorting lists in Microflows. This ensures consistent sorting results in both Microflows and Nanoflows. (Ticket 263311) - We added new `BiConsumer` overloads to `ListenersRegistry`, `ActionListener`, and `EventActionInfo` so that event listener callbacks now receive the active `IContext` alongside the object. The existing `Consumer` methods are deprecated and will be removed in Mendix 12. -- We have upgraded the Java Migration Tool that is downloaded by the Studio Pro installer to version 1.0.2. This versions adds a recipe to fix the deprecated `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the various `ListenersRegistry.register*Listener` methods. - -- You can now use Enter to navigate between Maia's questions and submit your answers without reaching for the mouse. +- We upgraded the Java Migration Tool that is downloaded by the Studio Pro installer to version 1.0.2. This versions adds a recipe to fix the deprecated `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the various `ListenersRegistry.register*Listener` methods. +- You can now use Enter to navigate between Maia's questions and submit your answers without reaching for the mouse. {TW} - We updated Rspack to version 2.1, which reduces bundle times by up to 25%. - We improved React client bundling diagnostics with clearer reporting for memory related bundler failures. -- We reduced the exported bundle size for the React and Native clients when a translatable text (such as a Caption or text template) contains parameters. Only the parts of the text that actually differ between languages are now translated, instead of duplicating the entire text for every language. +- We reduced the exported bundle size for the React and Native clients when a translatable text (such as a caption or text template) contains parameters. Only the parts of the text that actually differ between languages are now translated, instead of duplicating the entire text for every language. {TW} ### Fixes From 2642e6eebd6ff98282fb9b85928b6ffdc3fbf59a Mon Sep 17 00:00:00 2001 From: "MENDIXDOMAIN\\Maria.Shaposhnikova" Date: Tue, 18 Aug 2026 14:51:42 +0200 Subject: [PATCH 4/8] Review Fixes, Deprecations, Breaking Changes --- .../docs/releasenotes/studio-pro/11/11.14.md | 69 +++++++++---------- 1 file changed, 34 insertions(+), 35 deletions(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.14.md b/content/en/docs/releasenotes/studio-pro/11/11.14.md index e0bd662db20..3d9fc5be282 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.14.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.14.md @@ -75,50 +75,49 @@ We recommend that projects and Marketplace modules upgrade to Java 25. ### Fixes -- We fixed an issue where opening the Git preferences would throw an unexpected error when Studio Pro could not load your Git configuration (for example when Git was not installed or its location was set incorrectly). Studio Pro now shows a clear message explaining how to resolve it instead. -- Fixed an issue where activities in microflows generated by Maia showed the default caption **Activity** instead of a caption describing the activity. -- We fixed an issue in React client mode, where snippets would not load properly when navigating to a page with the same snippet. (Ticket 281906) -- We fixed an issue where Studio Pro could incorrectly go into offline mode at startup due to a transient SSL connection failure when fetching the OpenID configuration. -- Fixed an issue where Maia did not create sufficient spacing before and after loops within microflows. -- We fixed an issue where Studio Pro could freeze while a progress dialog is shown, for exammple while opening an app. - -- We fixed an issue where pressing Ctrl+F in the CSS editor or JavaScript editor would open the global Find dialog instead of the editor's built-in search on Windows. (Ticket 283730) -- We fixed an issue where Studio Pro could freeze for up to several seconds during copy operations when another process held a lock on the clipboard. +- We fixed an issue in React client mode, where snippets did not load properly when navigating to a page with the same snippet. (Ticket 281906) +- We fixed an issue where Studio Pro did not update the Java proxies during deployment after renaming a module. (Ticket 282363) +- We fixed an issue where attribute references in microflow expressions were not updated when the attribute was renamed in the domain model. (Tickets 282373, 282363) +- We fixed an issue where pressing Ctrl + F in the CSS editor or JavaScript editor opened the global **Find** dialog instead of the editor's built-in search on Windows. (Ticket 283730) +- We fixed an issue where expanding a folder in a document selector (for example when selecting a microflow, nanoflow, or JSON structure) showed it as expanded but without its contents. (Ticket 284451) +- We fixed an issue where opening the Git preferences threw an unexpected error when Studio Pro could not load your Git configuration (for example when Git was not installed or its location was set incorrectly). Studio Pro now shows a clear message explaining how to resolve it. +- We fixed an issue where activities in microflows generated by Maia showed the default caption **Activity** instead of a caption describing the activity. +- We fixed an issue where Studio Pro incorrectly went into offline mode at startup due to a transient SSL connection failure when fetching the OpenID configuration. +- We fixed an issue where Maia did not create sufficient spacing before and after loops within microflows. +- We fixed an issue where Studio Pro froze while a progress dialog is shown, for exammple while opening an app. +- We fixed an issue where Studio Pro froze for up to several seconds during copy operations when another process held a lock on the clipboard. - We fixed an issue where Studio Pro incorrectly displayed consistency errors after opening an app. -- We fixed an issue where Studio Pro would not update the Java proxies during deployment after renaming a Module. (Ticket #282363) -- We fixed an issue where expanding a folder in a document selector (for example while selecting a microflow, nanoflow, or JSON structure) would show it as expanded but without its contents. (Ticket #284451) -- We fixed an issue where the active document's tab could get scrolled out of view after opening many documents in a row. -- We fixed an issue where renaming in Studio Pro of e.g. a module or an entity could lead to consistency errors in Microflow expressions. +- 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 a module or an entity led to consistency errors in microflow expressions. - We fixed an issue where Maia named single objects returned from a **Retrieve Action** as "{entity}List". -- Fixed custom icon visibility for exposed microflow, Java and Javascript actions based on icon availibility and selected Studio Pro theme. -- Fixed an issue where attribute references in microflow expressions were not updated when the attribute was renamed in the **Domain Model**. (Tickets 282373, 282363) -- Fixed an issue where the in-editor Recommender dialog still appeared for empty microflows, nanoflows, and rules after all Recommender features were disabled in **Preferences → AI**. -- Fixed an issue where the content of the Microflow editor and Domain Model editor (Beta) canvas could appear blurry after scrolling or zooming. -- We fixed an issue where the "Push your changes" notification bar was incorrectly shown after a merge or cherry-pick that produced no actual model changes. Studio Pro now detects this scenario and shows an informational message instead. -- We fixed an issue where some grid cells in Studio Pro would become empty while scrolling the grid. -- Fixed an issue where concurrent git operations could fail with an "index is locked" error when the version control status bar polled for conflict information at the same time as write operations such as reset or checkout. -- We resolved an issue where using **Undo All** in the Changes pane did not remove the overview pages generated by **Start with Maia**. -- Fixed Maia's inability to create While loops. -- We fixed an issue in the MCP settings panel where the **Enable all** and **Disable all** buttons remained clickable even when all tools were already in that state. The buttons are now disabled when they would have no effect. +- We fixed custom icon visibility for an exposed microflow, Java and Javascript actions based on icon availibility and selected Studio Pro theme. +- We fixed an issue where the in-editor Recommender dialog still appeared for empty microflows, nanoflows, and rules after all Recommender features were disabled in **Preferences** > **AI**. +- We fixed an issue where the content of the Microflow editor and domain model editor (Beta) canvas appeared blurry after scrolling or zooming. +- We fixed an issue where the **Push your changes** notification bar was incorrectly shown after a merge or cherry-pick that produced no actual model changes. Studio Pro now detects this scenario and shows an informational message instead. +- We fixed an issue where some grid cells in Studio Pro became empty while scrolling the grid. +- We fixed an issue where concurrent Git operations failed with an *index is locked* error when the version control status bar polled for conflict information at the same time as write operations such as reset or checkout. +- We resolved an issue where using **Undo All** in the **Changes** pane did not remove the overview pages generated by **Start with Maia**. +- We fixed Maia's inability to create *While* loops. +- We fixed an issue in the MCP settings pane where the **Enable all** and **Disable all** buttons remained clickable even when all tools were already in that state. The buttons are now disabled when they have no effect. - We have fixed an issue where text box values filled in by a password manager were not registered. (Ticket 284395, 283505) -- Fixed an error in offline-first (PWA) apps when a list view with an association data source was opened for a context object that had not been synchronized yet. (Ticket #283531) -- Fixed an error in offline-first (PWA) apps on iOS 26.5.2 and later, where synchronizing a newly added image or file document failed because its contents were not included in the upload. (Ticket #248368) -- We removed the theme.compiled.css.map from the deployment package due to privacy and security concerns +- We fixed an error in offline-first (PWA) apps when a list view with an association data source was opened for a context object that had not been synchronized yet. (Ticket 283531) +- We fixed an error in offline-first (PWA) apps on iOS 26.5.2 and above, where synchronizing a newly added image or file document failed because its contents were not included in the upload. (Ticket 248368) +- We removed the *theme.compiled.css.map* from the deployment package due to privacy and security concerns - We fixed an issue where date filters sent to OData services with DateTimeOffset attributes contained the wrong date format, causing the remote service to reject the request. - We fixed an issue in Studio Pro where publishing a microflow in a new a REST service allowed adding that service to read-only modules such as the System module. -- We fixed an issue that when opening a non version controlled application after version controlled one, comparison pane was showing old comparison data. -- We fixed an issue where Studio Pro could appear frozen when marking or unmarking a module as a UI resources module. A progress dialog is now shown while the app is synchronized with the file system. -- We fixed an issue in the modernized App Explorer where Studio Pro could appear unresponsive after moving documents or folders. A progress dialog is now shown until the App Explorer has finished updating. -- Fixed an issue in the modernized Find Results panel where closed result sets could reappear and the displayed number of open result sets could be incorrect. +- We fixed an issue that when opening a non-version controlled application after version controlled one, the **Comparison** pane was showing old comparison data. +- We fixed an issue where Studio Pro appeared frozen when marking or unmarking a module as a UI resources module. A progress dialog is now shown while the app is synchronized with the file system. +- We fixed an issue in the modernized App Explorer where Studio Pro appeared unresponsive after moving documents or folders. A progress dialog is now shown until the App Explorer has finished updating. +- We fixed an issue in the modernized **Find Results** pane where closed result sets reappeared and the displayed number of open result sets were incorrect. - We fixed an issue in the modernized App Explorer where actions triggered with keyboard shortcuts could apply to the previously selected node. -- We fixed an issue where JavaScript actions with npm dependencies installed in their `actions/node_modules` folder could fail to bundle in the React client, for both the Rollup and Rspack bundlers. (Ticket 283840) -- We fixed an issue where pressing Escape to close a modal dialog would also close the sidebar. -- Fixed an issue in the microflow editor where sometimes the loop would be selected when trying to select elements inside of the loop. -- We fixed an issue where an editable condition set to Never could be lost during widget conversion. (Ticket 283552) +- 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 pressing Escape to close a modal dialog also closed the sidebar. +- We fixed an issue in the microflow editor where sometimes the loop was selected when trying to select elements inside of the loop. +- We fixed an issue where an editable condition set to *Never* was lost during widget conversion. (Ticket 283552) ### Deprecations -- We have deprecated support for Java 21. Support for Java 21 will be dropped in the future. We recommend to use Java 25. +- We deprecated support for Java 21. Support for Java 21 will be dropped in the future. We recommend using Java 25. - The `Consumer` overloads of `ListenersRegistry.register*Listener`, `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the matching `EventActionInfo` constructors are deprecated since Mendix 11.14.0 and will be removed in Mendix 12. Use the `BiConsumer` overloads instead, which also provide the active context to the callback. ### Breaking Changes From eb2372149d28c1280bf3d06293aa0fbe918463ae Mon Sep 17 00:00:00 2001 From: "MENDIXDOMAIN\\Maria.Shaposhnikova" Date: Tue, 18 Aug 2026 15:15:51 +0200 Subject: [PATCH 5/8] Review --- content/en/docs/.claude/settings.local.json | 7 ++ .../docs/releasenotes/studio-pro/11/11.14.md | 66 +++++++++---------- 2 files changed, 40 insertions(+), 33 deletions(-) create mode 100644 content/en/docs/.claude/settings.local.json diff --git a/content/en/docs/.claude/settings.local.json b/content/en/docs/.claude/settings.local.json new file mode 100644 index 00000000000..00b310a2102 --- /dev/null +++ b/content/en/docs/.claude/settings.local.json @@ -0,0 +1,7 @@ +{ + "permissions": { + "allow": [ + "Read(//c/Users/Maria.Shaposhnikova/Documents/docs/releasenotes/studio-pro/11/**)" + ] + } +} diff --git a/content/en/docs/releasenotes/studio-pro/11/11.14.md b/content/en/docs/releasenotes/studio-pro/11/11.14.md index 3d9fc5be282..39e980b9965 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.14.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.14.md @@ -34,15 +34,15 @@ We recommend that projects and Marketplace modules upgrade to Java 25. - We added support for updating a module from a file for module packages created below Studio Pro 11.12.0. After you provide the *.mpk* files, Studio Pro attempts to map documents by name. The update then runs the merge algorithm and, if needed, conflict resolution, so you can keep any customizations made to the module. - Maia now supports working with **Change Data Capture** documents. - We now prefix versioned deployment packages with the branch name they were created with: {BranchName}-{AppName}_{Version}.mda -- A module ID can now be passed to the element selector for the `selectedElementId` property, and the corresponding module will be preselected and expanded. This will allow the user to directly create a new document of the desired type in that module. -- We added a capability to **Clear from device** nanoflow action that removes specific objects from the offline device storage. You can now select individual objects or object lists to clear, in addition to clearing all objects of an entity. -- You can now create a branch directly from a specific commit in the History pane by right-clicking the commit and selecting **Create branch...**. +- A module ID can now be passed to the element selector for the `selectedElementId` property, and the corresponding module is preselected and expanded. This allows you to directly create a new document of the desired type in that module. +- We added a capability to the **Clear from device** nanoflow action that removes specific objects from the offline device storage. You can now select individual objects or object lists to clear, in addition to clearing all objects of an entity. +- You can now create a branch directly from a specific commit in the **History** pane by right-clicking the commit and selecting **Create branch...**. - We added a **Branch line** filter to the **History** pane toolbar. You can now select any branch from a searchable dropdown to view its commit history without switching your working branch. The filter can be cleared with the **×** button or the **Reset filters** button. The **Revert Commit** option is hidden when viewing the history of a branch other than the current one. - Maia can now answer basic questions about your version control history and commit and push changes to the server. -- We added the ability to filter out the on disk changes on the **Comparison** pane. +- We added the ability to filter out the on-disk changes on the **Comparison** pane. - We introduced new fields to the package manifest of module packages. The manifest now indicates the type of the module (source, add-on, or solution) and whether the module contains extensions or AI skills. For more information, see [Package Manifest](/refguide/module-settings/#package-manifest). -- The `mx` command line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (Add-on and Solution) modules. The System module remains excluded. -- The `mx` command line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from the Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy. +- The `mx` command-line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (add-on and solution) modules. The System module remains excluded. +- The `mx` command-line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the Marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy. ### Improvements @@ -53,72 +53,72 @@ We recommend that projects and Marketplace modules upgrade to Java 25. #### Other Improvements -- We improved the sort function in **ListOperation** activity. We now use ICU4J library instead of Java's built-in Collator for sorting lists in microflows. This ensures consistent sorting results in both microflows and nanoflows. (Ticket 263311) +- We improved the sort function in the **ListOperation** activity. We now use the ICU4J library instead of Java's built-in Collator for sorting lists in microflows. This ensures consistent sorting results in both microflows and nanoflows. (Ticket 263311) - Items in the **Comparison** pane are now sorted by default, first by module and then by document type. -- We now delete the log files generated by Studio Pro that are older than 7 days. +- We now delete the log files generated by Studio Pro that are older than seven days. - We added support for the following database versions: - - MariaDB 12.3 - - MySQL 9.7 + - MariaDB 12.3 + - MySQL 9.7 - In the logic editors, we improved the way sequence flow arrows are drawn. - In the logic editors, Maia now enforces best practices more strictly. -- We added 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 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 **Maia Skills** pane by updating the filter toggle to use a clearer label (*Show errors only*) and more appropriate icons. - We updated Maia Agent's visual design to align with EU AI Act compliance guidelines for improved transparency and readability. -- We changed the **JSON Structure** document editor to open in a tab and not in a dialog. If you encounter any issues, you can revert to the previous editor by deselecting **Preferences** > **New Features** > **Use the modernized editor for JSON Structure**. -- When logging HTTP requests and responses, the runtime now omits the value of headers Authorization, Cookie, Proxy-Authorization, Set-Cookie, X-Auth-Token and X-Auth-Token where before it only omitted the value of the Authorization header. +- We changed the **JSON Structure** document editor to open in a tab instead of a dialog. If you encounter any issues, you can revert to the previous editor by clearing **Preferences** > **New Features** > **Use the modernized editor for JSON Structure**. +- When logging HTTP requests and responses, the Mendix Runtime now omits the value of the Authorization, Cookie, Proxy-Authorization, Set-Cookie, and X-Auth-Token headers, whereas previously it only omitted the value of the Authorization header. - We added new `BiConsumer` overloads to `ListenersRegistry`, `ActionListener`, and `EventActionInfo` so that event listener callbacks now receive the active `IContext` alongside the object. The existing `Consumer` methods are deprecated and will be removed in Mendix 12. -- We upgraded the Java Migration Tool that is downloaded by the Studio Pro installer to version 1.0.2. This versions adds a recipe to fix the deprecated `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the various `ListenersRegistry.register*Listener` methods. +- We upgraded the Java Migration Tool that is downloaded by the Studio Pro installer to version 1.0.2. This version adds a recipe to fix the deprecated `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the various `ListenersRegistry.register*Listener` methods. - You can now use Enter to navigate between Maia's questions and submit your answers without reaching for the mouse. {TW} - We updated Rspack to version 2.1, which reduces bundle times by up to 25%. -- We improved React client bundling diagnostics with clearer reporting for memory related bundler failures. +- We improved React client bundling diagnostics with clearer reporting for memory-related bundler failures. - We reduced the exported bundle size for the React and Native clients when a translatable text (such as a caption or text template) contains parameters. Only the parts of the text that actually differ between languages are now translated, instead of duplicating the entire text for every language. {TW} ### Fixes -- We fixed an issue in React client mode, where snippets did not load properly when navigating to a page with the same snippet. (Ticket 281906) +- We fixed an error in offline-first (PWA) apps on iOS 26.5.2 and above where synchronizing a newly added image or file document failed because its contents were not included in the upload. (Ticket 248368) +- We fixed an issue in React client mode where snippets did not load properly when navigating to a page with the same snippet. (Ticket 281906) - We fixed an issue where Studio Pro did not update the Java proxies during deployment after renaming a module. (Ticket 282363) - We fixed an issue where attribute references in microflow expressions were not updated when the attribute was renamed in the domain model. (Tickets 282373, 282363) +- We fixed an error in offline-first (PWA) apps when a list view with an association data source was opened for a context object that had not been synchronized yet. (Ticket 283531) +- We fixed an issue where an editable condition set to *Never* was lost during widget conversion. (Ticket 283552) - We fixed an issue where pressing Ctrl + F in the CSS editor or JavaScript editor opened the global **Find** dialog instead of the editor's built-in search on Windows. (Ticket 283730) -- We fixed an issue where expanding a folder in a document selector (for example when selecting a microflow, nanoflow, or JSON structure) showed it as expanded but without its contents. (Ticket 284451) -- We fixed an issue where opening the Git preferences threw an unexpected error when Studio Pro could not load your Git configuration (for example when Git was not installed or its location was set incorrectly). Studio Pro now shows a clear message explaining how to resolve it. +- 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. (Ticket 284395, 283505) +- We fixed an issue where expanding a folder in a document selector (for example, when selecting a microflow, nanoflow, or JSON structure) showed it as expanded but without its contents. (Ticket 284451) +- We fixed an issue where opening the Git preferences threw an unexpected error when Studio Pro could not load your Git configuration (for example, when Git was not installed or its location was set incorrectly). Studio Pro now shows a clear message explaining how to resolve it. - We fixed an issue where activities in microflows generated by Maia showed the default caption **Activity** instead of a caption describing the activity. - We fixed an issue where Studio Pro incorrectly went into offline mode at startup due to a transient SSL connection failure when fetching the OpenID configuration. - We fixed an issue where Maia did not create sufficient spacing before and after loops within microflows. -- We fixed an issue where Studio Pro froze while a progress dialog is shown, for exammple while opening an app. +- 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 Studio Pro froze for up to several seconds during copy operations when another process held a lock on the clipboard. - We fixed an issue where Studio Pro incorrectly displayed consistency errors after 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 a module or an entity led to consistency errors in microflow expressions. - We fixed an issue where Maia named single objects returned from a **Retrieve Action** as "{entity}List". -- We fixed custom icon visibility for an exposed microflow, Java and Javascript actions based on icon availibility and selected Studio Pro theme. +- We fixed custom icon visibility for an exposed microflow, Java and JavaScript actions based on icon availability and selected Studio Pro theme. - We fixed an issue where the in-editor Recommender dialog still appeared for empty microflows, nanoflows, and rules after all Recommender features were disabled in **Preferences** > **AI**. -- We fixed an issue where the content of the Microflow editor and domain model editor (Beta) canvas appeared blurry after scrolling or zooming. +- We fixed an issue where the content of the microflow editor and domain model editor (Beta) canvas appeared blurry after scrolling or zooming. - We fixed an issue where the **Push your changes** notification bar was incorrectly shown after a merge or cherry-pick that produced no actual model changes. Studio Pro now detects this scenario and shows an informational message instead. - We fixed an issue where some grid cells in Studio Pro became empty while scrolling the grid. - We fixed an issue where concurrent Git operations failed with an *index is locked* error when the version control status bar polled for conflict information at the same time as write operations such as reset or checkout. - We resolved an issue where using **Undo All** in the **Changes** pane did not remove the overview pages generated by **Start with Maia**. - We fixed Maia's inability to create *While* loops. - We fixed an issue in the MCP settings pane where the **Enable all** and **Disable all** buttons remained clickable even when all tools were already in that state. The buttons are now disabled when they have no effect. -- We have fixed an issue where text box values filled in by a password manager were not registered. (Ticket 284395, 283505) -- We fixed an error in offline-first (PWA) apps when a list view with an association data source was opened for a context object that had not been synchronized yet. (Ticket 283531) -- We fixed an error in offline-first (PWA) apps on iOS 26.5.2 and above, where synchronizing a newly added image or file document failed because its contents were not included in the upload. (Ticket 248368) -- We removed the *theme.compiled.css.map* from the deployment package due to privacy and security concerns +- We removed the *theme.compiled.css.map* from the deployment package due to privacy and security concerns. - We fixed an issue where date filters sent to OData services with DateTimeOffset attributes contained the wrong date format, causing the remote service to reject the request. -- We fixed an issue in Studio Pro where publishing a microflow in a new a REST service allowed adding that service to read-only modules such as the System module. -- We fixed an issue that when opening a non-version controlled application after version controlled one, the **Comparison** pane was showing old comparison data. +- We fixed an issue in Studio Pro where publishing a microflow in a new REST service allowed adding that service to read-only modules such as the System module. +- We fixed an issue where opening a non-version-controlled app after a version-controlled one, the **Comparison** pane was showing old comparison data. - We fixed an issue where Studio Pro appeared frozen when marking or unmarking a module as a UI resources module. A progress dialog is now shown while the app is synchronized with the file system. - We fixed an issue in the modernized App Explorer where Studio Pro appeared unresponsive after moving documents or folders. A progress dialog is now shown until the App Explorer has finished updating. -- We fixed an issue in the modernized **Find Results** pane where closed result sets reappeared and the displayed number of open result sets were incorrect. +- We fixed an issue in the modernized **Find Results** pane where closed result sets reappeared and the displayed number of open result sets was incorrect. - We fixed an issue in the modernized App Explorer where actions triggered with keyboard shortcuts could apply to the previously selected node. -- 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 pressing Escape to close a modal dialog also closed the sidebar. -- We fixed an issue in the microflow editor where sometimes the loop was selected when trying to select elements inside of the loop. -- We fixed an issue where an editable condition set to *Never* was lost during widget conversion. (Ticket 283552) +- We fixed an issue in the microflow editor where sometimes the loop was selected when trying to select elements inside the loop. ### Deprecations -- We deprecated support for Java 21. Support for Java 21 will be dropped in the future. We recommend using Java 25. -- The `Consumer` overloads of `ListenersRegistry.register*Listener`, `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the matching `EventActionInfo` constructors are deprecated since Mendix 11.14.0 and will be removed in Mendix 12. Use the `BiConsumer` overloads instead, which also provide the active context to the callback. +- We deprecated support for Java 21. Support for Java 21 will be removed in the future. Mendix recommends using Java 25. +- The `Consumer` overloads of `ListenersRegistry.register*Listener`, `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the matching `EventActionInfo` constructors are deprecated as of Mendix 11.14.0 and will be removed in Mendix 12. Use the `BiConsumer` overloads instead, which also provide the active context to the callback. ### Breaking Changes From 524bb2fe512b0a49d315d1f3500fabdb205ba4f4 Mon Sep 17 00:00:00 2001 From: "MENDIXDOMAIN\\Maria.Shaposhnikova" Date: Tue, 18 Aug 2026 15:23:06 +0200 Subject: [PATCH 6/8] Align fixes with previous versions --- content/en/docs/releasenotes/studio-pro/11/11.14.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.14.md b/content/en/docs/releasenotes/studio-pro/11/11.14.md index 39e980b9965..5c38a712ec7 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.14.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.14.md @@ -75,13 +75,13 @@ We recommend that projects and Marketplace modules upgrade to Java 25. ### Fixes -- We fixed an error in offline-first (PWA) apps on iOS 26.5.2 and above where synchronizing a newly added image or file document failed because its contents were not included in the upload. (Ticket 248368) -- We fixed an issue in React client mode where snippets did not load properly when navigating to a page with the same snippet. (Ticket 281906) +- We fixed an error in offline-first (PWA) apps on iOS 26.5.2 and above, where synchronizing a newly added image or file document failed because its contents were not included in the upload. (Ticket 248368) +- We fixed an issue in the React client mode where snippets did not load properly when navigating to a page with the same snippet. (Ticket 281906) - We fixed an issue where Studio Pro did not update the Java proxies during deployment after renaming a module. (Ticket 282363) - We fixed an issue where attribute references in microflow expressions were not updated when the attribute was renamed in the domain model. (Tickets 282373, 282363) - We fixed an error in offline-first (PWA) apps when a list view with an association data source was opened for a context object that had not been synchronized yet. (Ticket 283531) -- We fixed an issue where an editable condition set to *Never* was lost during widget conversion. (Ticket 283552) -- We fixed an issue where pressing Ctrl + F in the CSS editor or JavaScript editor opened the global **Find** dialog instead of the editor's built-in search on Windows. (Ticket 283730) +- We fixed an issue where an editable condition set to **Never** was lost during widget conversion. (Ticket 283552) +- We fixed an issue on Windows where pressing Ctrl + F in the CSS editor or JavaScript editor opened the global **Find** dialog instead of the editor's built-in search. (Ticket 283730) - 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. (Ticket 284395, 283505) - We fixed an issue where expanding a folder in a document selector (for example, when selecting a microflow, nanoflow, or JSON structure) showed it as expanded but without its contents. (Ticket 284451) From d363806f5fc8be03f14c5013082ba406d20ef1d3 Mon Sep 17 00:00:00 2001 From: "MENDIXDOMAIN\\Maria.Shaposhnikova" Date: Wed, 19 Aug 2026 15:08:03 +0200 Subject: [PATCH 7/8] Review --- .../docs/releasenotes/studio-pro/11/11.14.md | 162 +++++++++--------- 1 file changed, 81 insertions(+), 81 deletions(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.14.md b/content/en/docs/releasenotes/studio-pro/11/11.14.md index 5c38a712ec7..b5ee0344fb0 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.14.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.14.md @@ -19,109 +19,109 @@ weight: 86 #### Java 25 We now support Java 25 in Studio Pro. -- This release ships with Java Development Kit (JDK) 25 and Gradle 9.5.1. -- You can now configure your application to use Java 25 in the project settings. -- In the Studio Preferences you can configure a different JDK for each supported version of Java. -- Targeting Java 25 allows the project to use language constructs and APIs that were introduced with Java 25. -- Newly created projects will be configured to use Java 25 by default. -- Gradle 9.5.1 supports both Java 21 and 25. Java 25 requires Gradle 9.1+. -- Support for Java 21 is deprecated. +* This release ships with Java Development Kit (JDK) 25 and Gradle 9.5.1. +* You can now configure your application to use Java 25 in the project settings. +* In the Studio Preferences you can configure a different JDK for each supported version of Java. +* Targeting Java 25 allows the project to use language constructs and APIs that were introduced with Java 25. +* Newly created projects will be configured to use Java 25 by default. +* Gradle 9.5.1 supports both Java 21 and 25. Java 25 requires Gradle 9.1+. +* Support for Java 21 is deprecated. We recommend that projects and Marketplace modules upgrade to Java 25. #### Other New Features -- We added support for updating a module from a file for module packages created below Studio Pro 11.12.0. After you provide the *.mpk* files, Studio Pro attempts to map documents by name. The update then runs the merge algorithm and, if needed, conflict resolution, so you can keep any customizations made to the module. -- Maia now supports working with **Change Data Capture** documents. -- We now prefix versioned deployment packages with the branch name they were created with: {BranchName}-{AppName}_{Version}.mda -- A module ID can now be passed to the element selector for the `selectedElementId` property, and the corresponding module is preselected and expanded. This allows you to directly create a new document of the desired type in that module. -- We added a capability to the **Clear from device** nanoflow action that removes specific objects from the offline device storage. You can now select individual objects or object lists to clear, in addition to clearing all objects of an entity. -- You can now create a branch directly from a specific commit in the **History** pane by right-clicking the commit and selecting **Create branch...**. -- We added a **Branch line** filter to the **History** pane toolbar. You can now select any branch from a searchable dropdown to view its commit history without switching your working branch. The filter can be cleared with the **×** button or the **Reset filters** button. The **Revert Commit** option is hidden when viewing the history of a branch other than the current one. -- Maia can now answer basic questions about your version control history and commit and push changes to the server. -- We added the ability to filter out the on-disk changes on the **Comparison** pane. -- We introduced new fields to the package manifest of module packages. The manifest now indicates the type of the module (source, add-on, or solution) and whether the module contains extensions or AI skills. For more information, see [Package Manifest](/refguide/module-settings/#package-manifest). -- The `mx` command-line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (add-on and solution) modules. The System module remains excluded. -- The `mx` command-line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the Marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy. +* We added support for updating a module from a file for module packages created below Studio Pro 11.12.0. After you provide the *.mpk* files, Studio Pro attempts to map documents by name. The update then runs the merge algorithm and, if needed, conflict resolution, so you can keep any customizations made to the module. +* Maia now supports working with **Change Data Capture** documents. +* We now prefix versioned deployment packages with the branch name they were created with: {BranchName}-{AppName}_{Version}.mda +* A module ID can now be passed to the element selector for the `selectedElementId` property, and the corresponding module is preselected and expanded. This allows you to directly create a new document of the desired type in that module. +* We added a capability to the **Clear from device** nanoflow action that removes specific objects from the offline device storage. You can now select individual objects or object lists to clear, in addition to clearing all objects of an entity. +* You can now create a branch directly from a specific commit in the **History** pane by right-clicking the commit and selecting **Create branch...**. +* We added a **Branch line** filter to the **History** pane toolbar. You can now select any branch from a searchable dropdown to view its commit history without switching your working branch. The filter can be cleared with the **×** button or the **Reset filters** button. The **Revert Commit** option is hidden when viewing the history of a branch other than the current one. +* Maia can now answer basic questions about your version control history and commit and push changes to the server. +* We added the ability to filter out the on-disk changes on the **Comparison** pane. +* We introduced new fields to the package manifest of module packages. The manifest now indicates the type of the module (source, add-on, or solution) and whether the module contains extensions or AI skills. For more information, see [Package Manifest](/refguide/module-settings/#package-manifest). +* The `mx` command-line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (add-on and solution) modules. The System module remains excluded. +* The `mx` command-line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the Marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy. ### Improvements #### Performance -- We improved build performance and reduced memory usage of the React client when bundling with Rspack. (Ticket 282716, 282165, 282605) +* We improved build performance and reduced memory usage of the React client when bundling with Rspack. (Ticket 282716, 282165, 282605) #### Other Improvements -- We improved the sort function in the **ListOperation** activity. We now use the ICU4J library instead of Java's built-in Collator for sorting lists in microflows. This ensures consistent sorting results in both microflows and nanoflows. (Ticket 263311) -- Items in the **Comparison** pane are now sorted by default, first by module and then by document type. -- We now delete the log files generated by Studio Pro that are older than seven days. -- We added support for the following database versions: - - MariaDB 12.3 - - MySQL 9.7 -- In the logic editors, we improved the way sequence flow arrows are drawn. -- In the logic editors, Maia now enforces best practices more strictly. -- 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 **Maia Skills** pane by updating the filter toggle to use a clearer label (*Show errors only*) and more appropriate icons. -- We updated Maia Agent's visual design to align with EU AI Act compliance guidelines for improved transparency and readability. -- We changed the **JSON Structure** document editor to open in a tab instead of a dialog. If you encounter any issues, you can revert to the previous editor by clearing **Preferences** > **New Features** > **Use the modernized editor for JSON Structure**. -- When logging HTTP requests and responses, the Mendix Runtime now omits the value of the Authorization, Cookie, Proxy-Authorization, Set-Cookie, and X-Auth-Token headers, whereas previously it only omitted the value of the Authorization header. -- We added new `BiConsumer` overloads to `ListenersRegistry`, `ActionListener`, and `EventActionInfo` so that event listener callbacks now receive the active `IContext` alongside the object. The existing `Consumer` methods are deprecated and will be removed in Mendix 12. -- We upgraded the Java Migration Tool that is downloaded by the Studio Pro installer to version 1.0.2. This version adds a recipe to fix the deprecated `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the various `ListenersRegistry.register*Listener` methods. -- You can now use Enter to navigate between Maia's questions and submit your answers without reaching for the mouse. {TW} -- We updated Rspack to version 2.1, which reduces bundle times by up to 25%. -- We improved React client bundling diagnostics with clearer reporting for memory-related bundler failures. -- We reduced the exported bundle size for the React and Native clients when a translatable text (such as a caption or text template) contains parameters. Only the parts of the text that actually differ between languages are now translated, instead of duplicating the entire text for every language. {TW} +* We improved the sort function in the **ListOperation** activity. We now use the ICU4J library instead of Java's built-in Collator for sorting lists in microflows. This ensures consistent sorting results in both microflows and nanoflows. (Ticket 263311) +* Items in the **Comparison** pane are now sorted by default, first by module and then by document type. +* We now delete the log files generated by Studio Pro that are older than seven days. +* We added support for the following database versions: + * MariaDB 12.3 + * MySQL 9.7 +* In the logic editors, we improved the way sequence flow arrows are drawn. +* In the logic editors, Maia now enforces best practices more strictly. +* 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 **Maia Skills** pane by updating the filter toggle to use a clearer label (*Show errors only*) and more appropriate icons. +* We updated Maia Agent's visual design to align with EU AI Act compliance guidelines for improved transparency and readability. +* We changed the **JSON Structure** document editor to open in a tab instead of a dialog. If you encounter any issues, you can revert to the previous editor by clearing **Preferences** > **New Features** > **Use the modernized editor for JSON Structure**. +* When logging HTTP requests and responses, the Mendix Runtime now omits the value of the Authorization, Cookie, Proxy-Authorization, Set-Cookie, and X-Auth-Token headers, whereas previously it only omitted the value of the Authorization header. +* We added new `BiConsumer` overloads to `ListenersRegistry`, `ActionListener`, and `EventActionInfo` so that event listener callbacks now receive the active `IContext` alongside the object. The existing `Consumer` methods are deprecated and will be removed in Mendix 12. +* We upgraded the Java Migration Tool that is downloaded by the Studio Pro installer to version 1.0.2. This version adds a recipe to fix the deprecated `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the various `ListenersRegistry.register*Listener` methods. +* You can now use Enter to navigate between Maia's questions and submit your answers without using a mouse. +* We updated Rspack to version 2.1, which reduces bundle times by up to 25%. +* We improved React client bundling diagnostics with clearer reporting for memory-related bundler failures. +* We reduced the exported bundle size for the React and Native clients when a translatable text (such as a caption or text template) contains parameters. Only the parts of the text that actually differ between languages are now translated, instead of duplicating the entire text for every language. ### Fixes -- We fixed an error in offline-first (PWA) apps on iOS 26.5.2 and above, where synchronizing a newly added image or file document failed because its contents were not included in the upload. (Ticket 248368) -- We fixed an issue in the React client mode where snippets did not load properly when navigating to a page with the same snippet. (Ticket 281906) -- We fixed an issue where Studio Pro did not update the Java proxies during deployment after renaming a module. (Ticket 282363) -- We fixed an issue where attribute references in microflow expressions were not updated when the attribute was renamed in the domain model. (Tickets 282373, 282363) -- We fixed an error in offline-first (PWA) apps when a list view with an association data source was opened for a context object that had not been synchronized yet. (Ticket 283531) -- We fixed an issue where an editable condition set to **Never** was lost during widget conversion. (Ticket 283552) -- We fixed an issue on Windows where pressing Ctrl + F in the CSS editor or JavaScript editor opened the global **Find** dialog instead of the editor's built-in search. (Ticket 283730) -- 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. (Ticket 284395, 283505) -- We fixed an issue where expanding a folder in a document selector (for example, when selecting a microflow, nanoflow, or JSON structure) showed it as expanded but without its contents. (Ticket 284451) -- We fixed an issue where opening the Git preferences threw an unexpected error when Studio Pro could not load your Git configuration (for example, when Git was not installed or its location was set incorrectly). Studio Pro now shows a clear message explaining how to resolve it. -- We fixed an issue where activities in microflows generated by Maia showed the default caption **Activity** instead of a caption describing the activity. -- We fixed an issue where Studio Pro incorrectly went into offline mode at startup due to a transient SSL connection failure when fetching the OpenID configuration. -- We fixed an issue where Maia did not create sufficient spacing before and after loops within microflows. -- 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 Studio Pro froze for up to several seconds during copy operations when another process held a lock on the clipboard. -- We fixed an issue where Studio Pro incorrectly displayed consistency errors after 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 a module or an entity led to consistency errors in microflow expressions. -- We fixed an issue where Maia named single objects returned from a **Retrieve Action** as "{entity}List". -- We fixed custom icon visibility for an exposed microflow, Java and JavaScript actions based on icon availability and selected Studio Pro theme. -- We fixed an issue where the in-editor Recommender dialog still appeared for empty microflows, nanoflows, and rules after all Recommender features were disabled in **Preferences** > **AI**. -- We fixed an issue where the content of the microflow editor and domain model editor (Beta) canvas appeared blurry after scrolling or zooming. -- We fixed an issue where the **Push your changes** notification bar was incorrectly shown after a merge or cherry-pick that produced no actual model changes. Studio Pro now detects this scenario and shows an informational message instead. -- We fixed an issue where some grid cells in Studio Pro became empty while scrolling the grid. -- We fixed an issue where concurrent Git operations failed with an *index is locked* error when the version control status bar polled for conflict information at the same time as write operations such as reset or checkout. -- We resolved an issue where using **Undo All** in the **Changes** pane did not remove the overview pages generated by **Start with Maia**. -- We fixed Maia's inability to create *While* loops. -- We fixed an issue in the MCP settings pane where the **Enable all** and **Disable all** buttons remained clickable even when all tools were already in that state. The buttons are now disabled when they have no effect. -- We removed the *theme.compiled.css.map* from the deployment package due to privacy and security concerns. -- We fixed an issue where date filters sent to OData services with DateTimeOffset attributes contained the wrong date format, causing the remote service to reject the request. -- We fixed an issue in Studio Pro where publishing a microflow in a new REST service allowed adding that service to read-only modules such as the System module. -- We fixed an issue where opening a non-version-controlled app after a version-controlled one, the **Comparison** pane was showing old comparison data. -- We fixed an issue where Studio Pro appeared frozen when marking or unmarking a module as a UI resources module. A progress dialog is now shown while the app is synchronized with the file system. -- We fixed an issue in the modernized App Explorer where Studio Pro appeared unresponsive after moving documents or folders. A progress dialog is now shown until the App Explorer has finished updating. -- We fixed an issue in the modernized **Find Results** pane where closed result sets reappeared and the displayed number of open result sets was incorrect. -- We fixed an issue in the modernized App Explorer where actions triggered with keyboard shortcuts could apply to the previously selected node. -- We fixed an issue where pressing Escape to close a modal dialog also closed the sidebar. -- We fixed an issue in the microflow editor where sometimes the loop was selected when trying to select elements inside the loop. +* We fixed an error in offline-first (PWA) apps on iOS 26.5.2 and above, where synchronizing a newly added image or file document failed because its contents were not included in the upload. (Ticket 248368) +* We fixed an issue in the React client mode where snippets did not load properly when navigating to a page with the same snippet. (Ticket 281906) +* We fixed an issue where Studio Pro did not update the Java proxies during deployment after renaming a module. (Ticket 282363) +* We fixed an issue where attribute references in microflow expressions were not updated when the attribute was renamed in the domain model. (Tickets 282373, 282363) +* We fixed an error in offline-first (PWA) apps when a list view with an association data source was opened for a context object that had not been synchronized yet. (Ticket 283531) +* We fixed an issue where an editable condition set to **Never** was lost during widget conversion. (Ticket 283552) +* We fixed an issue on Windows where pressing Ctrl + F in the CSS editor or JavaScript editor opened the global **Find** dialog instead of the editor's built-in search. (Ticket 283730) +* 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. (Ticket 284395, 283505) +* We fixed an issue where expanding a folder in a document selector (for example, when selecting a microflow, nanoflow, or JSON structure) showed it as expanded but without its contents. (Ticket 284451) +* We fixed an issue where opening the Git preferences threw an unexpected error when Studio Pro could not load your Git configuration (for example, when Git was not installed or its location was set incorrectly). Studio Pro now shows a clear message explaining how to resolve it. +* We fixed an issue where activities in microflows generated by Maia showed the default caption **Activity** instead of a caption describing the activity. +* We fixed an issue where Studio Pro incorrectly went into offline mode at startup due to a transient SSL connection failure when fetching the OpenID configuration. +* We fixed an issue where Maia did not create sufficient spacing before and after loops within microflows. +* 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 Studio Pro froze for up to several seconds during copy operations when another process held a lock on the clipboard. +* We fixed an issue where Studio Pro incorrectly displayed consistency errors after 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 a module or an entity led to consistency errors in microflow expressions. +* We fixed an issue where Maia named single objects returned from a **Retrieve Action** as "{entity}List". +* We fixed custom icon visibility for an exposed microflow, Java and JavaScript actions based on icon availability and selected Studio Pro theme. +* We fixed an issue where the in-editor Recommender dialog still appeared for empty microflows, nanoflows, and rules after all Recommender features were disabled in **Preferences** > **AI**. +* We fixed an issue where the content of the microflow editor and domain model editor (Beta) canvas appeared blurry after scrolling or zooming. +* We fixed an issue where the **Push your changes** notification bar was incorrectly shown after a merge or cherry-pick that produced no actual model changes. Studio Pro now detects this scenario and shows an informational message instead. +* We fixed an issue where some grid cells in Studio Pro became empty while scrolling the grid. +* We fixed an issue where concurrent Git operations failed with an *index is locked* error when the version control status bar polled for conflict information at the same time as write operations such as reset or checkout. +* We resolved an issue where using **Undo All** in the **Changes** pane did not remove the overview pages generated by **Start with Maia**. +* We fixed Maia's inability to create *While* loops. +* We fixed an issue in the MCP settings pane where the **Enable all** and **Disable all** buttons remained clickable even when all tools were already in that state. The buttons are now disabled when they have no effect. +* We removed the *theme.compiled.css.map* from the deployment package due to privacy and security concerns. +* We fixed an issue where date filters sent to OData services with DateTimeOffset attributes contained the wrong date format, causing the remote service to reject the request. +* We fixed an issue in Studio Pro where publishing a microflow in a new REST service allowed adding that service to read-only modules such as the System module. +* We fixed an issue where opening a non-version-controlled app after a version-controlled one, the **Comparison** pane was showing old comparison data. +* We fixed an issue where Studio Pro appeared frozen when marking or unmarking a module as a UI resources module. A progress dialog is now shown while the app is synchronized with the file system. +* We fixed an issue in the modernized App Explorer where Studio Pro appeared unresponsive after moving documents or folders. A progress dialog is now shown until the App Explorer has finished updating. +* We fixed an issue in the modernized **Find Results** pane where closed result sets reappeared and the displayed number of open result sets was incorrect. +* We fixed an issue in the modernized App Explorer where actions triggered with keyboard shortcuts could apply to the previously selected node. +* We fixed an issue where pressing Escape to close a modal dialog also closed the sidebar. +* We fixed an issue in the microflow editor where sometimes the loop was selected when trying to select elements inside the loop. ### Deprecations -- We deprecated support for Java 21. Support for Java 21 will be removed in the future. Mendix recommends using Java 25. -- The `Consumer` overloads of `ListenersRegistry.register*Listener`, `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the matching `EventActionInfo` constructors are deprecated as of Mendix 11.14.0 and will be removed in Mendix 12. Use the `BiConsumer` overloads instead, which also provide the active context to the callback. +* We deprecated support for Java 21. Support for Java 21 will be removed in the future. Mendix recommends using Java 25. +* The `Consumer` overloads of `ListenersRegistry.register*Listener`, `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the matching `EventActionInfo` constructors are deprecated as of Mendix 11.14.0 and will be removed in Mendix 12. Use the `BiConsumer` overloads instead, which also provide the active context to the callback. ### Breaking Changes -- Requests to servlets registered via `Core.addDevelopmentServlet` now require authentication. The M2EE admin password must be provided in the `X-M2EE-Authentication` header (Base64-encoded). +* Requests to servlets registered via `Core.addDevelopmentServlet` now require authentication. The M2EE admin password must be provided in the `X-M2EE-Authentication` header (Base64-encoded). ### Known Issues \ No newline at end of file From 6c08f8a0d932658677e5558ed6015eda421b0b16 Mon Sep 17 00:00:00 2001 From: Quinn Tracy <142489060+quinntracy@users.noreply.github.com> Date: Wed, 19 Aug 2026 16:53:29 +0200 Subject: [PATCH 8/8] Add Find Results RN --- content/en/docs/releasenotes/studio-pro/11/11.14.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.14.md b/content/en/docs/releasenotes/studio-pro/11/11.14.md index b5ee0344fb0..866d6b326dd 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.14.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.14.md @@ -43,6 +43,7 @@ We recommend that projects and Marketplace modules upgrade to Java 25. * We introduced new fields to the package manifest of module packages. The manifest now indicates the type of the module (source, add-on, or solution) and whether the module contains extensions or AI skills. For more information, see [Package Manifest](/refguide/module-settings/#package-manifest). * The `mx` command-line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (add-on and solution) modules. The System module remains excluded. * The `mx` command-line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the Marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy. +* We introduced a new pattern that allows you to store multiple searches in the **Find Results** pane. Subsequent searches are added as tabs and previous searches are kept so you can revisit them at a later time. This removes the **Find Results 2** pane, which previously held a separate set of search results. ### Improvements @@ -124,4 +125,4 @@ We recommend that projects and Marketplace modules upgrade to Java 25. * Requests to servlets registered via `Core.addDevelopmentServlet` now require authentication. The M2EE admin password must be provided in the `X-M2EE-Authentication` header (Base64-encoded). -### Known Issues \ No newline at end of file +### Known Issues