Changes for page 273 - Squash Squash

Last modified by Erik Bakker on 2026/07/27 11:44

From version 345.1
edited by Erik Bakker
on 2026/07/14 12:42
Change comment: There is no comment for this version
To version 144.1
edited by CarlijnKokkeler
on 2023/10/23 16:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -272 - Driven Datamodel
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,22 +1,31 @@
1 -This release includes improvements to managing relationships at the data model level in Design. On top of that, various other user improvements are introduced. Furthermore, new users are created at the container level in preparation for our upcoming feature development.
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>>doc:Main.Release Information.Release Blogs.272 - Driven Datamodel.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 - Data model: On the data model level, we introduce two new context menu items allowing the user to add and manage relationships between entities. This option is available for all data model levels in Design.
7 -** A new **Manage relationships** option is added to the context menu in the data model editor. When editing a data model, right-clicking an entity displays the **Manage relationships** action, which opens a pop-up to manage the relationships associated with the selected entity. The dialog allows relationships to be added, edited, or deleted.
8 -** A new **Add relationship** option is added to the context menu in the data model editor. When editing a data model, right-clicking an entity displays the **Add relationship** action, which opens a pop-up to add a relationship to the selected entity.
9 -* Deploy: A container-level user is introduced for each container in the deploy phase. This user will allow us to connect to other parts of our eMagiz infrastructure via a more fine-grained authorization procedure.
5 +=====Minor changes=====
10 10  
11 -==== Minor Changes ====
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 - Flow Designer: When importing items from the store, flowfragments that are hidden in Design will be listed under the versions in Create. (#1044)
10 +* Create - Flow Designer: Resources without name won't trigger error messages when users select components. (#950)
11 +* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
12 +* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
13 +* 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)
14 +* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
15 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
16 +* Manage - Data Sink: Data sink page has been moved to the “Explore” tab. (#946)
17 +* 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.
18 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
19 +* 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)
12 12  
13 -* Create - Flow Designer: When saving a flow version, we determine whether related eMagiz resources (i.e., your message definition and transformation) require an update. If not, we do not regenerate them. As a result, saving flow versions has become faster, especially when you do not make changes to those resources. (#1645)
14 -* Create - Flow Designer (OAuth Interceptor): Various help texts for this component have been updated to provide additional clarity on its functionality and more advanced configurations. (#1761)
21 +====Bug fixes====
15 15  
23 +* 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)
24 +* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
25 +* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087)
26 +* Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term.
16 16  
17 -==== Bug fixes ====
18 18  
19 -* Design - API Catalog (Operation - Response): A user can define an HTTP range as the HTTP Status Code for an operation's response, as suggested by the help text. (#1764)
20 -* Create - Overview: Number of errors in transformation is reflected correctly in offramp flow.
21 -* Create - Flow Designer (SFTP/FTP Outbound Channel Adapters): Ensured that the correct help text is shown for the Temporary remote directory configuration option. (#1754)
22 -* Deploy - Releases (Missing Properties): Nested emagiz properties are removed from the missing properties page. (#1803)
29 +=====Infra and image changes=====
30 +
31 +* 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.