Skip to Content

Changes for page 272 - Driven Datamodel

Last modified by Erik Bakker on 2026/07/14 12:42
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 321.1
edited by Erik Bakker
on 2026/03/10 12:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -272 - Driven Datamodel
1 +263 - User Update
Content
... ... @@ -1,22 +1,19 @@
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 +This release includes many user-driven updates to our platform to enhance your everyday work.
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>>doc:Main.Release Information.Release Blogs.263 - User Update.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 +* Create - Flow Designer: Improved the help text of the advanced ‘Match value’ attribute of the XPath filter, so it is clear how this option of the XPath filter can be used. (#1542)
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)
15 -
16 -
17 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)
11 +* Deploy - Deployment plan execution: The failure message shown during release preparation has been improved to be more descriptive. (#1568)
12 +* Deploy - Releases: We fixed an issue where the UI of the Create phase and Deploy phase were not aligned since the Releases screen did not show the new additions, but you can find them in the Release details popup. (#1675)
13 +* Manage - Explore - Topic browser: We fixed two problems with the topic browser.
14 +** When navigating to the last page of messages on a topic’s partition, the amount of messages shown in the paging will now correspond to the number of messages on that partition (#1714)
15 +** The first page of messages on a topic’s partition will now include the last message, with offset 1 below the ‘last offset’.
16 +* Manage - Export - Data sink: When opening this page on an empty data sink bucket, there will be a warning on top of the page (“no results found”). (#1096)
17 +==== Remarks ====
18 +
19 +* General - Portal: We have removed part of our platform's functionality as it was not used anymore.