Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 341.1
edited by Carlijn Kokkeler
on 2024/01/15 14:44
Change comment: There is no comment for this version
To version 346.1
edited by Carlijn Kokkeler
on 2024/01/17 08:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,29 +3,28 @@
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 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 7  
8 8  == **Cloud Template R20 - Double Lane** ==
9 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"]].
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 11  
12 12  == **Cloud Template R27 - Single Lane** ==
13 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"]].
14 +This release introduces a new non-service affecting cloud template for all our customers running in a single-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 15  
16 16  == **Feedback Items** ==
17 17  
18 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"]].
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 20  
21 -
22 22  == **Bug Fixes** ==
23 23  
24 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.
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.
26 26  
27 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.
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.
29 29  
30 30  == **Fancy Forum Answers** ==
31 31