Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 374.1
edited by Carlijn Kokkeler
on 2024/02/12 15:09
Change comment: There is no comment for this version
To version 338.1
edited by Carlijn Kokkeler
on 2024/01/15 14:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -214 - System Symphony
1 +212 - Failover Fiesta
Content
... ... @@ -3,45 +3,29 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, ...
6 +**Hi there, eMagiz developers!** This release...
7 7  
8 8  == **Feedback Items** ==
9 9  
10 -//__Update flows__//
11 -Support for deploying to on premise Windows machines has been delivered.
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"]].
12 12  
13 -//__Image versions__//
14 -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.
15 15  
16 -//__Adding multiple attributes__//
17 -It is now possible to add multiple existing attributes to an entity at once.
18 -
19 -//__Monitoring graphs__//
20 -The monitoring graphs can now show data up to the last 30 days.
21 -
22 22  == **Bug Fixes** ==
23 -//__Failover group helptext__//
24 -The helptext of the Group attribute has been improved.
25 25  
26 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
16 +//__Message merging tool__//
17 +The message merging tool has been fixed to allow merging a store item message model into your own message models. In some rare cases your CDM message may be broken due to incorrect data. In those cases, the message mapping and message merge functionalities will be broken as well. If this broken data is detected when navigating to CDM-message-related pages, you will be able to clean your CDM message.
27 27  
28 -//__Failover group refresh__//
29 -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.
19 +//__Catalog topic definitions__//
20 +It is now possible to generate a JSON Example of a topic whose schema has nested elements. Before, an error would occur when trying to generate a JSON example in this case.
30 30  
31 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
32 -
33 -//__Resource paths__//
34 -After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
35 -
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 -* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
41 -* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
42 -* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
26 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
43 43  
44 -== **Key Takeaways** ==
28 +== **Key takeaways** ==
45 45  
46 46  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:
47 47