Update Maia and workflow release notes for Studio Pro 11.10

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

@@ -15,21 +15,28 @@ weight: 90
 ## 11.10.0
 
 ### New Features
-
+
+#### New Maia Features
+
+- We introduced a new Maia MCP Client Settings editor to make configuring and managing MCP Client settings easier.
+- Maia's capabilities can now be exposed as an MCP server, which can be enabled in the Maia preferences. This allows external agentic coding tools like Claude Code or Copilot to make modifications to your Mendix application, with changes reflected directly in Studio Pro.
+- Maia can now fetch and interpret static web content such as external documentation, JSON specifications, and other publicly available documents. Note that it does not support content requiring authentication, dynamic web pages, or non-text formats.
+- Maia can organize documents (excluding pages) into folders, following your existing folder structure, or using standard Mendix best practices.
+- Maia can now generate new JavaScript actions, add new parameters to existing JavaScript actions, and create or update the JavaScript file associated with a JavaScript action.
+- Maia can now generate and configure [Multi-user task](/refguide/multi-user-task/) in workflows.
+
+#### Other New Features
+
+- We introduced Update Assistant (Beta) as a bottom panel in Studio Pro, where you can check Java action deprecations in your app.
 -  We implemented a new function `DATEPARSE` in OQL. For more information, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#dateparse-function).
-- We added support for interrupting behavior on the workflow Notification Event Sub-Process Start Event. When configured as interrupting, the Event Sub-Process will interrupt the parent workflow, terminating all active execution paths within the global scope — including activities in the main process and any nested sub-processes — before initiating the Event Sub-Process flow.
+- We added support for the interrupting behavior on the workflow notification event sub-process **Start** event. When configured as interrupting, the event sub-process interrupts the parent workflow, terminating all active execution paths within the global scope，including activities in the main process and any nested sub-processes，before initiating the event sub-process flow.
 - We added a Show button in the element selector. Clicking it opens the selected element.
 - We added the optional `selectedElementId` in the select methods of the element selector. If passed in, it will highlight the node with the corresponding id in the tree.
-- We introduced a new MCP Settings editor to make configuring and managing MCP settings easier.
 - We added the `http.nonProxyHosts` runtime configuration setting to specify hosts for which the runtime should not use a proxy.
 - We added the ability to revert a commit from the history pane. You can now right-click a commit and select 'Revert Commit' to reverse the changes introduced by that specific commit.
 - We added a new runtime setting `FileStorage.S3.DisableChunkedEncoding` to allow disabling chunked encoding for S3 storage. (Tickets 274327, 272789)
 - We added a new Java API to create spans for tracing. The API is accessible via `com.mendix.core.Core.tracing()`.
-- Maia can fetch and interpret static web content such as external documentation, JSON specifications, and other publicly available documents. Note that it doesn't support content requiring authentication, dynamic web pages, or non-text formats.
-- Maia's capabilities can now be exposed as an MCP server, which can be enabled in the Maia preferences. This allows external agentic coding tools like Claude Code or Copilot to make modifications to your Mendix application, with changes reflected directly in Studio Pro.
-- Maia can organize documents (excluding pages) into folders, following your existing folder structure or using standard Mendix best practices.
 - The Mendix runtime now responds to Cross-Origin Resource Sharing (CORS) preflight (`OPTIONS`) requests for client-facing endpoints. The responses include the custom headers configured in the runtime settings, allowing you to set up CORS for your application.
-- We introduced Update Assistant (Beta) as a bottom panel in Studio Pro, where you can check Java action deprecations in your app.
 
 ### Improvements
 
@@ -48,7 +55,7 @@ weight: 90
 - We fixed an issue where OQL‑based view entities could use an outdated ID column alias, leading to mismatches with Domain Model association names. A new App conversion step now detects these mismatches when opening the App and updates the column alias in OQL accordingly.
 - We fixed an issue where copying a ViewEntity together with its associated Entity failed to include the connecting association. This association is now correctly copied whenever both elements are selected. Additionally, copying and pasting a ViewEntity now duplicates any linked in‑module or cross‑module Associations, assigning them new names and automatically updating their OQL references.
 - Maia answers now also include sources from the Mendix Support Knowledge Base.
-- We improved the Maia chat experience with several UI enhancements.
+- We improved the Maia Chat experience with several UI enhancements.
 - We upgraded to React 19.2 and React Native 0.83, bringing the latest performance improvements and features from both ecosystems. These updates provide enhanced rendering performance, improved native module integration, and a more modern foundation for building your low-code applications.
 - We improved how Studio Pro stores the configuration microflow and the headers microflow in consumed OData services. These used to be stored in the same field. Now they are stored in two separate fields. When you switch from using a headers microflow to using a configuration microflow, Studio Pro will ask if you want to clear the headers microflow and vice versa.
 - We now delete sessions when the associated user is deleted.
@@ -75,9 +82,9 @@ weight: 90
 - We made main start activity in Workflow not draggable to prevent users from accidentally dragging it and losing their progress. This change will help improve the user experience and prevent frustration caused by accidental drags.
 - We fixed an issue where renaming a view entity association in the Domain Model editor did not update the corresponding ID alias in the OQL query, ensuring the OQL definition now stays consistent with the new association name.
 - We fixed an issue in the logic editors, where the LogicBot recommender dialog remained open after running the app, causing an error. The dialog is now closed when suggestions are cleared.
-- We fixed an issue where documents generated and then edited by Maia were not deleted properly when Undo was pressed
-- We fixed an issue where using **Undo all** in Maia Chat would trigger an unexpected error dialog.
-- We fixed an issue where App Explorer Maia context menu items were enabled when multiple documents were selected. These items are now disabled for multi-document selections.
+- We fixed an issue where documents generated and then edited by Maia were not deleted properly when **Undo** was pressed.
+- We fixed an issue where using **Undo all** in Maia would trigger an unexpected error dialog.
+- We fixed an issue where Maia context menu items in the App Explorer were enabled when multiple documents were selected. These items are now disabled for multi-document selections.
 - We added an additional fix for cases where an external keyboard would not traverse properly through elements marked as accessible on mobile devices.
 - We have fixed an issue on iOS where specific scenarios of using custom styled widgets inside Containers would not show the desired styling.
 - We fixed an issue where an Oops dialog appeared when re-selecting a modified JSON Structure in an import mapping. This happened after updating the JSON Structure's content and then re-opening the Select Elements dialog to select the same structure again.