Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
134 changes: 134 additions & 0 deletions content/en/docs/releasenotes/studio-pro/11/11.16 copy.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,134 @@
---
title: "11.16"
url: /releasenotes/studio-pro/11.17/
description: "The release notes for Mendix Studio Pro 11.17 (including all patches) with details on new features, bug fixes, and known issues."
weight: 83
# KI: "Maia Chat pane issue": MID-317
# KI: "BYO LLM": SPAM-435
# KI: "Mx.exe commands": SOLP-4224
# KI: "Breaking client certificate auth": REST-751
---

{{% alert color="info" %}}For highlights of this release, see the [Mendix Release 11.17](https://www.mendix.com/blog/mendix-release-11-17/) blog post.{{% /alert %}}

## 11.17.0 {#11170}

**Release date: November ___, 2026**

{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.16.1" text="Go to Marketplace" title="Download version 11.17.0 from the Marketplace" %}}

### New Features

- Maia can now create and edit page templates, and create new pages based on them.
- Maia now supports prompt caching and reasoning when you connect it to your own Amazon Bedrock models.
- For Change Data Capture document, we added `userName` and `userRoles` to the Kafka message.
- Maia now generates microflows faster, since it no longer needs to calculate the position of every activity itself; the new auto layout engine arranges the flow automatically after generation. The microflow editor's right-click menu also gets a new "Auto layout" option, letting you arrange either the whole microflow or just the activities you have selected. This experimental feature is enabled by default and can be turned off via the "Enable auto layout for microflows (Experimental)" checkbox in Preferences, under New features > Microflow, Nanoflow, and Rule Editor.
- Maia can now create and change XML Schema documents from XSD content/file. When the XSD contains constructs that Studio Pro does not support, Maia tells you which ones.
- Maia can now clear the mappings of an Import Mapping or Export Mapping, like **Clear mappings** in the mapping editor does. This lets Maia map the selected elements again after they were auto-mapped.
- When comparing two app versions and a document has been moved, you can now open the newer version of that document directly from the context menu in the comparison pane.
- You can now add custom headers, such as an API key, when you add an MCP server in Maia. This lets you connect to MCP servers that require them. Header values are stored securely.
- You can now [override the system texts](add-link-to-the-docs-explaining-the-feature-11.17) used by pluggable widgets. You can add overrides per language using text templates, which can use the system text's parameters and other variables on the page or snippet.
- You can now connect Maia to an OpenAI compatible model that is protected by Microsoft Entra ID, such as Azure AI Foundry. In the Maia settings, set the authentication mode to **Sign in with Microsoft Entra ID**, enter the details of your app registration, and sign in with your Microsoft account. You do not need an API key. This has only been tested with Azure AI Foundry.
- We have added autoformatting to the JavaScript Action editor. If desired, you can turn it off in the modeler settings.
- Update Assistant now also checks JavaScript actions for deprecated Client API calls. If a replacement is available, Update Assistant shows the suggested change.
- We added a `getLocale()` method to the `mx-api/session` module, allowing you to retrieve the locale of the current session. For more information, see the [`getLocale()` API documentation](https://apidocs.rnd.mendix.com/11/client-mx-api/module-mx-api_session.html#getLocale).

#### Primitive Parameters Support for Snippets

It is now possible to define primitive parameters (like a `String` or `Boolean`) for [snippets](https://docs.mendix.com/refguide/snippet/). When [calling a snippet](https://docs.mendix.com/refguide/snippet-call/), you can use [expressions](https://docs.mendix.com/refguide10/expressions/) to set primitive values as arguments, use functions, and even follow associations!

One of the big advantages is that a page can now use a local variable or a page parameter and pass it straight to a snippet. In general, logic that has primitive parameters can be more easily reused as it is not tied to the domain model. Thus, this feature also improves overall reusability. You can imagine how much easier and faster this makes modeling!

When you extract a snippet, the primitive variables and parameters it uses are now turned into primitive snippet parameters automatically, so the extracted snippet keeps working without manual rework.
- The **Close Action** property of pop-up pages now supports a regular client action that you can configure directly, just like any other action in the platform. This gives you more flexibility and a more consistent modeling experience for newly configured pop-up pages.

New pop-up pages use this action-based close behavior by default.

#### Existing Pop-Ups

Existing pop-ups that use the legacy button reference continue to work after you update the project. They are automatically converted to the new action model only when the referenced button uses one of the following client actions:

- `DoNothingClientAction`
- `CancelChangesClientAction`
- `ClosePageClientAction`
- `SaveChangesClientAction`
- `SignOutClientAction`

#### Manual Conversion

If an existing pop-up cannot be converted automatically, switch its close action type from the deprecated button reference to the new action configuration.

If you used the conditional visibility of the referenced close button to execute different close behaviors, that logic is not carried over when you switch to the new action-based behavior. The close action is now a direct client action, so visibility conditions on the old button no longer affect it. To preserve conditional close behavior, configure the close action to call a nanoflow that contains the conditional logic.

#### Deprecation

We deprecated the legacy system of using a button reference as a close action.

### Improvements

* We upgraded the JDBC driver for Microsoft SQL Server to version 13.6.2.
* If you connect to SQL Server using integrated security in a module such as [Database Connector](https://marketplace.mendix.com/link/component/2888), you may need to update the JDBC driver in `userlib` as well.
- We improved performance of Studio Pro especially for App Explorer operations such as right mouse click, double click to open, etc for non-sprintr projects.
- We updated the .NET Runtime to version 10.0.15.
- Selecting a consistency error for the Change Data Capture document now opens the document and highlights the source of the error.
- We added Kafka producer metrics for Change Data Capture (CDC) publishing under `mx.cdc.producer.kafka.*`.
These cover batch sizes, records per request, queue time, send rate, request latency, and available buffer memory.
- In the Change Data Capture document, we added visual styling for revision changes to make it easier to identify what has changed since the previous revision.
- In the Change Data Capture document, the revision check now takes into account the decimal scale defined in the project settings.
- In the Change Data Capture document, the revision check now detects changes to the required rule of an attribute in the domain model.
- In the Change Data Capture document, the revision check now detects changes to the length of a String attribute in the domain model.
- In the Change Data Capture document, the revision check now also detects changes to associations multiplicity in the domain model.
- In the microflow editor, Maia can now generate error handling flows more efficiently
- Maia now uses the app's configured default sequence flow type when generating microflow flows, instead of always using a Bezier curve.
- We upgraded the react-native to 0.88.0 and bumped related dependencies.
- The `clearElementMapping` method of the import and export mapping APIs (`studioPro.app.model.importMappings` and `studioPro.app.model.exportMappings`) now works like **Clear mappings** in the mapping editor. Besides entities and attributes, it also clears associations and converters, and restores the default object handling. For import mappings it also resets the parameter type. It now returns how many entity and attribute mappings were cleared.
- Maia can now create a JSON structure document from an attached JSON file, or replace the JSON snippet of an existing JSON structure with it. You no longer need to paste the JSON content into the chat, which also makes it possible to use large JSON files.
- We improved the call REST service and call web service activities at runtime. Multipart requests now use boundary values that only contain alphanumeric characters, dashes and dots.
- We updated the bundled JDK to version 25.0.5.
- We removed the individual OQL generation capability since this is now handled in Maia.
- When you open the Find dialog, the previous search text in the "Find what" field is now selected, so you can type a new search term without clearing the field first.
- In apps that use the React client, generated sources are now placed in **deployment/websource**, so **deployment/web** only contains the files that are served to the browser.
- Embedded apps no longer need a `minHeight` to be passed to `render`. An embedded app now takes the height of the element it is rendered into, or the height of its content when that element has no height. Passing `minHeight` has no effect anymore.
- We removed the **Use the legacy JavaScript Action editor** preference. JavaScript actions now always open in the new JavaScript Action editor.
- We removed the restriction that allowed only one interrupting boundary event per workflow activity. You can now add multiple interrupting boundary events to an activity, up to the existing limit of five boundary events in total.
- We removed the context menu options to **Convert to** widgets that are not supported in React client. Specifically [dropdown](/refguide/mendix-client/react/#reference-selectors-drop-down), [dynamic image, and static image](/refguide/mendix-client/react/#dynamic-static).
- We improved the **inline snippet** action. When you inline a snippet, its variables are now recreated on the page or snippet you are editing.
- We optimized the deployment of snippets for native apps. Apps that reuse snippets across multiple pages will see faster build times and smaller JavaScript bundle sizes.
- We fixed an issue where expressions that don't support page or snippet variables still allowed you to reference them, which caused a runtime error in the client; a consistency error now prevents this.
- We updated Maia Make to use Claude Sonnet 5.5.

### Fixes

- We fixed an issue where auto-committed entries and objects were not being cleaned up after application restart. (Ticket 261753)
- We fixed a caching issue that could cause errors in React client PWAs after a new version was deployed to Sandbox. Page requests now include a cache-busting query parameter to ensure the latest version is loaded. (Ticket 283757)
- We fixed an issue on mobile applications where Tab labels would get cut off depending on various combinations of styling and/or mix of alphanumeric characters. (Ticket 286711)
- We fixed an issue where an app could not be opened if it contained a consumed REST service query parameter with dots in its name (for example, `Person.Address.Zipcode`) that was used in a **Send REST request** microflow activity. The runtime now also sends the full name of such query parameters instead of only the part after the last dot. (Ticket 287134)
- We fixed an error in Studio Pro when deleting a nanoflow variable referenced by a "Synchronize specific objects" activity. (Ticket 289290)
- We fixed an issue in the React client where a translated caption was not shown at runtime when it had no translation in the default language. (Tickets 289478, 290936)
- We fixed an issue where pluggable widget action variables were empty when the widget was placed inside a snippet. (Tickets 291606, 291618)
- We now only show the name of unknown configuration settings when a warning about them is logged. (Ticket 291608)
- We fixed an issue where files from external entities published via OData could not be downloaded. (Ticket 292299)
- We fixed an issue where the dispose listener was not returned correctly by the `addEventListener` method, causing an error to be thrown when attempting to call it.
- We fixed an issue where the Changes pane had focused a document that was being brought back to focus after each save of the project.
- In the logic editors, we fixed an issue where a microflow's ReturnVariableName would not be set when setting a return value through the context menu
- We fixed an issue in the microflow editor that could occur after the project was closed.
- We fixed an issue where icon is misaligned if caption is empty in Button.
- We fixed an issue where **Map automatically** in import and export mappings changed entities that cannot be edited, such as entities of the System module, by adding attributes to them or setting their generalization. These entities are no longer changed, and the log of changes lists the elements that were skipped.
- For improved security, XSD imports no longer fetch nested schemas from private or local network addresses, and only follow redirects to public addresses. A schema fetched from a URL can no longer include local files. When a referenced schema cannot be loaded, Studio Pro now shows which one and why. **As a work-around**, if you have a schema that imports from an internal server and that is rejected now, then please download the schema references, save them next to the root XSD file, change the `schemaLocation` attributes to point to the local copies, and import the root XSD file from your computer.
- We fixed an issue where Maia page generation removed the design properties of widgets nested inside a custom widget, such as the containers in the filter of a Data grid 2 column, whenever it created or edited the page. These design properties are now kept.
- We fixed an issue where Maia Make was using outdated project information when switching projects, causing issues.
- We fixed an issue where documents were not saved after Maia Make applied a rename in that document.
- We fixed an issue where a user who was set to inactive could keep using their existing session. Their sessions now end on their next request.
- Fixed an issue where updating from file did not reflect a document's new folder location on the consumer side when the document itself was unchanged.
- We fixed the Setup node in the App Explorer: reverting changes and removing items now leave the right state in the Changes pane, and the comparison shows Setup item names.
- We fixed an issue where Maia tool outputs could appear empty or truncated, on both the Mendix platform and Amazon Bedrock models.
- We fixed an issue where Maia could run out of context when reading a large attached file. Long attachment content is now truncated, and Maia can read the rest in follow-up calls.
- We fixed an issue where the delete tool did not work when used through the Maia MCP server.
- We fixed an issue where AI agents connected through the Maia MCP server did not get the list of available skills.
- We fixed an issue where the Modernized App Explorer scrolled sideways while you dragged an item out of it, for example onto a document editor. The App Explorer no longer scrolls horizontally during a drag, and scrolling vertically while you drag still works. You can still scroll horizontally with the scrollbar when you are not dragging.
- We fixed an issue where expanding or collapsing a node in the Modernized App Explorer with the right or left arrow key also scrolled the App Explorer sideways.
- We fixed an issue where code written to a JavaScript action by Maia or outside of Studio Pro could be overwritten when the action was saved in its editor. Maia now asks you to save or discard your unsaved code changes before it reads or changes the code of a JavaScript action.
- In apps that use the React client, we fixed an issue where Studio Pro's memory use and the duration of **Run Locally** updates could grow rapidly when nanoflows were changed repeatedly during a long session.

### Known Issues

Loading