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 346.1
edited by Erik Bakker
on 2026/07/27 08:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -272 - Driven Datamodel
1 +273 - Squash Squash
Content
... ... @@ -1,16 +1,10 @@
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 includes various smaller improvements throughout the various phases of the platform. On top of that, we have updated certain parts of our Mendix project to their respective latest version.
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.273 - Squash Squash.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.
10 -
11 11  ==== 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)
7 +* Deploy - History (Releases): Introduced various changes to this overview to make the information we show here more specific. The main changes are that we show a full timestamp in the “When” column instead of the date itself, and the “eye” icon is only present when the registered audit log exceeds a predefined length. (#1779)
14 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 15  
16 16  
... ... @@ -20,3 +20,7 @@
20 20  * Create - Overview: Number of errors in transformation is reflected correctly in offramp flow.
21 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 22  * Deploy - Releases (Missing Properties): Nested emagiz properties are removed from the missing properties page. (#1803)
17 +
18 +==== Remarks ====
19 +
20 +* Updated various UI related modules within our Mendix project to their respective latest version.