Skip to content

Commit 74bd08e

Browse files
committed
re-order fixes
1 parent 2271ee1 commit 74bd08e

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

  • content/en/docs/releasenotes/studio-pro/10

content/en/docs/releasenotes/studio-pro/10/10.24.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -27,19 +27,19 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for
2727

2828
* We upgraded the JDBC driver for Microsoft SQL Server to version 12.8.2, because of [CVE-2025-59250](https://www.cve.org/CVERecord?id=CVE-2025-59250).
2929
* 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.
30+
- We fixed an issue where OQL query parsing would fail if the query included a numeric WHEN clause without an accompanying ELSE condition. (Ticket 255719)
3031
- We fixed an issue where XPath access rules on a view entity could lead to an "Object hash is invalid!" error. (Ticket 255889)
3132
- We fixed an issue that caused the microflow execution to abort when the **Sync to Device** action failed in offline apps due to missing files. (Ticket 261053)
3233
- We fixed an issue where undoing a widget update could lead to an inconsistent model, causing an error when attempting to reopen the project. We now prevent **Undo** actions for widget updates to safeguard against similar issues. (Tickets 256004, 260822)
34+
- We fixed an issue that prevented a dialog from closing when users pressed <kbd>Escape</kbd> while editing an [access rule](/refguide/access-rules/). (Ticket 257016)
3335
- We fixed an issue where conditional editability expressions in snippet calls incorrectly references variables when nested snippets were involved. (Tickets 257120, 262408)
36+
- We fixed an issue where source maps for pluggable widgets were not included correctly in the React client bundle when **Optimize bundle** is set to **No**. (Ticket 261353)
37+
- We fixed an issue where widgets with unbounded dynamic imports (for example, `await import(path);`) would result in a bundling error when using the React client. They are now marked as external, which means they will be resolved when the widget is loaded in the browser. (Ticket 261630)
38+
- We fixed an issue for the Message Definitions editor where custom values for editable fields like 'External Name' disappeared. (Tickets 263144, 263609, 263817, 264535, 264805, 264850)
3439
- We now allow first-time users to use Studio Pro without logging in.
3540
- We fixed memory leaks related to the style document editor.
36-
- We fixed an issue where OQL query parsing would fail if the query included a numeric WHEN clause without an accompanying ELSE condition. (Ticket #255719)
37-
- We fixed an issue for the Message Definitions editor where custom values for editable fields like 'External Name' disappeared. (Tickets 263144, 263609, 263817, 264535, 264805, 264850)
3841
- We fixed an issue in consumed OData services in Studio Pro where importing a metadata file with incorrect XML namespaces would show an "Importing..." progress dialog without ever completing the import.
3942
- We fixed an issue where `Core.getLicenseInformation().products()` did not return a numeric value if the value was larger than `2147483647`.
40-
- We fixed an issue that prevented a dialog from closing when users pressed <kbd>Escape</kbd> while editing an [access rule](/refguide/access-rules/). (Ticket 257016)
41-
- We fixed an issue where source maps for pluggable widgets were not included correctly in the React client bundle when **Optimize bundle** is set to **No**. (Ticket 261353)
42-
- We fixed an issue where widgets with unbounded dynamic imports (for example, `await import(path);`) would result in a bundling error when using the React client. They are now marked as external, which means they will be resolved when the widget is loaded in the browser. (Ticket 261630)
4343
- We fixed a bug where nanoflows would not be exported when re-added to a page after a full deployment cycle. The issue occurred when a nanoflow was removed from a page during hot-reload, followed by a full deployment, and then re-added during another hot-reload.
4444

4545
## 10.24.11 {#102411}

0 commit comments

Comments
 (0)