Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 499.1
edited by Carlijn Kokkeler
on 2024/05/06 13:04
Change comment: There is no comment for this version
To version 345.1
edited by Carlijn Kokkeler
on 2024/01/16 16:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -220 - Patch Parade
1 +212 - Failover Fiesta
Content
... ... @@ -3,53 +3,38 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
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 -//__Integration pattern information__//
11 -Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
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-220-integration-pattern.png]]
12 +== **Cloud Template R27 - Single Lane** ==
14 14  
15 -//__Message queue history__//
16 -All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
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 -[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
16 +== **Feedback Items** ==
19 19  
20 -//__Search boxes__//
21 -Search boxes in the properties overview are now shown by default.
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"]].
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
24 -
25 -//__Set as mapped__//
26 -It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
27 -
28 -[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
29 -
30 -//__SSL settings__//
31 -Changes can now be deployed on SSL level without creating a new version of a flow in Create.
32 -
33 33  == **Bug Fixes** ==
34 -//__Annotation styling__//
35 -It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
36 36  
37 -[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
23 +//__Message merging tool__//
24 +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.
38 38  
39 -//__Filter rejection warnings__//
40 -A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
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.
41 41  
42 -[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
43 -
44 44  == **Fancy Forum Answers** ==
45 45  
46 46  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:
47 47  
48 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
49 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
50 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||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"]]
51 51  
52 -== **Key Takeaways** ==
37 +== **Key takeaways** ==
53 53  
54 54  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:
55 55  
... ... @@ -57,7 +57,7 @@
57 57  * If you have feedback or ideas for us, talk to the Platypus
58 58  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
59 59  * Clear your browser cache (Ctrl + Shift + Del)
60 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
45 +* Check out the release notes [here]
61 61  * Start thinking about how the license tracker can aid your development
62 62  * Start thinking about major, minor, and patch
63 63  * Keep making great integrations