Changes for page 273 - Squash Squash
Last modified by Erik Bakker on 2026/07/27 11:44
From version 233.1
edited by Erik Bakker
on 2025/03/10 09:59
on 2025/03/10 09:59
Change comment:
There is no comment for this version
To version 345.1
edited by Erik Bakker
on 2026/07/14 12:42
on 2026/07/14 12:42
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 40-SpringCleaning1 +272 - Driven Datamodel - Content
-
... ... @@ -1,13 +1,22 @@ 1 - In thelastsprint, we focused on tidyingupourhouse toprepareforvariouscoolthings laterthisyear.As a result, wehave aseriesofimprovementsandbugfixes foryouto enjoy.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.2 40-SpringCleaning.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 -====Minor Changes==== 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 -* Overall UI/UX: Alerts / Notifications now have an icon before the text to further emphasize the meaning. 8 -* Overall UI/UX: We have updated our badge, switch, and progress bar components. 11 +==== Minor Changes ==== 9 9 10 -====Bug fixes==== 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) 11 11 12 -* Create - Flow Creation: We have changed the auto-creation behavior for entry gates. This means we now avoid creating functionality in these entry gates only relevant for flows running inside a Mendix app. 13 -* Create - Reset Infra: Infra flows for systems labeled as a "Mendix Connector" can now be reset once more under all circumstances, including when your model utilizes the code mapping functionality. 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)