Skip to Content

Changes for page 245 - Limited Exposure

Last modified by Erik Bakker on 2025/05/21 09:01
From version 23.1
edited by Erik Bakker
on 2022/11/21 13:13
Change comment: There is no comment for this version
To version 252.1
edited by Erik Bakker
on 2025/05/19 15:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +245 - Limited Exposure
Content
... ... @@ -1,25 +1,15 @@
1 -The release brings several improvements to our 3rd generation runtime and the interaction with it. On top of that, we have several feedback items and bug fixes.
1 +In the last sprint, we released increased stability on Windows runtimes. This means that those runtimes are now better limited in the memory they can utilize to prevent resource limitations on the machine level. Furthermore, we introduced several small improvements on the platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.245 - Limited Exposure.WebHome||target= "blank"]].
4 4  
5 -=====New features=====
6 -* Design - Store: It is now possible to import Transformations and Data Models from the store into a model.
7 -** The Design Store can also be opened from the Mapping and Data Model screens.
8 -** The Design Store now offers search options for store items, including Transformations and Data Models.
9 -** When importing a Store item with a Transformation or Data Model, a new merge tool is available to link the Store Items data model to the users' data model or to add new attributes/entities to the user data model.
10 -** When importing a Store item with a data model that has been previously linked, the links are automatically restored, allowing for easy updating of store-based Integrations and easier installation of multiple Store items with the same data model.
5 +====Minor Changes====
11 11  
12 -=====Minor changes=====
7 +* Deploy - General: For current deployed Windows machines, the calculation of the memory limit of containers is updated, which will prevent memory leaks.
8 +* Deploy - Architecture: You can now manually set the memory of your on-premise machine in design architecture. This memory is considered when checking the machine's health in "Deploy architecture."
9 +* Q&A Forum - Moderation: Q&A Forum Moderators can choose to receive notifications by email about newly posted questions on the forum. (#1401)
13 13  
14 -* Create - Flow Designer: Code mapping is now available for models migrating to the 3rd generation runtime
15 -* Create - eMagiz Mendix Connector exit: Download buttons are added for non-legacy eMagiz Mendix connectors.
16 -* Create - Overview: You will now see your errors within a flow but on the Create - Overview. To activate this, open your flow, and the number of errors you have in it, if any, will update so that next time, you don't have to navigate inside the flow to check how many alerts you have.
17 -
18 -
19 19  ====Bug fixes====
20 -* Design - Store: Importing store items from response messages doesn't cause issues anymore.
21 -* Design - Store: Importing response messages and transformation to API integration is possible.
22 -* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document. (#783)
23 -* Create - Flow Designer: Ensure that the copy and pasting experience works for all flows.
24 -* Create - Flow Designer - Store: We fixed the maintaining selection of flow fragments from the store.
25 -* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed. (#744)
12 +
13 +* Create - Flow designer: The help text for the "value expression" field for the "duplicate detector" support object better reflects the purpose of that field while also providing practical examples. (#1376)
14 +* Create - Flow Designer: The help text for the "virtual root "field of the "JSON source factory "support object better reflects the functionality and behavior of the field while also stating that arrays on the root level are not supported. (#1459)
15 +* General - User Access: Users with view rights in Deploy and Manage (but no rights in the other phases) can now see data in Manage grids. (#1525)