Skip to Content

Changes for page 270 - Round Round

Last modified by Erik Bakker on 2026/06/15 10:37
From version 234.1
edited by Erik Bakker
on 2025/03/24 06:40
Change comment: There is no comment for this version
To version 341.1
edited by Erik Bakker
on 2026/06/15 10:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -241 - Wild West
1 +270 - Round Round
Content
... ... @@ -1,31 +1,20 @@
1 -In the last sprint, we have released a lot in terms of usability improvements both while working within the various phases of eMagiz as well as when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] containing a much needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.
1 +This release includes improvements to our certificate rotation mechanism that affect all customers using our event streaming offering. On top of that, new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** are released. Furthermore, additional accelerants for all integration developers are here. This includes improvements in how we assist users in Capture, Design, and Create at the system level. Subsequently, we introduced a fix to improve the stability of interacting with Create via the flow designer and when adding and removing integrations. Enjoy reading our latest updates on the platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.270 - Round Round.WebHome||target="blank"]].
4 4  
5 -====Minor Changes====
5 +==== Minor Changes ====
6 6  
7 -* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
8 -* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture, because this field was not visible enough in the rest of the portal. (#1608)
9 -* Capture / Design: For new systems, message types, machines, tenants and models hyphens are not allowed in the technical name anymore. The technical name can only consist of lower case letters and digits and must start with a letter. This also applies to systems, message types and tenants that have not yet been transferred from design to create. The portal will give an error message while transferring and the hyphen has to be removed manually.
10 -* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
11 -* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
12 -* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
7 +* General - Environment Templates: New **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** are released. Make sure to update before **August 15th, 2026**.
8 +* General - Event Streaming: Managing the rotation of customer intermediate certificates before they expire to keep the environment operational.
9 +* Design - System: On API-related systems, we stop activating the “OpenAPI” checkbox by default, as it was not used often enough to warrant the default behavior. (#1794)
10 +* Design - System: When activating the “OpenAPI” option and neglecting to supply any operation, you are confronted with a message specifying what you forgot when pressing Save. (#1794)
11 +* Design - System: Fixed an inconsistency in Event Streaming systems regarding the selected default message format. As a result, we will no longer alter the default message format when saving the corresponding system in Capture. (#1794)
13 13  
14 -====Bug fixes====
13 +==== Bug fixes ====
15 15  
16 -* Capture - Add System: When a user tries to creates a system or edits a system, loading bar is displayed before showing the pop-up. (#1228)
17 -* Capture - Edit System: When editing a system, the validation now takes into account that the name cannot be an empty string. (#1562)
18 -* Design - Message Definition: small improvements are introduced:
19 -** the widget can prevent user multiple message attributes on a message entity for the same attribute in datamodel.
20 -** when adding a new message entity to a current message entity, it doesn’t throw exception when user double click to many times in Save button
21 -* Design - Catalog: When exporting swagger json, in case an operation has example in request, the example will be shown correctly in swagger. (#1597)
22 -* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513)
23 -* Create - Add Integrations: Users are able to untransfer a flow even when there is a property attached to the flow. (#1590)
24 -* Create - Add Integrations: Flow, flow versions and the corresponding integration in the Deploy phase is cleaned when an integration is utransferred from the Create phase.
25 -* Create - Components: The browser page now displays the correct page title (#1509)
26 -* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
27 -* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560)
28 -* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already a property description in place. (#1526)
29 -* Deploy - Environment Template: Fixed a bug where upgrading a fully on-premise environment would incorrectly exclude some machines.
30 -* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore now moves the user to the queue browser of the correct environment. (#1408)
31 -* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents that flows using code mappings may encounter errors when stopping their runtime and messages were still processed. (#1550)
15 +* Create - Add Integrations: A more informative message is shown to the user if and when an automated flow configuration has failed. Additionally, the SOAP integrations can be recreated and edited. (#1377)
16 +* Create - Add Integrations: Fixed a specific case where changing a system to be a Mendix connector in the design phase did not correctly influence the deploy phase.
17 +* Create - Overview: We allow users to open (and reset) connector infra flows for on-premises API systems via the context menu. This makes the navigation to these connector infra flows consistent across patterns. (#1297)
18 +* Create - Flow Designer: A JMS outbound channel adapter can be saved without getting an alert when using a destination expression.
19 +* Create - Flow testing: XML test messages created based on a message definition will now contain randomized data.
20 +* Deploy - Releases (Swagger UI): Ensure that when you click the “Swagger UI” button in Deploy Releases, you are always redirected to the corresponding Swagger UI page, not the home page of our platform. (#1797)