Wiki source code of 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07

Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5
6 **Hi there, eMagiz developers!** This release contains single and double lane cloud template updates, both non-service affecting. Moreover, work has been done to better support a failover setup. Lastly, some bug fixes were done regarding the message merging tool and catalog topic defintions.
7
8 == **Cloud Template R20 - Double Lane** ==
9
10 This release introduces a new non-service affecting cloud template for all our customers running in a double-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R20 - Double lane.WebHome||target="blank"]].
11
12 == **Cloud Template R27 - Single Lane** ==
13
14 This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R27 - Single lane.WebHome||target="blank"]].
15
16 == **Feedback Items** ==
17
18 //__Failover setup__//
19 New components have been created to support a failover setup. Moreover, two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
20
21 == **Bug Fixes** ==
22
23 //__Message merging tool__//
24 We have improved our merging functionality within our Store offering to avoid unexpected results after merging. These unexpected results would lead to a broken Design phase on the data model level. If you have encountered this issue, you can manually clean your CDM message by removing the entities from the tree view and the canvas and correcting the CDM itself accordingly.
25
26 //__Catalog topic definitions__//
27 Before, an error would occur in the Catalog page when generating an example JSON message of a topic definition that has nested elements. This issue is now fixed and generating a sample JSON message for such topic definition is possible.
28
29 == **Fancy Forum Answers** ==
30
31 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:
32
33 * [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
34 * [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
35 * [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
36
37 == **Key Takeaways** ==
38
39 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:
40
41 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
42 * If you have feedback or ideas for us, talk to the Platypus
43 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
44 * Clear your browser cache (Ctrl + Shift + Del)
45 * Check out the release notes [[here>>doc:Main.Release Information.Portal.212 - Failover Fiesta.WebHome||target="blank"]]
46 * Start thinking about how the license tracker can aid your development
47 * Start thinking about major, minor, and patch
48 * Keep making great integrations
49
50 Let's stay in touch and till next time!
51
52 {{info}}
53 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
54
55 {{/info}}
56 )))
57
58 (((
59 {{toc/}}
60 )))
61 {{/container}}
62 {{/container}}