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	+210 - Deployment Delights

Content

...	...	@@ -3,48 +3,62 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes!
	6	+**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7	7
	8	+== **Alerts** ==
	9	+
	10	+//__Topic approaching max size alert__//
	11	+The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
	12	+
	13	+//__Missing metrics alert__//
	14	+We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
	15	+
8	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.
11	11
12		-[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
	18	+//__Improved release build process__//
	19	+When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
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.
	21	+//__Container version overview__//
	22	+Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
	24	+[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
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.
	26	+//__Improved deployment process__//
	27	+The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
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.
	29	+//__Rebuilding of images__//
	30	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
25	25
26		-[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
	32	+== **Bug Fixes** ==
27	27
28		-//__Invalid memory configurations__//
29		-We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
	34	+//__Runtime metrics processing__//
	35	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
30	30
31		-//__Property value synchronization__//
32		-Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
	37	+//__Deployment plan__//
	38	+We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
33	33
34		-//__JMS number__//
35		-The number on the JMS container correctly displays the amount of queues present in Design.
	40	+//__View all store items__//
	41	+An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
36	36
37		-[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
	43	+//__Out of memory behavior__//
	44	+We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
38	38
	46	+//__Max fetch size__//
	47	+In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
	48	+
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"]]
	53	+* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
	54	+* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
	55	+* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
	56	+* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
	57	+* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
45	45
46		-== **Key Takeaways** ==
47	47
	60	+== **Key takeaways** ==
	61	+
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
50	50	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
...	...	@@ -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"]]
	68	+* 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
	71	+* 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
	79	+~*~* Indicates a next-generation-architecture only feature.
64	64	{{/info}}
65	65	)))
66	66