Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
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 143.1
edited by Carlijn Kokkeler
on 2023/10/23 16:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,25 +1,29 @@
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 delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
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.207 - Aligned State .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.
11 -
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.
7 +* Design - Message Mapping: The button 'Import from Store' will directly open the store.
8 +* Design - Performance: Performance improvements for the Flow Designer have been implemented.
9 +Create-Flowdesigner] When importing items from the store, flowfragments that are hidden in design will be listed under the versions in create.
10 +* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
11 +* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
12 +* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
13 +* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
14 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
15 +* Manage - Data Sink: Data sink page has been moved to the “Explore” tab. (#946)
16 +* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
17 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
18 +* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
17 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)
21 +
22 +* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
23 +* Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term.
24 +
25 +
26 +
27 +=====Infra and image changes=====
28 +
29 +* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.