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 15.1
edited by Erik Bakker
on 2022/10/28 16:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -272 - Driven Datamodel
1 +186 - Daemon Switch
Content
... ... @@ -1,22 +1,35 @@
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 new monitoring stack to fruition and various updates to handling multiple namespaces. On top of that, we have released a slew of smaller 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.186 - Daemon Switch.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 +* Generic - New monitoring stack: As of this release, you can run on the new monitoring stack. For more information on becoming an early adopter, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
10 10  
11 -==== Minor Changes ====
8 +=====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)
10 +* Create - Flow designer: You can now see who/when a resource was changed on a resource view page.
11 +* Design - Solution: You will see a warning in the Solution view on operation if it is not connected to a backend API operation or in "Transformation" mode.
12 +* Create - Flow designer: You can see all related configurations that use a specific resource when viewing the details of the resource.
13 +* Design - API Gateway: Changes in your Gateway messages are reflected directly in your OpenAPI JSON document.
14 +* Model Dashboard - Going to manage from the model dashboard now loads the error message dashboard without having to click on the error messages dashboard explicitly
15 +* Create - Flow testing: The name of the starting point in the flow testing result tab is matched with the component type.
16 +* Deploy - Releases: The automated flow test pop-up can now be closed by pressing "Enter."
17 +* Deploy - Properties: Password-type properties are masked in the unused properties pop-up.
18 +* Deploy - User management: "Generate Keystore" button is renamed "Download Keystore," and the file name contains environment information.
19 +* Create - Flow Testing: Added a button to display the content of a selected trace message in a pop-out.
20 +* Deploy - Properties: You can use enter key to search on the property overview page.
21 +* Create - Flow designer: Increased size of the SpEL expression input field of standard transformer component.
22 +* Create - Flow Designer: Show generated resources toggle is not disabled by default; your preference for showing or hiding generated resources will be saved.
23 +* Administration - Licenses: Added event streaming storage usage of your models.
24 +* Store: Compatibility check is added, which prevents importing G3 store items into G2 flow/integration
25 +* General: Improved help texts explaining options and screens related to the new runtime architecture or the migration towards it.
15 15  
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)
27 +====Bug fixes====
28 +* Deploy - Properties: Improved the layout of the cron trigger generator page
29 +* Deploy - Properties: Generating a password or CRON trigger will not reset the runtime field
30 +* Create - Flow designer: While editing an exit flow, the system message is not editable.
31 +* Design - Integration designer: For event streaming integrations, switching between Design Mapping and Create Transformation sometimes did not work.
32 +* Create - Transformation: For event streaming integrations, the 'Start editing' button sometimes did not work.
33 +* Create - Flow designer: Comparing two flow versions works again.
34 +* Create- Flow Designer: When creating my initial version of a flow, the notification pop-up shows the correct information.
35 +* Create - Flow Designer: All relevant support objects will be highlighted when selecting a support object.