Changes for page 214 - System Symphony
Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 387.1
edited by Carlijn Kokkeler
on 2024/02/13 09:51
on 2024/02/13 09:51
Change comment:
There is no comment for this version
To version 385.1
edited by Carlijn Kokkeler
on 2024/02/12 16:54
on 2024/02/12 16:54
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -13,19 +13,16 @@ 13 13 [[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]] 14 14 15 15 //__Adding multiple attributes__// 16 -It is now possible to add multiple existing attributes to an entity at once. This saves time when having to add multiple attributes to an entity. 16 +It is now possible to add multiple existing attributes to an entity at once. This saves time when having to add multiple attributes to an entity. 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. 17 17 18 18 [[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]] 19 19 20 20 //__Monitoring graphs__// 21 -The monitoring graphs can now show data up to 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.21 +The monitoring graphs can now show data up to the last thirty days. 22 22 23 23 == **Bug Fixes** == 24 24 //__Image versions__// 25 -To keep the overview of releases compact we now have improved the (automatic) deletion behavior in the following way: 26 -* The deletion of releases with deployed container versions will not be blocked anymore. 27 -* Automated release clean up behaviour will also not exclude these releases from deletion. 28 -* Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases. 25 +The deletion of releases with deployed container versions will not be blocked anymore. Automated release clean up behaviour will also not exclude these releases from deletion. Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases. 29 29 30 30 //__Failover group helptext__// 31 31 The helptext of the Group attribute has been improved. ... ... @@ -33,12 +33,12 @@ 33 33 [[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 34 34 35 35 //__Failover group refresh__// 36 -A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in theGroup tab of "Start/Stop Flows" screen.33 +A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in Group tab of "Start/Stop Flows" screen. 37 37 38 38 [[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 39 39 40 40 //__Resource paths__// 41 -After migrating a gateway away fomthelegacy runtime architecture, the path references in the event processors would be broken. This has been fixed.38 +After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed. 42 42 43 43 == **Fancy Forum Answers** == 44 44