Changes for page 210 - Deployment Delights

Summary

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

Details

Page properties

Content

...	...	@@ -9,13 +9,13 @@
9	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	10	{{/warning}}
11	11
12		-== **Quicker Deployment Plan Execution** ==
	12	+== **Quicker Deployment Plan** ==
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!
	14	+We sped up the process of preparing runtime images in 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 which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deployment plan will be finished much quicker now!
15	15
16	16	== **Next Generation Architecture Default** ==
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.
	18	+With this release, the next generation architecture will become the default. New models will use this generation as default.
19	19
20	20	[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
21	21
...	...	@@ -36,11 +36,12 @@
36	36	* Not required by a flow that is in the Create phase release.
37	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	41	//__Queue explorer milliseconds__//
42	42	The queue browser now displays milliseconds in the timestamps.
43	43
	42	+//__Cancel and next buttons order__//
	43	+The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
	44	+
44	44	//__Unused images__//
45	45	When a release is removed, the related unused images in the on-premises machines will be removed as well.
46	46
...	...	@@ -53,10 +53,10 @@
53	53	== **Bug Fixes** ==
54	54
55	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.
	57	+In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
57	57
58	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.
	60	+We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
60	60
61	61	//__Error channel inbounds__//
62	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.