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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -196 - The Last Post
1 +267 - Navigational Nirvana
Content
... ... @@ -1,35 +1,17 @@
1 -Here's our first release of this quarter. We have delivered additional small (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 improvements in the way of work for nextGen environments.
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>>Main.Release Information.Release Blogs.196 - The Last Post.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=====
5 +==== New features ====
6 6  
7 -* Create - Flow Testing: Till now, the Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), run them and compare the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with an actual "live" endpoint. As a result a “HTTP outbound gateway” can be set in “Live Mode”. When you do this, the HTTP outbound gateway will send its HTTP request to the actual 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.
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)
8 8  
9 -=====Minor changes=====
13 +==== Bug fixes ====
10 10  
11 -* Design - Store: You are able to see some warning messages when you import a transformation from store. Because your imported transformation is required some information from the related store fragment. You should include that store fragment to avoid a breaking transformation in Create phase after importing. Afterward, we will update your existing flow component transformer to make it work correctly.
12 -* Design - Store: We updated importing to help you avoiding an error during importing store item that will break your message definition in some special cases.
13 -* Design - Store: We fixed an issue that you import the message definition(s) and a specialized DataType of imported message definition(s) are not matched with the exported message definition(s). Now, they are matched and your transformation won't get issues.
14 -* Create - Store: We excluded automatically resources that are not good enough from the exporting wizard. Then you will easy to recognize a problem and avoid creating unusable store item.
15 -* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can not change CDM message definition, Gateway message definition, even Event streaming message definition without the proper right.
16 -* Create - Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
17 -* Create - Flow designer: Improve responsiveness of resources tab at right panel.
18 -* Create - Flow Designer: Resources in "Unused resources" section can be marked as used for the case that the resources are referred by components through property placeholders or in custom spel expressions.
19 -* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests, if that parameter was not supplied. Please reset your entry flow to apply the fix.
20 -* 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.
21 -* Create - Resources: When viewing a resource, its full name will be shown, removing the need to download the resource in order to obtain its name
22 -* 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.
23 -* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
24 -* Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’)
25 -* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
26 -* Manage - Explore: A new button to delete queue is added. This button is only visible for authorized personnel.
27 -* Administration -User management: Company contact can edit permissions of models that fall under child companies.
28 -* Administration - Overview: Contracts page removed.
29 -
30 -====Bug fixes====
31 -
32 -* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They now better explain what you need them for and mention important security considerations.
33 -* Create - Flow designer: Various small (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
34 -* Deploy - Releases: We fixed an issue, where after removing containers from a machine, during execution of the deployment plan, the removed containers are not recognized as change, causing the ‘Deploy machine’ step to be skipped.
35 -* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.
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)