Skip to Content

Changes for page 273 - Squash Squash

Last modified by Erik Bakker on 2026/07/27 11:44
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 284.1
edited by Erik Bakker
on 2025/10/09 11:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -272 - Driven Datamodel
1 +254 - Other One
Content
... ... @@ -1,22 +1,23 @@
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 features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready. Additionally, we will release new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** to update our underlying libraries.
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.254 - Other One.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 +* General - Cloud Template: A new [[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]], for every type of **cloud** we offer, is available that updates underlying libraries.
8 +* General - eMagiz Store: Introduced a new state generation license type for store items. This license is now required for models intending to utilize store items that depend on state generation capabilities. (#1400)
9 +* Capture - Settings - Integrations: Update column label to be more consistent (#1710)
10 +* Design - Data model: When you change the data type of the attribute in the Design phase while a flow has a transformation in Create, before saving the changes, you will see the confirmation popup with the warning message because the changes will impact your transformation in Create. (#1163)
11 +* Create - Flow testing: Specifying the type of a header on a test message has been made simpler: Instead of having to type the class name, the most common types can now be selected in a dropdown menu instead. It is still possible to provide a custom type. (#1711)
12 +* Deploy - Architecture: We added the refresh button in the footer of the “Runtime details” popup in the Deploy Architecture. (#1708)
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 +==== Bug fixes ====
15 15  
16 +* Create - Flow designer: Resolved the issue where resizing columns in the ‘Java mail sender’ support object would make the columns ‘stick’ to the mouse. (#1320)
17 +* Create - Flow designer: Several broken Spring documentation references in help texts are updated to new documentation pages. (#1534)
18 +* Deploy - Releases: Changed the text on the wrench icon when hovering for the create phase release to “Property configuration“ to differentiate it from regular property releases. (#1571)
19 +* Deploy - Releases: Resolved the issue where resizing columns in the 'Compare properties' would prevent further interactions with the popup. (#1668)
20 +* Deploy - Releases: Warning message showing the set advised number of flows per container is fixed to show the correct number when a release is approved for the next environment. (#1059)
21 +* Deploy - eMagiz Connector: Resolved the issue where, in some edge cases, downloading the latest release when staring the eMagiz Connector could lead to an error, preventing the connector from starting.
16 16  
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)