Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 342.1
edited by Carlijn Kokkeler
on 2024/01/15 14:50
Change comment: There is no comment for this version
To version 55.1
edited by Erik Bakker
on 2022/11/24 11:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,51 +1,90 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release...
5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
7 7  
8 -== **Cloud Template R20 - Double Lane** ==
7 +== **3rd generation runtime bolstering** ==
9 9  
10 -This release introduces a new non-service affecting cloud template for all our customers running in a single-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 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
11 11  
12 -== **Cloud Template R27 - Single Lane** ==
11 +//__Migration of JMS backup configuration improved__//
12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
13 13  
14 -This release introduces a new non-service affecting cloud template for all our customers running in a double-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 +//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
15 15  
16 -== **Feedback Items** ==
17 +//__Autogenerated exits can be deployed at once__//
18 +This release has fixed a bug that prevented you from deploying an exit flow correctly.
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 +//__Code mapping functionality available on 3rd generation runtime__//
21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
20 20  
23 +//__Failing runtimes won't be restarted indefinitely anymore__//
24 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
21 21  
22 -== **Bug Fixes** ==
26 +== **Exportable Release Audit** ~* ==
23 23  
24 -//__Message merging tool__//
25 -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.
28 +On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
26 26  
27 -//__Catalog topic definitions__//
28 -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.
30 +[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
29 29  
32 +{{warning}}Note that the following restrictions apply when exporting an audit document:
33 + * Works **only** for releases that are promoted and made active on **Production**
34 + * You will **only** see changes made during the **current** calendar year
35 + * On the first of April all objects of the **last** calendar year will be **removed**.
36 + ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
37 +
38 +== **Feedback items ** ==
39 +
40 +We have also solved other feedback items besides the flow designer's critical updates.
41 +
42 +//__Improved naming convention on Store related pages__//
43 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
44 +
45 +//__Press "Enter" to search on multiple pages__//
46 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
47 +
48 +* Deploy → Deployment Plan
49 +* Deploy → Properties → History
50 +* Deploy → User Management → Roles
51 +* Manage → Error Messages → Error Messages
52 +* Manage → Error Messages → Flows with Error Messages
53 +* Manage → Error Messages → Exceptions of Error Messages
54 +* Manage → Log Entries
55 +* Manage → Alerts
56 +* Manage → Triggers
57 +* Manage → Tags – Cant find (only Gen2)
58 +* Manage → Notifications
59 +* Manage → Notification Settings
60 +* Manage → Data Usage → History
61 +* Manage → Code mappings → All tabs
62 +
63 +== **Bug fixes ** ==
64 +
65 +//__Loading problems of Deployment plan execution overview__//
66 +We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
67 +
30 30  == **Fancy Forum Answers** ==
31 31  
32 32  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:
33 33  
34 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
35 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
36 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
72 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
73 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
74 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
37 37  
38 38  == **Key takeaways** ==
39 39  
40 -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:
78 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
41 41  
42 42  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
43 43  * If you have feedback or ideas for us, talk to the Platypus
44 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
82 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
45 45  * Clear your browser cache (Ctrl + Shift + Del)
46 46  * Check out the release notes [here]
47 47  * Start thinking about how the license tracker can aid your development
48 48  * Start thinking about major, minor, and patch
87 +* Upgrade to the latest build number
49 49  * Keep making great integrations
50 50  
51 51  Let's stay in touch and till next time!
... ... @@ -53,11 +53,6 @@
53 53  {{info}}
54 54  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
55 55  
56 -{{/info}}
57 -)))
58 -
59 -(((
60 -{{toc/}}
61 -)))
95 +~*~* Indicates a GEN3-only feature.
96 +{{/info}})))((({{toc/}}))){{/container}}
62 62  {{/container}}
63 -{{/container}}