edit

Author: ConnorLand

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

@@ -16,29 +16,29 @@ weight: 90
 
 #### Send Email Microflow Activity (Beta)
             
-In Studio Pro 11.13.0, we introduced the [Send Email](/refguide/send-email-action/) microflow activity as a beta feature. The Send Email activity lets you send emails directly from a microflow in Studio Pro. 
+In Studio Pro 11.13.0, we introduced the [Send Email](/refguide/send-email-action/) microflow activity as a beta feature. The Send Email activity lets you send emails directly from a microflow in Studio Pro.
 
 With the Send Email activity, you can configure the email server connection, authentication method, sender and recipients, message content, attachments, and other email properties directly within the activity. You can also test the connection and send a test email from Studio Pro while your app is running, making it easier to build and validate email-based workflows.
 
 #### Other New Features
             
-- We added a **Location** setting to the General tab of the Module Settings dialog. It lets you choose whether a module is listed in the regular module list or under the **Marketplace modules** node in the App Explorer.
+- We added a **Location** setting to the **General** tab of the Module Settings dialog. It lets you choose whether a module is listed in the regular module list or under the **Marketplace modules** node in the App Explorer.
 - You can now update a module from a file, by right clicking on the module in the App Explorer. You must to provide the *.mpk* files for the original version, and the version you are updating to. Updating will trigger the merge algorithm and possibly conflict resolution, allowing you to retain customizations you made to the module. This update mechanism only works for module packages created after 11.12.0. A future update will add compatibility for modules created before that.
 -  We added support for constants in OQL queries. Constants defined in the model can be referred in OQL queries as `$<Module>.<Constant>`. Currently, this feature is available only in Java API.
 -  We added support for enumerations in OQL queries. Enumeration values can be used in OQL queries as `<Module>.<Enumeration>#<Value>`. Currently, this feature is available only in Java API.
-- German is now available as a Beta language in Studio Pro. You can switch the Studio Pro interface to German in the **Preferences** dialog.
-- We added a "Copy Path" button to the notification that shows when the App folder fails to be excluded by the antivirus.
+- German is now available as a beta language in Studio Pro. You can switch the Studio Pro interface to German in the **Preferences** dialog.
+- We added a **Copy Path** button to the notification that shows when the app folder fails to be excluded by the antivirus.
 - The Java API `OqlStatement` now supports `INSERT INTO VALUES` statements to insert value rows directly. For mor information, see the [SELECT Statement](/refguide/oql-statement/#oql-insert).
 - Maia now supports working with JSON Structure documents.
-- We added observability for offline synchronization operations. Each synchronization now records success/failure counters for apps with a metrics dashboard. For apps without a metrics dashboard, the same data is also persisted in a new `System.SynchronizationHistory` entity (including duration, number of synchronized objects, error count, and the user who initiated the synchronization), which can be used to build an admin dashboard. History records are automatically cleaned up after the configurable custom setting `com.mendix.offline.SynchronizationHistoryRetentionDuration` (default: 365 days).
-- We added the ability to display added documents and elements details in Comparison Pane.
-- We added the ability to display deleted documents and elements details in Comparison Pane.
+- We added observability for offline synchronization operations. Each synchronization now records success and failure counters for apps using a metrics dashboard. For apps without a metrics dashboard, the same data is also persisted in a new `System.SynchronizationHistory` entity (including duration, number of synchronized objects, error count, and the user who initiated the synchronization), which can be used to build an admin dashboard. History records are automatically cleaned up after the configurable custom setting `com.mendix.offline.SynchronizationHistoryRetentionDuration` (default: 365 days).
+- We added the ability to display added documents and elements details in the **Comparison** pane.
+- We added the ability to display deleted documents and elements details in the **Comparison** pane.
 - We added a new setting to enable or disable OQL generation with Maia. OQL generation always uses the Mendix Platform regardless of the provider.
-- We added **Maia Explain** and **Solve problem with Maia Chat** context menu options to the Error List to help you understand and resolve consistency errors directly with Maia.
-This setting takes effect immediately, with one exception: if you are using the Studio Pro MCP Server a restart of Studio Pro is required for the changes to take effect. OQL generation with Studio Pro MCP Server is only possible with both the Enable Maia and Enable oql tool settings enabled.
+- We added **Maia Explain** and **Solve problem with Maia Chat** context menu options to the **Error** List to help you understand and resolve consistency errors directly with Maia.
+This setting takes effect immediately, with one exception: if you are using the Studio Pro MCP Server a restart of Studio Pro is required for the changes to take effect. OQL generation with Studio Pro MCP Server is only possible with both the **Enable Maia** and **Enable OQL** tool settings enabled.
 - Studio Pro now automatically selects a free port for the MCP server when the default port is already in use, so multiple instances can run side by side without manual configuration.
 - A notification is shown when the MCP server starts, and the active port is visible in the status bar.
-- We added support for interrupting and non-interrupting behavior on the workflow Timer 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. When configured as non-interrupting, the Event Sub-Process runs in parallel with the parent workflow without affecting its execution.
+- We added support for interrupting and non-interrupting behavior on the workflow Timer 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. When configured as non-interrupting, the Event Sub-Process runs in parallel with the parent workflow without affecting its execution.
 - The External Database Connector is now built into Studio Pro. You no longer need to download the module from the Marketplace.
 - Web extensions now must include `@mendix/model-access-registry` in the external build configuration.