Skip to content

SP 11.10 RNs #11056

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ConnorLand wants to merge 1 commit into
base: development
Choose a base branch
from
+110 −0
Open

SP 11.10 RNs #11056

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
110 changes: 110 additions & 0 deletions content/en/docs/releasenotes/studio-pro/11/11.10.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,110 @@
---
title: "11.10"
url: /releasenotes/studio-pro/11.10/
description: "The release notes for Mendix Studio Pro 11.10 (including all patches) with details on new features, bug fixes, and known issues."
weight: 90
# KI: "Using an Oracle database": Ticket 275597
---

## 11.9.1 {#1191}

**Release date: _____ , 2026**

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

## 11.10.0

### New Features

- We have implemented a new function `DATEPARSE` in OQL. For more details, 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 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

- We introduced a stricter requirements check on the server synchronization API's for offline apps. This prevents entities from synchronizing changes when they are configured with the synchronization modes Online, Nothing, or Never. To allow older offline clients having an All Objects or By XPath synchronization mode to still synchronize while the new app version has the entity configured with an Online, Nothing, or Never synchronization mode, we added a Compatibility mode checkbox.
- Pluggable widgets can now select any file or image entity on the page when configuring a file or image property. Previously this was limited to just the immediate surrounding data view.
- We have added a text indicator to the comparison pane toolbar showing information about what is being compared.
- We have made improvements to the "Collect Support Information" feature:
1. The "Collect Support Information" progress dialog is now cancellable.
2. We made the "Collect Support Information" feature available to macOS users.
3. We have added useful information to aid our support team in diagnosing issues, such as:
1. The length of the current session.
1. The size of the app.
1. Number of modules.
1. Total document count and document type breakdown.
1. If the project directory has been excluded from Windows Defender Antivirus.
- 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 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.
- We added the `com.mendix.tracing.Span.setAttribute` methods to set attributes of spans that are already started.
- Java action tracing span names now include the Java action name.
- We clarified the error message when upgrading solutions with files that have paths that are too long.
- We replaced the custom error screen in App Explorer with a unified global error screen that provides a consistent experience and includes a refresh button and a direct link to support.
- Modernized console table now supports multi-selection via the context menu flow, allowing copying message and stack traces for multiple selected log lines.
- The `app-bundler` file in the project directory has been removed and replaced by a property in the model. The bundler selection (Rspack or Rollup) is now stored as part of the project settings instead of a file.

### Fixes


- We now ensure a `SELECT *` OQL query returns the same columns independent of optimistic locking setting value. Previously the `MxObjectVersion` column would be returned when optimistic locking was enabled.
- We fixed INSERT OQL statements when optimistic locking is enabled.
- We fixed an issue when running with Oracle where task queue queries generated invalid SQL. (Ticket 275597)
- We fixed image rendering for offline web applications during local development. Also, we enabled service worker and disabled service worker caching by default for local development. (Tickets #271956, #273435)
- We made Event sub-process start activity in workflow not draggable.
- 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've added an aditional 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.
- We fixed an issue where saving changes in the **Select Elements** dialog of an XML import mapping incorrectly allowed saving an invalid selection where a parent element was checked but its required child element was not, without showing the expected error "Element '…' cannot be checked without a checked child element." (Ticket 273820)
- We fixed an issue in the **Select Elements** dialog of an XML export mapping where clicking OK on a checked parent element whose required child elements had not been expanded caused the error "Element '…' cannot be checked without a checked child element." Studio Pro now automatically checks required child elements of unexpanded parent nodes before saving. (Ticket 274683)
- Fixed an error in offline synchronization when objects with sync mode set to "Never" are selectively synced after a full synchronization (Ticket 266442)
- We fixed an issue where filtering for objects using a constraint like [not(association)] in offline apps incorrectly returned no results. (Ticket 274157)
- We fixed an issue in Consumed REST service, Path-level parameters are now added to parameters table when importing OpenAPI/Swagger contract.
- We fixed an issue in published REST service using CORS. The runtime now includes CORS headers in error responses.
- We fixed an issue in published REST services in Studio Pro. Studio Pro would use the same field for (internal) documentation and public documentation (used in OpenAPI documents). Now these are two separate fields.
- We fixed an issue in modernized console panel where new logs appeared at the bottom of the table instead of the top when sorted in descending order.
- We fixed an issue where native macOS context menus could appear instead of the intended Studio Pro context menus.
- We fixed an issue in the modernized Runtime Console where the restart and stop buttons stopped working after the first restart.
- We fixed an issue where the modernized App Explorer is not rendered on startup.
- We fixed an issue in the modernized Console Panel where the logs would not clear whenever another app was created or opened.
- We fixed an issue in the modernized Console Panel where log levels were not always reset to their defaults when opening a new app.
- We fixed an issue in the JavaScript Action Editor where multiline import statements were not parsed correctly.
- We fixed an issue where an app could reject valid localized dates for custom date patterns that use month names. This affected patterns with abbreviated month names such as `dd MMM yyyy` and standalone abbreviated month names such as `dd LLL yyyy`, so values like the Dutch `16 mrt 2027 10:02` could be treated as invalid.
- We fixed an issue where the `Filter` interface in `mx-api/data` incorrectly used `amount` instead of `limit` to specify the maximum number of records to retrieve. While `amount` is supported, we recommend using `limit`.
- In the entity access rules editor, we fixed module roles not being sorted in alphabetical order.
- We improved the error message for invalid save actions when trying to save an unexpected object type while strict mode is enabled. (Ticket 270333)

### Deprecations

- Starting with Mendix version 11.12, we will drop support for the following database versions that are no longer supported by the vendors:
- PostgreSQL 13
- MariaDB 10.6

### Breaking Changes

- We removed the `scope` parameter from the `subscribe` method in `mx-api/data`. This parameter was never intended to be part of this API. If you rely on it to bind a context object to your callback, use other standard JavaScript context-binding techniques instead.

### Known Issues

REMINDER - DUPLICATE KI from previous version (oracle)