Skip to Content
Last modified by Erik Bakker on 2026/05/06 23:07
From version 333.1
edited by Erik Bakker
on 2026/05/06 23:07
Change comment: There is no comment for this version
To version 75.1
edited by Erik Bakker
on 2023/04/28 09:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -267 - Navigational Nirvana
1 +196 - The Last Post
Content
... ... @@ -1,17 +1,39 @@
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 +Here is our first release of this quarter. We have delivered additional minor (bug) fixes in this release and released the Live Flow testing feature. The last is a real improvement during the development process of a flow. Furthermore, you will find several enhancements in working in nextGen environments.
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.196 - The Last Post.WebHome||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 +* Create - Flow Testing: Till now, Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), running them, and comparing the actual and expected messages. In this release, "Live Mode Testing" is introduced, making testing communication with an actual "live" endpoint possible. As a result, an "HTTP outbound gateway" can be set in "Live Mode." When you do this, the HTTP outbound gateway will send its request to the endpoint. Consequently, the response will be handled by the flow in the flow test so you can determine whether the actual endpoint behaves as expected.
12 12  
13 -==== Bug fixes ====
9 +=====Major 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)
11 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target= "blank"]] for more information.
12 +
13 +=====Minor changes=====
14 +
15 +* Design - Store: You can encounter a warning message when you import a transformation from the store because your imported transformation requires information from the related store fragment. To avoid a non-functional transformation in the Create phase, you should include that store fragment. Afterward, we will update your default flow component transformer to make it work correctly.
16 +* Design - Store: We updated importing to help you avoid an error while importing store items that will break your message definition in some cases.
17 +* Design - Store: We fixed an issue that you import the message definition(s), and a specialized DataType of imported message definition(s) is not matched with the exported message definition(s). Now, they are matched, and your transformation won't get issues.
18 +* Create - Store: We automatically excluded resources that are not good enough from the exporting wizard. Then you will find it easy to recognize a problem and avoid creating unusable store items.
19 +* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can only change the CDM message definition, Gateway message definition, or even Event streaming message definition with the proper rights. (#690)
20 +* Create - Flow designer: Model resources tab removed on the resources page when adding a resource to a validating filter. (#921)
21 +* Create - Flow designer: Improve the responsiveness of the resources tab on the right panel.
22 +* Create - Flow Designer: Resources in the "Unused resources" section can be marked as used when components refer to the resources through property placeholders or in custom SPeL expressions.
23 +* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests if that parameter was not supplied, so please reset your entry flow to apply the fix.
24 +* Create - API Gateway: We fixed an issue where API-Key secured requests would fail with error code 500 instead of code 401 if no API-Key was supplied. Please reset your entry flow to apply the fix.
25 +* Create - Resources: When viewing a resource, its full name will be shown, removing the need to download the resource to obtain its name. (#922)
26 +* Deploy - Releases: We reduced the time it takes to prepare a release before it can be deployed. The process of building runtime images has been optimized.
27 +* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
28 +* Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543)
29 +* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are run.
30 +* Manage - Explore: A new queue delete button is added. This button is only visible to authorized personnel.
31 +* Administration -User management: Company contact can edit permissions of models that fall under child companies. (#895)
32 +* Administration - Overview: Contracts page removed. (#907)
33 +
34 +====Bug fixes====
35 +
36 +* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They better explain what you need them for and mention essential security considerations.
37 +* Create - Flow designer: Various minor (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
38 +* Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514)
39 +* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs. (#940)