Changes for page 214 - System Symphony

Last modified by Carlijn Kokkeler on 2024/04/18 13:06

From version 334.1
edited by Carlijn Kokkeler
on 2024/01/15 14:14
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,41 +3,36 @@
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 -== **Feedback Items** ==
8 +== **Cloud Template R20 - Double Lane** ==
9 9  
10 -//__Failover setup__//
11 -New components have been created to support a failover setup. More information can be found [[here>>doc:Main.Release Information.Runtime Images.V2.1.0||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"]].
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
12 +== **Cloud Template R27 - Single Lane** ==
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.
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"]].
17 17  
18 -//__Broker queue metrics dashboards__//
19 -It is now possible to select the MQTT broker in the queue metrics dashboards.
16 +== **Feedback Items** ==
20 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.
18 +//__Failover setup__//
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"]].
23 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.
23 +//__Message merging tool__//
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.
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.
26 +//__Catalog topic definitions__//
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.
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:
39 39  
40 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
33 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
34 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
35 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
41 41  
42 42  == **Key takeaways** ==
43 43