diff --git a/content/en/docs/releasenotes/studio-pro/11/11.12.md b/content/en/docs/releasenotes/studio-pro/11/11.12.md index f75eea11a8c..c16b0589edb 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.12.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.12.md @@ -6,11 +6,65 @@ lts: true weight: 88 # KI: "Maia Chat pane issue": MID-317 # KI: "BYO LLM": SPAM-435 -# KI: "GUIDs are not restored": SOLP-4209 --- {{% alert color="info" %}}For highlights of this release, see the [Mendix Release 11.12](https://www.mendix.com/blog/mendix-release-11-12/) blog post.{{% /alert %}} +## 11.12.7 {#11127} + +**Release date: November ___, 2026** + +{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.12.7" text="Go to Marketplace" title="Download version 11.12.7 from the Marketplace" %}} + +### New Features + +* We added support for updating a module from a file for module packages created before Mendix 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. +* We added a new API for interacting with the Maia agent chat (`studioPro.ai.chat`) to prefill the Maia chat window with input text and either let the user review it before sending it or automatically send it. +* We added rules to the Best Practice Recommender that help you limit anonymous user access. Several of these rules can automatically apply changes for you. For more information, see [Security Recommendations](/refguide/security-best-practices/). +* Maia now supports prompt caching and reasoning when you connect it to your own Amazon Bedrock models. + +### Improvements + +* We added a confirmation dialog box before publishing, so you can review and confirm the action. +* We changed the runtime to exit with exit code 7 instead of 0 when a cluster node fails to update its heartbeat on time. This allows service managers, such as Windows service recovery, to treat the shutdown as a failure and restart the runtime. The heartbeat check is also no longer affected by system clock changes. +* We improved the Studio Pro MCP Server connection handling. If you have an MCP client (such as Claude Code) connected to Studio Pro, disconnect and reconnect it after updating. + +### Fixes + +* We fixed a [known issue](#ki-guids) where storage GUIDs were not retained during module update from an *.mpk* file. +* We fixed a race condition that occurred during metadata update. (Ticket 282231) +* 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. (Ticket 282757) +* We fixed an issue where the `analyze-mpr` command of `mx.exe` crashed on projects containing modules with more than 10,000 documents inside. (Ticket 284495) +* We fixed an issue where metadata was missed during a commit with a large number of model changes. (Tickets 285459, 285998, 286434, 286937, and 287069) +* We fixed an issue on mobile apps where tab labels got cut off depending on the combination of styling and alphanumeric characters. (Ticket 286711) +* We fixed an issue with sorting and filtering on microflow, nanoflow, or association data sources. A client error dialog box appeared when users sorted or filtered by an attribute or association they could not access because of access rule constraints. (Ticket 287118) +* We fixed an issue where a row extracted with **Extract to new grid** could not be selected in the page editor and had no **Insert row above/below** options in the context menu. Inserting a row in the extracted grid placed it at the wrong position or caused an error. (Ticket 287120) +* We fixed an issue where a Custom Chart in a pop-up window flooded the console with type errors when users hovered over data points. (Ticket 287153) +* We fixed an issue where signing out of native and offline-first web apps could show a database error when other database operations were still running. (Ticket 288359) +* We fixed an issue where offline synchronization operation IDs changed between builds, which could cause synchronization errors after updating a native app. (Ticket 288359) +* We fixed an issue where missing file content on the server caused a microflow's **Sync to device** action to fail in offline apps instead of skipping the affected objects and synchronizing the remaining objects. (Ticket 288772) +* We fixed an issue where Prometheus failed to scrape the `/prometheus` endpoint on the admin port, because the response had no `Content-Type` header and Prometheus could not parse the `jvm_info` metric. (Ticket 289111) +* We fixed an issue where deploying an app could fail while exporting a nanoflow. This happened when a Call JavaScript action with **Use return value** turned off still had an old output variable name stored, and the nanoflow also contained a variable with that same name. (Ticket 289203) +* We fixed an error in Studio Pro that occurred when deleting a nanoflow variable referenced by a **Synchronize specific objects** activity. (Ticket 289290) +* We fixed an issue that resulted in an index.lock error when performing a rebase. +* We fixed an issue where consistency errors did not show up after changing security settings. +* We fixed an issue where adding a System association to the **Change Data Capture** document did not allow users to accept changes. +* We fixed an issue where entity access rules contained invalid module role references after copying or moving an entity to another module, preventing users from selecting and updating roles in the access rule editor. +* In the logic editors, we fixed an issue where dragging a toolbar item did not work the first time after dragging a different one. +* We fixed an issue where Maia page generation removed all but one translation from a page title when it read or edited a page in an app with multiple languages. Page titles now keep all their translations. +* We fixed an issue where Maia page generation removed the design properties of widgets nested inside a custom widget, such as containers in a filter of a Data Grid 2 column, whenever it created or edited a page. These design properties are now kept. +* We fixed an issue where the custom error handler of a decision was skipped when its expression or rule failed after another decision had already been executed in the same microflow. Instead, a "No connecting flow found" error was thrown and handled by the error handler of a calling microflow. +* We fixed an issue where Maia tool outputs appeared empty or truncated on both the Mendix platform and Amazon Bedrock models. +* We fixed an issue where comparing two lists with `=` in a client-evaluated expression (for example, in a nanoflow) used a membership check instead of true equality. Lists with duplicate elements, or the same elements in a different order, could incorrectly be considered equal. For example, `[1, 2] = [2, 1]` previously evaluated to `true`; it now evaluates to `false`, matching microflow behavior. +* We fixed an issue where nanoflows with the same name in different modules called the wrong nanoflow at runtime in apps that use the React client. + +### Known Issues + +* The Maia Chat pane may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**. + * Workaround: Manually close the panel when it appears. +* When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning. + * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. + ## 11.12.6 {#11126} **Release date: October 8, 2026** @@ -42,11 +96,13 @@ weight: 88 ### Known Issues +* When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue. + * Fixed in [11.12.7](#ki-fix-guids) and [11.16.0](/releasenotes/studio-pro/11.16/#ki-fix-guids). * The Maia Chat pane may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**. * Workaround: Manually close the panel when it appears. * When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning. * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. -* When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue. + ## 11.12.5 {#11125} @@ -104,15 +160,17 @@ weight: 88 ### Known Issues +* * REST, ODATA, Web Services, and all other features that use client certificate authentication fail because the client certificate is not sent. If you use client certificate authentication for these integrations, do not upgrade to this version. Instead, upgrade to version 11.12.6, where this issue will be fixed. (Tickets 289190, 289295, 289392, 289586) + * Fixed in [11.12.6](#fix-client-certificate) +* When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue. + * Fixed in [11.12.7](#ki-fix-guids) and [11.16.0](/releasenotes/studio-pro/11.16/#ki-fix-guids). +* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. + * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). * The Maia Chat pane may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**. + * Workaround: Manually close the panel when it appears. * When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning. * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. -* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. - * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). -* When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue. -* * REST, ODATA, Web Services, and all other features that use client certificate authentication fail because the client certificate is not sent. If you use client certificate authentication for these integrations, do not upgrade to this version. Instead, upgrade to version 11.12.6, where this issue will be fixed. (Tickets 289190, 289295, 289392, 289586) - * Fixed in [11.12.6](#fix-client-certificate) ## 11.12.4 {#11124} @@ -155,13 +213,15 @@ weight: 88 ### Known Issues +* When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue. + * Fixed in [11.12.7](#ki-fix-guids) and [11.16.0](/releasenotes/studio-pro/11.16/#ki-fix-guids). +* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. + * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). * The Maia Chat panel may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**. * Workaround: Manually close the panel when it appears. * When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning. * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. -* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. - * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). -* When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue. + ## 11.12.3 {#11123} @@ -222,13 +282,15 @@ weight: 88 ### Known Issues +* When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue. + * Fixed in [11.12.7](#ki-fix-guids) and [11.16.0](/releasenotes/studio-pro/11.16/#ki-fix-guids). +* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. + * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). * The Maia Chat pane may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**. * Workaround: Manually close the panel when it appears. * When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning. * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. -* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. - * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). -* When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue. + ## 11.12.2 {#11122} @@ -287,12 +349,12 @@ weight: 88 ### Known Issues +* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. + * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). * The Maia Chat pane may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**. * Workaround: Manually close the panel when it appears. * When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning. * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. -* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. - * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). ## 11.12.1 {#11121} @@ -340,12 +402,12 @@ weight: 88 ### Known Issues +* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. + * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). * The Maia Chat pane may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**. * Workaround: Manually close the panel when it appears. * When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning. * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. -* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. - * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). ## 11.12.0 {#1112} @@ -502,15 +564,15 @@ CDC can be used with the Mendix Event Broker or with a Bring Your Own Kafka (BYO ### Known Issues +* A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: + * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. + * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. + * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) +* In an [embedded navigation profile](/refguide/mendix-client/embedding-the-client/), omitting a parameter that is marked as optional from the `parameters` object will result in the fallback page being shown instead of the default value being passed. + * Added in [11.12.1](#embed-optional-params) +* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. + * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). * The Maia Chat pane may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**. * Workaround: Manually close the panel when it appears. * When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning. * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. -* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. - * Fixed in [11.15.0](/releasenotes/studio-pro/11.15/#ki-fix-skills-button). -* In an [embedded navigation profile](/refguide/mendix-client/embedding-the-client/), omitting a parameter that is marked as optional from the `parameters` object will result in the fallback page being shown instead of the default value being passed. - * Added in [11.12.1](#embed-optional-params) -* A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: - * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. - * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. - * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.16.md b/content/en/docs/releasenotes/studio-pro/11/11.16.md index 5081bb4c219..3e4c3ad1433 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.16.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.16.md @@ -83,10 +83,11 @@ weight: 84 * We made the modernized App Explorer the default for all users. If you find an issue, you can fall back to the legacy App Explorer by disabling the modernized App Explorer flag in **Preferences** > **New Features** tab. * The modernized Find Results pane now shows an overflow button next to the result set tab bar. Clicking it opens a menu listing all result sets, with the active one marked. Selecting an item from the menu switches to that result set and scrolls it into view. * We changed the default names of newly created workflow events so that they identify themselves as events. Start events are now named `startEvent`, end events `endEvent`, timers `timerEvent`, and notifications `notificationEvent`. Event sub-process start events now use `startEvent` as well, instead of a name derived from their event type. Existing workflows are not affected. +* We improved the Studio Pro MCP Server connection handling. If you have an MCP client (such as Claude Code) connected to Studio Pro, disconnect and reconnect it after updating. ### Fixes -* We fixed a [known issue](/releasenotes/studio-pro/11.12/#ki-guids) where storage GUIDS were not retained during module update from an *.mpk* file. +* We fixed a [known issue](/releasenotes/studio-pro/11.12/#ki-guids) where storage GUIDs were not retained during module update from an *.mpk* file. * We fixed an issue where files bigger than 5 MB could not be downloaded when encryption was enabled for S3. (Ticket 279197) * We fixed an issue where clearing the selection with a JavaScript action did not always work for data widgets with **Keep selection** enabled, such as the Data Grid 2 widget. The previously selected rows would become selected again. (Ticket 280575) * We fixed an issue where an optional microflow, nanoflow, or page parameter that was explicitly configured as "(none)" would still receive a default value at runtime instead of being left empty. (Ticket 284412) @@ -96,7 +97,7 @@ weight: 84 * We fixed an issue where Strict Mode would not work correctly with certain Client APIs and nanoflow actions in offline apps. (Tickets 287100, 282233) * We fixed an issue with sorting and filtering on microflow, nanoflow, or association data sources. A client error dialog would appear if users sorted or filtered by an attribute or association they could not access due to access rule constraints. (Ticket 287118) * We fixed an issue where a row extracted with **Extract to new grid** could not be selected in the page editor and had no **Insert row above/below** options in the context menu. Inserting a row in the extracted grid placed it at the wrong position or caused an error. (Ticket 287120) -* We fixed an issue where a Custom Chart in a pop-up window would flood the console with type errors when users hovered over data points. (Ticket 287153) +* We fixed an issue where a Custom Chart in a pop-up window flooded the console with type errors when users hovered over data points. (Ticket 287153) * We fixed an issue where signing out of native and offline-first web apps could show a database error when other database operations were still running. (Ticket 288359) * We fixed an issue where offline synchronization operation IDs changed between builds, which could cause synchronization errors after updating a native app. (Ticket 288359) * We fixed an issue where missing file content on the server caused a microflow's **Sync to device** action to fail in offline apps instead of skipping the affected objects and synchronizing the remaining objects. (Ticket 288772) @@ -110,9 +111,9 @@ weight: 84 * We fixed an issue where renaming a document could make Studio Pro unresponsive for 30 seconds and then fail with a timeout error while the Changes pane was open. * We fixed an issue where the **Fetch** menu item was enabled for apps that are not under version control. * We fixed an issue where undoing an entity rename did not revert the automatically updated references to that entity, its attributes, and its associations in microflows, pages, and access rules. This left consistency errors pointing at names that no longer existed until the references were corrected manually. -* We fixed an issue where consistency errors would not show up after changing security settings. +* We fixed an issue where consistency errors did not show up after changing security settings. * We fixed an issue where the runtime could start Change Data Capture snapshot processing when no CDC document was configured or when the Kafka Producer could not be created. -* We fixed an issue where entity access rules would contain invalid module role references after copying or moving an entity to another module, preventing users from selecting and updating roles in the access rule editor. +* We fixed an issue where entity access rules contained invalid module role references after copying or moving an entity to another module, preventing users from selecting and updating roles in the access rule editor. * In the logic editors, the expression wizard no longer selects a disabled expression type (such as 'Constant' for while loops) when it opens. * In the logic editors, we now check microflow or nanoflow return values for errors if the return type is set to Nothing. This prevents errors during deployment. * We fixed an issue in the logic editors where a selected flow, or a flow that was being changed, could be hidden behind other flows and elements. Such flows are now rendered on top. @@ -125,7 +126,6 @@ weight: 84 * We fixed a known issue where storage GUIDs were not retained during module update from an MPK file. * We fixed an issue where running `mx module-import`, `mx update-widgets`, or `mx rename-design-properties` on an app using MPR format version 2 converted it to version 1. * We fixed an issue where Maia MCP server tool selection was lost after signing out of the Mendix Platform and signing back in. -* We improved the Studio Pro MCP Server connection handling. If you have an MCP client (such as Claude Code) connected to Studio Pro, disconnect and reconnect it after updating. * We fixed an issue where running different Find Results-related operations could incorrectly reuse an unrelated Find Results tag. * We fixed an issue in the modernized Find Results pane where an older result tag could show information from a more recent search. Each tag now keeps the search it was created with, including when switching back to it or refreshing the results. * We fixed an issue where comparing two lists with `=` in a client-evaluated expression (for example, in a nanoflow) used a membership check instead of true equality. Lists with duplicate elements, or the same elements in a different order, could incorrectly be considered equal. For example, `[1, 2] = [2, 1]` previously evaluated to `true`; it now evaluates to `false`, matching microflow behavior.