Skip to Content

Changes for page 272 - Driven Datamodel

Last modified by Erik Bakker on 2026/07/14 12:42
From version 90.1
edited by Erik Bakker
on 2023/06/20 07:54
Change comment: There is no comment for this version
To version 345.1
edited by Erik Bakker
on 2026/07/14 12:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -200 - Uncharted Territories
1 +272 - Driven Datamodel
Content
... ... @@ -1,17 +1,22 @@
1 -In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture, and others.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.200 - Uncharted Territories.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.272 - Driven Datamodel.WebHome||target="blank"]].
4 4  
5 -=====Minor changes=====
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.
6 6  
7 -* Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. It is replaced by the automated upgrade feature.
8 -* Deploy - Deployment plan: We updated the place to display the logs in the right pane of the deployment plan to make it more compatible with the new runtime generation. Now, you can see all related logs with your deployment. By default, we only show some important logs, such as error logs, warning logs, and started runtime information logs. You can use the filter logs icons at the top of the list to show more information.
9 -* Create - Flow Designer: it is possible to select multiple components by area selection on the area which has scrollbar.
11 +==== Minor Changes ====
10 10  
11 -====Bug fixes====
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)
12 12  
13 -* Deploy - Architecture: We improved timeout settings to give Stop, Restart and Reset runtime actions, enough time to execute. (#957)
14 -* Design - Store: Import into design from store is possible, even if the integration is not in Create yet.
15 -* Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases. Note that this functionality requires a newly deployed release. (#956)
16 -* Manage - Manage Dashboards: The speed of loading the screen is improved greatly for all models. This is most noticeably for larger models. (#964)
17 17  
17 +==== Bug fixes ====
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)