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 35.1
edited by Erik Bakker
on 2022/12/06 16:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -272 - Driven Datamodel
1 +189 - Private Eye
Content
... ... @@ -1,22 +1,29 @@
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 a private store to our community and makes the latest runtime image available for our customers running on the 3rd generation architecture. Furthermore, we introduce several improvements to our 3rd generation runtime and its interaction with the portal.
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.189 - Private Eye.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 +* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
10 10  
11 -==== Minor Changes ====
8 +=====Major 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)
10 +* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your jms-server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
15 15  
12 +=====Minor changes=====
16 16  
17 -==== Bug fixes ====
14 +* Create - Event Streaming: Event streaming is now available for models migrating to the 3rd generation runtime.
15 +* Create - Transformation: source filter on attribute with empty field is more readable in read-only mode. (#732)
16 +* Create - Migration: Improved compatibility checks related to the 3rd generation runtime migration.
17 +* Deploy - Check properties: Informative error messages when saving or creating a property. (#576)
18 +* Deploy - Deployment plan: We improved the deployment plan to avoid crashing the server when executing a deployment plan.
19 +* Deploy - Architecture: Added reset feature for 3rd generation runtimes.
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)
21 +====Bug fixes====
22 +* Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows.
23 +* Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances.
24 +* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish.
25 +* Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798)
26 +* Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment.
27 +
28 +====Remarks====
29 +* Mendix Runtime has been upgraded to Mendix 9.19.0.