Changes for page 270 - Round Round

Last modified by Erik Bakker on 2026/06/15 10:37

From version 341.1
edited by Erik Bakker
on 2026/06/15 10:37
Change comment: There is no comment for this version
To version 88.1
edited by Erik Bakker
on 2023/06/06 08:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -270 - Round Round
1 +199 - Home Improvements
Content
... ... @@ -1,20 +1,20 @@
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.
1 +In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture, the store, security, and certificate management.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.270 - Round Round.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]].
4 4  
5 -==== Minor Changes ====
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 +* Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store.
8 +* 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.
9 +* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899)
10 +* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately three months before event streaming users' access certificates expire.
11 +* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan.
12 +* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960)
13 +* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.
14 +* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.
12 12  
13 -==== Bug fixes ====
16 +====Bug fixes====
14 14  
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)
18 +* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864)
19 +* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937)
20 +