Skip to Content

Changes for page 224 - Summer Sonata

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +219 - Creation Carousel
Content
... ... @@ -3,38 +3,45 @@
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!**
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** ==
10 +//__Machine agents__//
11 +We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more here.
11 11  
12 -== **Cloud Template R27 - Single Lane** ==
13 +//__Custom webhook__//
14 +We removed a deprecated functionality that sends a custom webhook when upgrading the environment. Please find out more here.
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"]].
16 +//__eMagiz Mendix connector__//
17 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.4
15 15  
16 -== **Feedback Items** ==
19 +//__Improved OpenAPI import__//
20 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
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"]].
20 -
21 21  == **Bug Fixes** ==
23 +//__Error handling__//
24 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
22 22  
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.
26 +//__Volume mapping passwords__//
27 +Passwords for network volumes are hidden on the machine after deployment.
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.
29 +//__Create integration removal__//
30 +When removing an integration from Create, the Create phase is correctly updated as well.
28 28  
32 +//__Legacy statistics__//
33 +Legacy pages are now correctly hidden when running on the current runtime architecture.
34 +
29 29  == **Fancy Forum Answers** ==
30 30  
31 31  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:
32 32  
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"]]
39 +* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
40 +* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
41 +* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
42 +* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]
36 36  
37 -== **Key takeaways** ==
44 +== **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  
... ... @@ -42,7 +42,7 @@
42 42  * If you have feedback or ideas for us, talk to the Platypus
43 43  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
44 44  * Clear your browser cache (Ctrl + Shift + Del)
45 -* Check out the release notes [here]
52 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
46 46  * Start thinking about how the license tracker can aid your development
47 47  * Start thinking about major, minor, and patch
48 48  * Keep making great integrations