Skip to Content

Changes for page 215 - Tiny Tales

Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 194.1
edited by Carlijn Kokkeler
on 2024/02/13 09:55
Change comment: There is no comment for this version
To version 159.1
edited by Carlijn Kokkeler
on 2023/11/21 12:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -214 - System Symphony
1 +209 - Max Verstappen
Content
... ... @@ -1,21 +1,33 @@
1 -In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.214 - System Symphony||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]].
4 4  
5 5  =====New features=====
6 6  
7 -* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once.
8 -* Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
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.
9 9  
10 10  =====Minor changes=====
11 11  
12 -* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore.
13 -* Manage - Monitoring: New functionality to ensure that the monitoring graphs in Manage can show data from the last thirty days. To utilize this, a new runtime image, [[V.2.1.1>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.1/||target="blank"]], is needed.
13 +* 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.
14 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
15 +* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
16 +* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
14 14  
15 15  ====Bug fixes====
16 16  
17 -* Create - Flow Designer: The help text of the Group attribute has been improved.
18 -* Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test.
19 -* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen.
20 +* Create - Flow Designer: An issue has been fixed in the flow designer where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
21 +* Create - Flow Designer: We added a migration step to set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
22 +* Deploy - Deployment plan: We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped.
23 +* Manage - Monitoring - We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that has just migrated to the next generation architecture.
20 20  
25 +====Infra and image changes====
21 21  
27 +* Infra: New logging feature enabling us to make better choices in encryption standards.
28 +
29 +
30 +
31 +
32 +
33 +