Skip to Content
Last modified by Erik Bakker on 2026/05/06 23:07
From version 45.1
edited by Erik Bakker
on 2023/01/31 14:39
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 -191 - Fifty Fifty
1 +267 - Navigational Nirvana
Content
... ... @@ -1,36 +1,17 @@
1 -The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
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.191 - Fifty Fifty.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 -* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
7 -** Error Message is to evaluate the headers of the original message which resulted in an error.
8 -** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
9 -** Queue Consumers is to configure for queues where more than 1 consumer is expected.
10 -** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
11 -** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow.
5 +==== New features ====
12 12  
13 -=====Major 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)
14 14  
15 -* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
13 +==== Bug fixes ====
16 16  
17 -=====Minor changes=====
18 -
19 -* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes.
20 -* Create - Flow designer: sensitive information stored in property values is masked. (#790)
21 -* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions.
22 -* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
23 -* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
24 -* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828)
25 -* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
26 -* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
27 -* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
28 -
29 -====Bug fixes====
30 -* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
31 -* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793)
32 -* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
33 -* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
34 -* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
35 -* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
36 -
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)