Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Max Verstappen
	1	+212 - Failover Fiesta

Content

...	...	@@ -3,69 +3,35 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
	6	+**Hi there, eMagiz developers!** This release...
7	7
8		-{{warning}}
9		-Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
10		-{{/warning}}
	8	+== **Cloud Template R20 - Double Lane** ==
11	11
12		-== **Quicker Deployment Plan Execution** ==
	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"]].
13	13
14		-We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. So, the deployment plan will be finished much quicker now!
	12	+== **Cloud Template R27 - Single Lane** ==
15	15
16		-== **Next Generation Architecture Default** ==
	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"]].
17	17
18		-With this release, the next generation architecture will become the default. From now on, new models will then use this generation as the default architecture.
19		-
20		-[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
21		-
22		-== **Cloud Template R11 Docker - Single Lane** ==
23		-
24		-This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
25		-
26		-== **Cloud Template R13 Docker - Double Lane** ==
27		-
28		-This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
29		-
30	30	== **Feedback Items** ==
31	31
32		-//__Unused properties overview__//
33		-In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
	18	+//__Failover setup__//
	19	+New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
34	34
35		-* Not used by any runtime that is in the Create phase release.
36		-* Not required by a flow that is in the Create phase release.
37		-* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
38	38
39		-[[image:Main.Images.Release Blog.WebHome@release-blog-209-unused-properties-overview.png]]
40		-
41		-//__Queue explorer milliseconds__//
42		-The queue browser now displays milliseconds in the timestamps.
43		-
44		-//__Unused images__//
45		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
46		-
47		-//__Carwash logging__//
48		-A new logging feature enabling us to make better choices in encryption standards will be released.
49		-
50		-//__Static alerts queue consumers__//
51		-Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
52		-
53	53	== **Bug Fixes** ==
54	54
55		-//__Flow Designer connection line__//
56		-In the Flow Designer an issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
	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.
57	57
58		-//__Portal for migrated models__//
59		-We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
	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.
60	60
61		-//__Error channel inbounds__//
62		-We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
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		-* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	34	+* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
69	69
70	70	== **Key takeaways** ==
71	71
...	...	@@ -78,7 +78,6 @@
78	78	* Check out the release notes [here]
79	79	* Start thinking about how the license tracker can aid your development
80	80	* Start thinking about major, minor, and patch
81		-* Upgrade to the latest build number
82	82	* Keep making great integrations
83	83
84	84	Let's stay in touch and till next time!
...	...	@@ -86,7 +86,6 @@
86	86	{{info}}
87	87	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
88	88
89		-~*~* Indicates a next-generation-architecture only feature.
90	90	{{/info}}
91	91	)))
92	92