Skip to Content

Changes for page 213 - Joyful Journeys

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +213 - Joyful Journeys
Content
... ... @@ -3,28 +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 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.
6 +**Hi there, eMagiz developers!** This release ....
7 7  
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 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"]].
9 +== **Feedback Items** ==
11 11  
12 -== **Cloud Template R27 - Single Lane** ==
11 +//__Property releases__//
12 +When a new property release is created, this property release can now be viewed and deleted.
13 13  
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"]].
14 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
15 15  
16 -== **Feedback Items** ==
16 +//__Runtime deletion__//
17 +When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
17 17  
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"]].
19 +//__Update flows__//
20 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
20 20  
22 +//__Input fields__//
23 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
24 +
21 21  == **Bug Fixes** ==
22 22  
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.
25 25  
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.
28 28  
29 29  == **Fancy Forum Answers** ==
30 30  
... ... @@ -34,7 +34,7 @@
34 34  * [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
35 35  * [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
36 36  
37 -== **Key takeaways** ==
37 +== **Key Takeaways** ==
38 38  
39 39  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
40 40