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 332.1
edited by Erik Bakker
on 2026/05/06 22:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -272 - Driven Datamodel
1 +267 - Navigational Nirvana
Content
... ... @@ -1,22 +1,17 @@
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 significant improvements regarding navigation options within the Create phase. This includes improvements in navigating between flows and in creating context between properties and flows. On top of that, it introduces a structured and simple way to navigate to our API MAM functionality for all models using the API Pattern in combination with the OAuth security option. Subsequently, we have also launched a new [[runtime image>>doc:Main.Release Information.Runtime Images.V352.WebHome||target="blank"]] for **all** customers. Enjoy reading our latest updates on the platform.
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.267 - Navigational Nirvana.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 ====
10 10  
11 -==== Minor Changes ====
7 +* Create - Flow Designer: Users can now navigate between flows using JMS and Kafka components. Navigation is based on the configured **destination** (for JMS) or **topic** (for Kafka) defined on each component, allowing quick access to related flows. (#738)
8 +** This functionality is embedded within the flow entities. By right-clicking a JMS or Kafka component, users can select “**Show destination(s)**” or “**Show source(s)**”, depending on the component's direction, to navigate to the connected flows.
9 +** Note that the topic navigation only works for models running on DSH.
10 +* General - API MAM Migration: Migration wizard for API MAM for OAuth API gateway models. This migration wizard enables you to transform your API gateway environment to support multiple authentication methods (OAuth, API key, and basic auth).
11 +* Create - Properties: The Properties tab in the Create phase is introduced. The tab now displays all properties, and selecting a property reveals a list of flows that use it. From this list, you can navigate directly to a specific flow by double-clicking it or by clicking the Go to Flow icon on the right side of the row. (#1217)
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)
15 -
16 -
17 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)
15 +* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V352.WebHome||target="blank"]] for **all** customers is available.
16 +* Create - Add Integrations: Trying to add an integration to a system without applying its settings in Design Architecture shows an informative message. (#1535)
17 +* Create - Flow Designer: Fixed the issue of no longer being able to add headers to an XPath Header Enricher introduced with the previous release. (#1783)