Skip to Content

Changes for page 272 - Driven Datamodel

Last modified by Erik Bakker on 2026/07/14 12:42
From version 45.1
edited by Erik Bakker
on 2023/01/31 14: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 -191 - Fifty Fifty
1 +272 - Driven Datamodel
Content
... ... @@ -1,36 +1,22 @@
1 -The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
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.191 - Fifty Fifty.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 -=====New features=====
6 -* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
7 -** Error Message is to evaluate the headers of the original message which resulted in an error.
8 -** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
9 -** Queue Consumers is to configure for queues where more than 1 consumer is expected.
10 -** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
11 -** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow.
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.
12 12  
13 -=====Major changes=====
11 +==== Minor Changes ====
14 14  
15 -* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
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)
16 16  
17 -=====Minor changes=====
18 18  
19 -* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes.
20 -* Create - Flow designer: sensitive information stored in property values is masked. (#790)
21 -* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions.
22 -* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
23 -* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
24 -* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828)
25 -* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
26 -* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
27 -* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
17 +==== Bug fixes ====
28 28  
29 -====Bug fixes====
30 -* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
31 -* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793)
32 -* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
33 -* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
34 -* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
35 -* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
36 -
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)