Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 158.1
edited by Carlijn Kokkeler
on 2023/11/21 12:42
Change comment: There is no comment for this version
To version 164.1
edited by Carlijn Kokkeler
on 2023/11/23 08:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,21 +8,18 @@
8 8  * Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 9  * All - The next generation architecture is the default now. New models will use this generation as default.
10 10  
11 -
12 -
13 13  =====Minor changes=====
14 14  
15 -* Deploy - Releases: We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
16 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
13 +* Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
17 17  * Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
15 +* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
18 18  
19 -
20 -
21 21  ====Bug fixes====
22 22  
23 -====Infra and image changes====
19 +* Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
20 +* Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.
21 +* Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
24 24  
25 -* Infra: New logging feature enabling us to make better choices in encryption standards.
26 26  
27 27  
28 28