Skip to Content

Changes for page 270 - Round Round

Last modified by Erik Bakker on 2026/06/15 10:37
From version 328.1
edited by Erik Bakker
on 2026/04/20 21:48
Change comment: There is no comment for this version
To version 83.1
edited by Erik Bakker
on 2023/05/22 15:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -266 - Feel Free
1 +198 - Great Migration
Content
... ... @@ -1,31 +1,24 @@
1 -This release has a significant impact on users. Both in delivering functional value to our end users and in moving away from a legacy construct within our platform, and taking the UI one step into the future. On top of that, we have squashed some bugs. Sadly, however, we also have to announce that the announced **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** in [[release 264>>doc:Main.Release Information.Release Blogs.264 - Strict Seperation.WebHome||target="blank"]] has been pulled due to not meeting quality standards. Having said that, enjoy reading our latest updates on the platform.
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.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.266 - Feel Free.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]].
4 4  
5 -==== Minor changes ====
5 +=====Minor changes=====
6 6  
7 -* General - Event Streaming: To authenticate at DSH, our event streaming broker, we use certificates. These certificates have an expiration date, so they must be rotated. We have introduced a new way of rotating these certificates for you.
8 -** Proxy certificates must always be valid in DSH to prevent clients from encountering issues. A scheduled event runs daily during working hours to verify this.
9 -** If certificate rotation fails in the test environment, it will **not** continue to the acceptance or production environments.
10 -* Create - System: We now show the parent entity when selecting an entity or attribute in the right panel. This allows a user to identify better where in the message's structure they currently are. (#1520)
11 -* Deploy - Release: Creating a new release automatically puts you in “edit mode” for that release. (#672)
12 -* Create - Add Integrations: Improved how we autogenerate flows for the user.
13 -* General - Platform: Improved our general deletion behavior when deleting a model.
7 +* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
8 +* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
9 +* 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.
10 +* 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.
11 +* 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.
12 +* Deploy - Architecture: You can apply your changes to environment without having an active release.
13 +* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
14 +(control tower, so Gen3 only)
15 +* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
14 14  
15 -==== Bug fixes ====
17 +====Bug fixes====
16 16  
17 -* Deploy - Upgrade: Fixes a bug where the portainer agent could not be updated, as part of the environment template procedures, for Windows systems where portainer is installed on another drive than C:\. [CSP-1922]
18 -* Manage - Monitoring - HTTP Statistics (Other metrics): The mean and max for the response time are split into two graphs. (#1200)
19 -* Deploy - History: Entries stating 'null' will no longer be shown. (#1479)
20 -* Manage - Monitoring - Log Entries: The search/reset buttons are disabled while the reset/search is still being processed. (#1538)
21 -* Design - Edit an API integration - New/Edit resource: Added reserved keywords for the path of a resource, which can no longer be used. (#1585)
22 -* Create - Transformation - Custom XSLT snippet: Trying to save a newly edited XSLT snippet is only possible in “Edit mode”. (#1670)
23 -* Capture - Integration: Users are prevented from clicking the "Save integration" button too fast after creating a new message type to prevent a timing issue resulting in an error. The save button at the integration level is inactive until a message type is set for that integration. (#531)
24 -* Design - Catalog: The default request body is generated automatically for the POST operation when added as an integration in the Design phase.
25 -* Deploy - Architecture: Fixed an issue in the execution of the environment upgrade for models that have API MAM.
19 +* 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.
20 +* 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.
26 26  
27 -==== Remarks ====
22 +====Remarks====
28 28  
29 -* General - Infrastructure: An update has been applied to the internal communication with the eMagiz-managed authorization server.
30 -* General - Infrastructure: An update has been applied across the platform regarding the UI. As a result, all reference selectors have been replaced with combo boxes, aligning with current best practices and enabling users to interact with the platform more effectively.
31 -** Slightly modified the creation of new message types by implementing a new type of input widget that combines drop-down selection functionality with actions.
24 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.