Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 147.1
edited by Erik Bakker
on 2023/08/15 13:53
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 -203 - Fast Paced
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,46 +1,41 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
6 +**Hi there, eMagiz developers!** This release...
6 6  
7 -== **Release Properties - Early Feedback** ==
8 -The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
9 -
10 10  == **Feedback Items** ==
11 11  
12 -//__"All entries" are now cleaned up as part of the migration__//
13 -To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
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"]].
14 14  
15 -//__Trigger ID added to our alerting on the next-generation architecture__//
16 -We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
17 17  
18 -//__Improved performance Manage Dashboards__//
19 -We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture.
20 -
21 21  == **Bug Fixes** ==
22 22  
23 -//__Ensure no flow can be in a release twice__//
24 -We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
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.
25 25  
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.
21 +
26 26  == **Fancy Forum Answers** ==
27 27  
28 28  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:
29 29  
30 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
26 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
31 31  
32 32  == **Key takeaways** ==
33 33  
34 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
30 +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:
35 35  
36 36  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
37 37  * If you have feedback or ideas for us, talk to the Platypus
38 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
34 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
39 39  * Clear your browser cache (Ctrl + Shift + Del)
40 40  * Check out the release notes [here]
41 41  * Start thinking about how the license tracker can aid your development
42 42  * Start thinking about major, minor, and patch
43 -* Upgrade to the latest build number
44 44  * Keep making great integrations
45 45  
46 46  Let's stay in touch and till next time!
... ... @@ -48,6 +48,11 @@
48 48  {{info}}
49 49  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
50 50  
51 -~*~* Indicates a next-generation-architecture only feature.
52 -{{/info}})))((({{toc/}}))){{/container}}
46 +{{/info}}
47 +)))
48 +
49 +(((
50 +{{toc/}}
51 +)))
53 53  {{/container}}
53 +{{/container}}