Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 276.1
edited by Carlijn Kokkeler
on 2023/12/04 14:43
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
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Deployment Delights
1 +212 - Failover Fiesta
Content
... ... @@ -3,44 +3,27 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have...
6 +**Hi there, eMagiz developers!** This release...
7 7  
8 -== **Release Maintenance** ==
9 -
10 -
11 -
12 -
13 -
14 14  == **Feedback Items** ==
15 15  
16 -//__Harbor port change__//
17 -The port for which you need to register has been changed ...?
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"]].
18 18  
19 -//__Container version overview__//
20 -In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
23 -
24 -//__Unchanged containers__//
25 -When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
26 -
27 -//__Rebuilding of images__//
28 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
29 -
30 -
31 31  == **Bug Fixes** ==
32 32  
33 -//__Runtime metrics processing__//
34 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
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.
35 35  
36 -//__Deployment plan__//
37 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
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.
38 38  
39 39  == **Fancy Forum Answers** ==
40 40  
41 41  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:
42 42  
43 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
26 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
44 44  
45 45  == **Key takeaways** ==
46 46  
... ... @@ -53,7 +53,6 @@
53 53  * Check out the release notes [here]
54 54  * Start thinking about how the license tracker can aid your development
55 55  * Start thinking about major, minor, and patch
56 -* Upgrade to the latest build number
57 57  * Keep making great integrations
58 58  
59 59  Let's stay in touch and till next time!
... ... @@ -61,7 +61,6 @@
61 61  {{info}}
62 62  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63 63  
64 -~*~* Indicates a next-generation-architecture only feature.
65 65  {{/info}}
66 66  )))
67 67