Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 335.1
edited by Carlijn Kokkeler
on 2024/01/15 14:14
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
Content
... ... @@ -8,31 +8,17 @@
8 8  == **Feedback Items** ==
9 9  
10 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"]]
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"]].
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
14 14  
15 -//__External recipients emailaddress__//
16 -The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
17 -
18 -//__Broker queue metrics dashboards__//
19 -It is now possible to select the MQTT broker in the queue metrics dashboards.
20 -
21 -//__Runtime image version__//
22 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
23 -
24 -
25 25  == **Bug Fixes** ==
26 26  
27 -//__Message throughput__//
28 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
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.
29 29  
30 -//__Cloud template upgrade incorrect rollback__//
31 -An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
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.
32 32  
33 -//__Next generation block__//
34 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
35 -
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  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: