Skip to Content

Changes for page 268 - Underlying Update

Last modified by Erik Bakker on 2026/05/18 16:45
From version 332.1
edited by Erik Bakker
on 2026/05/06 22:38
Change comment: There is no comment for this version
To version 188.1
edited by CarlijnKokkeler
on 2024/01/15 14:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -267 - Navigational Nirvana
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,17 +1,19 @@
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.
1 +In the last sprint cycle, we focused on ....
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.267 - Navigational Nirvana.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4 4  
5 -==== New features ====
5 +=====New features=====
6 6  
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)
7 +* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
8 +* Create - Flow Designer: New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
9 +* Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
12 12  
13 -==== Bug fixes ====
11 +=====Minor changes=====
14 14  
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)
13 +
14 +====Bug fixes====
15 +
16 +* Design - Message Mapping: The message merging tool has been fixed to allow merging a store item message model into your own message models.
17 +* Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements.
18 +
19 +