Skip to Content

Changes for page 215 - Tiny Tales

Last modified by Carlijn Kokkeler on 2024/04/18 13:05
From version 335.1
edited by Carlijn Kokkeler
on 2024/01/15 14:14
Change comment: There is no comment for this version
To version 383.1
edited by Carlijn Kokkeler
on 2024/02/12 16:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +214 - System Symphony
Content
... ... @@ -3,43 +3,50 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release...
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 8  == **Feedback Items** ==
9 9  
10 -//__Failover setup__//
11 -New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]]
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.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
13 +[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]
14 14  
15 -//__External recipients emailaddress__//
16 -The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
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.
17 17  
18 -//__Broker queue metrics dashboards__//
19 -It is now possible to select the MQTT broker in the queue metrics dashboards.
18 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]
20 20  
21 -//__Runtime image version__//
22 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
20 +//__Monitoring graphs__//
21 +The monitoring graphs can now show data up to the last thirty days.
23 23  
24 -
25 25  == **Bug Fixes** ==
24 +//__Image versions__//
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.
26 26  
27 -//__Message throughput__//
28 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
27 +//__Failover group helptext__//
28 +The helptext of the Group attribute has been improved.
29 29  
30 -//__Cloud template upgrade incorrect rollback__//
31 -An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
30 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
32 32  
33 -//__Next generation block__//
34 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
32 +//__Failover group refresh__//
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.
35 35  
35 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
36 +
37 +//__Resource paths__//
38 +After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
39 +
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  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:
39 39  
40 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
44 +* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]]
45 +* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]]
46 +* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]]
47 +* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]]
41 41  
42 -== **Key takeaways** ==
49 +== **Key Takeaways** ==
43 43  
44 44  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
45 45