Skip to Content

Changes for page 270 - Round Round

Last modified by Erik Bakker on 2026/06/15 10:37
From version 82.1
edited by Erik Bakker
on 2023/05/22 15:19
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 -198 - Great Migration
1 +270 - Round Round
Content
... ... @@ -1,27 +1,20 @@
1 -Another couple of weeks have passed, so it is time for a new release. We have focused in this period on improving the migration process towards the next-generation architecture as well as how the user experience and interaction with the next-generation architecture works.
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.198 - Great Migration.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 -=====New features=====
5 +==== Minor Changes ====
6 6  
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)
7 7  
8 -=====Minor changes=====
13 +==== Bug fixes ====
9 9  
10 -* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
11 -* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
12 -* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
13 -* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
14 -* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
15 -* Deploy - Architecture: You can apply your changes to environment without having an active release.
16 -* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
17 -(control tower, so Gen3 only)
18 -* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
19 -
20 -====Bug fixes====
21 -
22 -* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models.
23 -* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
24 -
25 -====Remarks====
26 -
27 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
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)