Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 165.1
edited by Carlijn Kokkeler
on 2023/12/04 15:30
Change comment: There is no comment for this version
To version 217.1
edited by Erik Bakker
on 2025/01/13 09:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -210 - Deployment Delights
1 +236 - Another Agent
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,28 +1,21 @@
1 -In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.210 - Deployment Delights||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.236 - Another Agent||target="blank"]].
4 4  
5 -=====New features=====
5 +====Major Changes====
6 6  
7 -* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties.
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 -* All - The next generation architecture is the default now. New models will use this generation as default.
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.
10 10  
11 -=====Minor changes=====
9 +====Minor Changes====
12 12  
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.
14 -* 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.
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.
16 16  
17 17  ====Bug fixes====
18 18  
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.
22 22  
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.
23 23  
24 -
25 -
26 -
27 -
28 -