Changes for page 272 - Driven Datamodel

Last modified by Erik Bakker on 2026/07/14 12:42

From version 192.1
edited by CarlijnKokkeler
on 2024/01/29 15:39
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 -213 - Joyful Journeys
1 +272 - Driven Datamodel
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,31 +1,22 @@
1 -In the last sprint cycle, we focused on improving pop-up messages to improve the user experience. Moreover, we did several alignment & formatting improvements. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
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.213 - Joyful Journeys||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 -=====New features=====
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 -* Home - Q&A: The option to search by pressing the Enter key has been added.
11 +==== Minor Changes ====
8 8  
9 -=====Minor changes=====
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)
10 10  
11 -* All - Input fields: Multiple input fields have been updated to expand when the amount of characters exceeds the default size. (#822)
12 -* Design - Message: The tooltip for the optional/required toggle has been improved. (#1172)
13 -* Create - Transformation: UI improvements for static input components have been done. (#1172)
14 -* Create - Resources: A button "Update flows" has been added to update versions of all flows in which a resource is used. (#1129)
15 -* Deploy - Releases: When a new property release is created, this property release can now not only be viewed but also release properties can be deleted. (#1031)
16 -* Deploy - Containers: The error message that is displayed when deleting a runtime is now more descriptive. (#1053)
17 -* Deploy - Runtime overview: Insight into intended and actual deployments has been improved.
18 -* Deploy - Architecture: It is now possible to change the memory settings of a new container before pressing "Apply to environment". (#968)
19 -* Deploy - Architecture: Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. (#977)
20 -* Deploy - Architecture: The formatting of action messages regarding changes in retention bytes/hours has been improved.
21 -* Manage - Explore: The error messages that may be displayed when using wiretaps and the debugger have been improved.
22 22  
23 -====Bug fixes====
17 +==== Bug fixes ====
24 24  
25 -* Create - Flow Designer: We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). (#1021)
26 -* Create - Flow Designer: A bug has been fixed where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. (#1030)
27 -* Deploy - Architecture: During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
28 -* Manage - Monitoring: The correct number of cache hits and misses are now shown in the state generation statistics. (#1161)
29 -* Manage - Monitoring: We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
30 -* Manage - Explorer: We aligned all timestamp formatting to yyyy-MM-dd HH:mm:ss.SSS. (#1151)
31 -* Manage - Notification settings: Internal recipients are now added correctly.
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)