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 18.1
edited by Erik Bakker
on 2022/11/08 08:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -272 - Driven Datamodel
1 +187 - Integration Sponsor
Content
... ... @@ -1,22 +1,25 @@
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 +The release brings the next step of the Design store to the public and releases a new version of the eMagiz Mendix Connector that unlocks those using it to migrate to the next generation runtime. On top of that, we have several feedback items and bug fixes.
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>>Main.Release Information.Release Blogs.187 - Integration Sponsor.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 +=====New features=====
6 +* Design - Store: It is now possible to import Transformations and Data Models from the Store into a model.
7 +** The Design Store can now be opened from the Mapping and Data Model screens as well.
8 +** The Design Store now offers search options to find store items that include Transformations and/or Data Models.
9 +** When importing a Store item with a Transformation and/or Data Model a new merge tool is available to link the Store Items data model to the users data model or to add new attributes/entities to the user data model.
10 +** When importing a Store item with a data model that has been previously linked the links are automatically restored allowing for easy updating of store based Integrations and for easier installation of multiple Store items with the same data model.
10 10  
11 -==== Minor Changes ====
12 +=====Minor changes=====
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)
14 +* Create - Flow designer: Improved the help texts of the Kafka components to better explain certain performance and load-balancing considerations, and added detailed information how messages (including headers) are converted to/from Kafka records.
15 +* Create - eMagiz Mendix Connector exit: Download buttons are added for non legacy eMagiz Mendix connectors
16 +* Create - Overview: You will now be able to see the errors that you have within a flow but on the integration widget. To do this, go into your flow and the number of errors you have in it, if any, will update so that next time you don’t have to navigate inside the flow to check how many alerts you have.
15 15  
16 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)
19 +====Bug fixes====
20 +* Design - Store: Importing store item from response messages doesn't cause issues anymore
21 +* Design - Store: Importing response message and transformation to Api integration is possible
22 +* Design - API Gateway: The order of attributes in gateway messages were not always the same as the order in the generated Open API document.
23 +* Create - Flow Designer: Fix bugs when copy and paste components in G3 configuration
24 +* Create - Flow designer - Store: We fixed the maintaining selection of flow flagment from Store.
25 +* Manage - Exceptions of error messages: The count of error messages per exception class are now displayed (#744)