Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 337.1
edited by Carlijn Kokkeler
on 2024/01/15 14:25
on 2024/01/15 14:25
Change comment:
There is no comment for this version
To version 339.1
edited by Carlijn Kokkeler
on 2024/01/15 14:39
on 2024/01/15 14:39
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -5,6 +5,14 @@ 5 5 6 6 **Hi there, eMagiz developers!** This release... 7 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 cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]]. 15 + 8 8 == **Feedback Items** == 9 9 10 10 //__Failover setup__// ... ... @@ -13,7 +13,11 @@ 13 13 14 14 == **Bug Fixes** == 15 15 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. 16 16 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. 17 17 18 18 == **Fancy Forum Answers** == 19 19