Changes for page 213 - Joyful Journeys

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+212 - Failover Fiesta

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,86 +1,50 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
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.
	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	6
7		-== **3rd generation runtime bolstering** ==
	8	+== **Cloud Template R20 - Double Lane** ==
8	8
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.
	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"]].
10	10
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.
	12	+== **Cloud Template R27 - Single Lane** ==
13	13
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.
	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	16
17		-//__Autogenerated exits can be deployed at once__//
18		-This release has fixed a bug that prevented you from deploying an exit flow correctly.
	16	+== **Feedback Items** ==
19	19
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.
	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		-//__Improved the performance when activating a release__//
24		-With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
	21	+== **Bug Fixes** ==
25	25
26		-//__Failing runtimes won't be restarted indefinitely anymore__//
27		-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.
	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.
28	28
29		-== **Exportable Release Audit** ~* ==
	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.
30	30
31		-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.
32		-
33		-[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
34		-
35		-{{warning}}Note that the following restrictions apply when exporting an audit document:
36		- * Works **only** for releases that are promoted and made active on Production
37		- * You will **only** see changes made during the **current** calendar year{{/warning}}
38		-
39		-== **Feedback items ** ==
40		-
41		-We have also solved other feedback items besides the flow designer's critical updates.
42		-
43		-//__Improved naming convention on Store related pages__//
44		-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.
45		-
46		-//__Press "Enter" to search on multiple pages__//
47		-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.
48		-
49		-* Deploy → Deployment Plan
50		-* Deploy → Properties → History
51		-* Deploy → User Management → Roles
52		-* Manage → Error Messages → Error Messages
53		-* Manage → Error Messages → Flows with Error Messages
54		-* Manage → Error Messages → Exceptions of Error Messages
55		-* Manage → Log Entries
56		-* Manage → Alerts
57		-* Manage → Triggers
58		-* Manage → Tags – Cant find (only Gen2)
59		-* Manage → Notifications
60		-* Manage → Notification Settings
61		-* Manage → Data Usage → History
62		-* Manage → Code mappings → All tabs
63		-
64	64	== **Fancy Forum Answers** ==
65	65
66	66	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:
67	67
68		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
69		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
70		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||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"]]
71	71
72	72	== **Key takeaways** ==
73	73
74		-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:
	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:
75	75
76	76	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77	77	* If you have feedback or ideas for us, talk to the Platypus
78		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	43	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
79	79	* Clear your browser cache (Ctrl + Shift + Del)
80	80	* Check out the release notes [here]
81	81	* Start thinking about how the license tracker can aid your development
82	82	* Start thinking about major, minor, and patch
83		-* Upgrade to the latest build number
84	84	* Keep making great integrations
85	85
86	86	Let's stay in touch and till next time!
...	...	@@ -88,6 +88,11 @@
88	88	{{info}}
89	89	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
90	90
91		-~*~* Indicates a GEN3-only feature.
92		-{{/info}})))((({{toc/}}))){{/container}}
	55	+{{/info}}
	56	+)))
	57	+
	58	+(((
	59	+{{toc/}}
	60	+)))
93	93	{{/container}}
	62	+{{/container}}