Skip to Content

Changes for page 272 - Driven Datamodel

Last modified by Erik Bakker on 2026/07/14 12:42
From version 289.2
edited by Erik Bakker
on 2025/11/04 12:44
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 -256 - Power Up
1 +272 - Driven Datamodel
Content
... ... @@ -1,15 +1,22 @@
1 -This release features various updates to our platform, with a user-centric focus, as we work on improved functionality for our new event streaming broker and API Gateway. All those improvements will be shared in the future once everything is ready. Additionally, we want to raise awareness that several new **[[environment templates>>> Main.Release Information.Cloud Templates.WebHome||target="blank"]]** have been released that need to be updated before **December, 14th**. So if you have yet to update please take the necessary actions.
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>>doc:Main.Release Information.Release Blogs.256 - Power Up.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 -==== Bug fixes ====
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 -* Design - System Message: Improved performance of saving entities whith a large number of attributes. (#1731)
8 -* Design - Store: Two fixes on importing store items for synchronous messages. (#1579)
9 -** From store functionality for API Gateway is restored.
10 -** Additionally, users can import store item to synchronous system message - response message.
11 -* Design - Create - System Message (API integrations) - The request system message correctly displays the message definition (#1713)
12 -* Create - Add Integrations: We have fixed a bug where some Mendix systems could face an error when trying to add an event streaming integration in Create.
13 -* Deploy - Containers: Debug icon has on hover text (#1725)
14 -* Manage - Alerting: Partial words from an alert's description can be searched and still return accurate results. (#1726)
11 +==== Minor Changes ====
15 15  
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 +==== 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)