Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-222 - Flee Frustration
	1	+209 - Max Verstappen

Content

...	...	@@ -3,47 +3,62 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!**
	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.
7	7
8		-== **Feedback Items** ==
9		-//__Cron triggers__//
10		-Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
	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}}
11	11
12		-[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
	12	+== **Quicker Deployment Plan Execution** ==
13	13
14		-//__Design changes__//
15		-If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
	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!
16	16
17		-[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
	16	+== **Next Generation Architecture Default** ==
18	18
19		-== **Bug Fixes** ==
20		-//__Trigger activation__//
21		-Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
	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.
22	22
23		-//__Multiple users deploying__//
24		-Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
	20	+[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
25	25
26		-[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
	22	+== **Cloud Template R11 Docker - Single Lane** ==
27	27
28		-//__Invalid memory configurations__//
29		-We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
	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"]].
30	30
31		-//__Invalid memory configurations__//
32		-Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
	26	+== **Cloud Template R13 Docker - Double Lane** ==
33	33
34		-//__JMS number__//
35		-The number on the JMS container correctly displays the amount of queues present in Design.
	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"]].
36	36
37		-[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
	30	+== **Feedback Items** ==
38	38
	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:
	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	+
	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	+//__Static alerts queue consumers__//
	45	+Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
	46	+
	47	+== **Bug Fixes** ==
	48	+
	49	+//__Flow Designer connection line__//
	50	+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.
	51	+
	52	+//__Portal for migrated models__//
	53	+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.
	54	+
39	39	== **Fancy Forum Answers** ==
40	40
41	41	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:
42	42
43		-* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
44		-* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
	59	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
45	45
46		-== **Key Takeaways** ==
	61	+== **Key takeaways** ==
47	47
48	48	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:
49	49
...	...	@@ -51,9 +51,10 @@
51	51	* If you have feedback or ideas for us, talk to the Platypus
52	52	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
53	53	* Clear your browser cache (Ctrl + Shift + Del)
54		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
	69	+* Check out the release notes [here]
55	55	* Start thinking about how the license tracker can aid your development
56	56	* Start thinking about major, minor, and patch
	72	+* Upgrade to the latest build number
57	57	* Keep making great integrations
58	58
59	59	Let's stay in touch and till next time!
...	...	@@ -61,6 +61,7 @@
61	61	{{info}}
62	62	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63	63
	80	+~*~* Indicates a next-generation-architecture only feature.
64	64	{{/info}}
65	65	)))
66	66