Skip to Content

Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
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 158.1
edited by Carlijn Kokkeler
on 2023/11/21 12:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,25 +1,31 @@
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 cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
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.209 - Max Verstappen.WebHome||target="blank"]].
4 4  
5 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.
11 11  
7 +* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties.
8 +* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 +* All - The next generation architecture is the default now. New models will use this generation as default.
10 +
11 +
12 +
12 12  =====Minor changes=====
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.
15 +* Deploy - Releases: We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
16 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
17 +* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
17 17  
18 18  
20 +
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)
22 +
23 +====Infra and image changes====
24 +
25 +* Infra: New logging feature enabling us to make better choices in encryption standards.
26 +
27 +
28 +
29 +
30 +
31 +