Skip to content
Merged
Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion content/en/docs/releasenotes/studio-pro/11/11.12.md
Original file line number Diff line number Diff line change
Expand Up @@ -228,7 +228,7 @@ weight: 88
* 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).
* <a id="ki-guids-are-not-restored"></a> 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.
* <a id="ki-guids"></a> 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}

Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/releasenotes/studio-pro/11/11.14.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ We recommend that apps and Marketplace modules upgrade to Java 25.
* We fixed an issue in the modernized App Explorer where actions triggered with keyboard shortcuts were applied to the previously selected node.
* We fixed an issue where pressing <kbd>Escape</kbd> to close a modal dialog also closed the sidebar.
* We fixed an issue in the microflow editor where sometimes the loop was selected when trying to select elements inside the loop.
* We temporarily removed functionality that allowed you to update modules retaining customizations (introduced in 11.12.3) due to a [known issue](/releasenotes/studio-pro/11.12/#ki-guids-are-not-restored). The feature will be restored in a future release.
* We temporarily removed functionality that allowed you to update modules retaining customizations (introduced in 11.12.3) due to a [known issue](/releasenotes/studio-pro/11.12/#ki-guids). The feature will be restored in a future release.

### Deprecations

Expand Down
4 changes: 2 additions & 2 deletions content/en/docs/releasenotes/studio-pro/11/11.15.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,6 @@ weight: 85
# KI: "Maia Chat pane issue": MID-317
# KI: "BYO LLM": SPAM-435
# KI: "Mx.exe commands": SOLP-4224
# KI: "GUIDs are not restored": SOLP-4209
# KI: "Breaking client certificate auth": REST-751
---

Expand Down Expand Up @@ -169,10 +168,11 @@ You can set the default flow shape for all new sequence flows in the **App setti

### 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.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.
* The `mx.exe module-import replace` and `mx.exe module-import update` commands will not rescue storage GUIDs after a module update, which will result in data loss.
* 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 until a fixed version is released.
4 changes: 1 addition & 3 deletions content/en/docs/releasenotes/studio-pro/11/11.16.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,6 @@ weight: 84
# KI: "Maia Chat pane issue": MID-317
# KI: "BYO LLM": SPAM-435
# KI: "Mx.exe commands": SOLP-4224
# KI: "GUIDs are not restored": SOLP-4209
# KI: "Breaking client certificate auth": REST-751
---

Expand All @@ -29,7 +28,6 @@ weight: 84
* 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 `mx.exe module-import replace` and `mx.exe module-import update` commands will not rescue storage GUIDs after a module update, which will result in data loss.
* 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 until a fixed version is released.

## 11.16.0 {#11160}
Expand Down Expand Up @@ -88,6 +86,7 @@ weight: 84

### Fixes

* <a id="ki-fix-guids"></a>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)
Expand Down Expand Up @@ -143,5 +142,4 @@ weight: 84
* 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 `mx.exe module-import replace` and `mx.exe module-import update` commands will not rescue storage GUIDs after a module update, which will result in data loss.
* 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 until a fixed version is released.
Loading