Skip to Content

Wiki source code of 212 - Failover Fiesta

Version 341.1 by Carlijn Kokkeler on 2024/01/15 14:44
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...
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 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.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 double-lane setup on the next generation architecture. 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. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
20
21
22 == **Bug Fixes** ==
23
24 //__Message merging tool__//
25 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.
26
27 //__Catalog topic definitions__//
28 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.
29
30 == **Fancy Forum Answers** ==
31
32 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:
33
34 * [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
35 * [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
36 * [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
37
38 == **Key takeaways** ==
39
40 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:
41
42 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
43 * If you have feedback or ideas for us, talk to the Platypus
44 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
45 * Clear your browser cache (Ctrl + Shift + Del)
46 * Check out the release notes [here]
47 * Start thinking about how the license tracker can aid your development
48 * Start thinking about major, minor, and patch
49 * Keep making great integrations
50
51 Let's stay in touch and till next time!
52
53 {{info}}
54 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
55
56 {{/info}}
57 )))
58
59 (((
60 {{toc/}}
61 )))
62 {{/container}}
63 {{/container}}