Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40

From version 594.1
edited by CarlijnKokkeler
on 2024/07/16 12:01
Change comment: There is no comment for this version
To version 392.1
edited by CarlijnKokkeler
on 2024/02/16 12:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - TBD
1 +214 - System Symphony
Content
... ... @@ -3,40 +3,52 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
6 +**Hi there, eMagiz developers!** This release contains multiple bug fixes, as well as some other improvements. The monitoring graphs have been improved, such that they can now show data up to the last thirty days. Moreover, we can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done.
7 7  
8 -
9 9  == **Feedback Items** ==
10 -//__Alerting notification settings__//
11 -The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
10 +//__On premise Windows machines__//
11 +We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
14 14  
15 -//__Process containers__//
16 -If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
13 +[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]
14 + [[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-windows.png]]
17 17  
18 -//__Design settings__//
19 -When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
16 +//__Adding multiple attributes__//
17 +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.
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
19 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]
22 22  
23 -//__Untested images__//
24 - A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before.
25 -
26 -PICTURE
21 +//__Monitoring graphs__//
22 +The monitoring graphs can now show data up to the last thirty days.
27 27  
28 -
29 29  == **Bug Fixes** ==
25 +//__Image versions__//
26 +To keep the overview of releases compact we now have improved the (automatic) deletion behavior in the following way:
27 +* The deletion of releases with deployed container versions will not be blocked anymore.
28 +* Automated release clean up behaviour will also not exclude these releases from deletion.
29 +* 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.
30 30  
31 +//__Failover group helptext__//
32 +The helptext of the Group attribute has been improved.
31 31  
34 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
32 32  
36 +//__Failover group refresh__//
37 +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 the Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed.
33 33  
39 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
34 34  
41 +//__Resource paths__//
42 +After migrating a gateway away fom the legacy runtime architecture, the path references in the event processors would be broken. This has been fixed.
43 +
35 35  == **Fancy Forum Answers** ==
36 36  
37 37  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
38 38  
39 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
48 +* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]]
49 +* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]]
50 +* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]]
51 +* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]]
40 40  
41 41  == **Key Takeaways** ==
42 42  
... ... @@ -46,7 +46,7 @@
46 46  * If you have feedback or ideas for us, talk to the Platypus
47 47  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
48 48  * Clear your browser cache (Ctrl + Shift + Del)
49 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
61 +* Check out the release notes [here]
50 50  * Start thinking about how the license tracker can aid your development
51 51  * Start thinking about major, minor, and patch
52 52  * Keep making great integrations