Skip to Content

Changes for page 236 - Another Agent

Last modified by Erik Bakker on 2025/01/13 09:32
From version 217.1
edited by Erik Bakker
on 2025/01/13 09:14
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 -236 - Another Agent
1 +198 - Great Migration
Content
... ... @@ -1,21 +1,24 @@
1 -In the last sprint cycle, we focused on delivering new [[cloud templates>>Main.Release Information.Cloud Templates||target="blank"]] for docker single and docker double lane. Moreover, we have addressed several key feedback points within our 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>>Main.Release Information.Release Blogs.236 - Another Agent||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 -====Major Changes====
5 +=====Minor changes=====
6 6  
7 -* * Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
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.
8 8  
9 -====Minor Changes====
10 -
11 -* Create - Flow Designer: Improved help texts for the FTP & SFTP local filter options.
12 -* Deploy - Overview: Spring6 pop-up has been removed.
13 -* Manage - Alerting: The recipients tab for the new Alerting triggers has seen a small update in regards of UX: You will get an explanation when you are trying to enable notifications when no recipients are selected yet.
14 -
15 15  ====Bug fixes====
16 16  
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.
17 17  
18 -* Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456)
19 -* Create - Transfer Settings: You can now increase and decrease the number of runtimes for existing Systems. And transfer them from Design Architecture to Deploy Architecture. This can be done in “Create – Settings - Transfer Settings from Design”. (#1543)
20 -* Manage - Alerting: Inactive users in your model are removed from the list of selectable recipients.
22 +====Remarks====
21 21  
24 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.