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,47 +3,58 @@
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 triggers 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!** We have...
7	7
	8	+== **Alerts** ==
	9	+
	10	+//__Topic approaching max size alert__//
	11	+The alert ‘topic approaching maximum size’ alert 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		-//__Design changes__//
10		-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.
11	11
12		-[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
	18	+//__Container version overview__//
	19	+In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
13	13
14		-== **Bug Fixes** ==
15		-//__Cron triggers__//
16		-Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
	21	+[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
17	17
18		-[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
	23	+//__Unchanged containers__//
	24	+When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
19	19
20		-//__Trigger activation__//
21		-Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed.
	26	+//__Rebuilding of images__//
	27	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
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.
25	25
26		-[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
	30	+== **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.
	32	+//__Runtime metrics processing__//
	33	+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.
	35	+//__Deployment plan__//
	36	+We solved a bug where a deployment step in 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.
	38	+//__Store message merging__//
	39	+The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
36	36
37		-[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
	41	+//__View all store items__//
	42	+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.
38	38
	44	+//__Out of memory behavior__//
	45	+We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
	46	+
	47	+//__Max fetch size__//
	48	+We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
	49	+
	50	+
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"]]
	55	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
45	45
46		-== **Key Takeaways** ==
	57	+== **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.222 - Flee Frustration.WebHome||target="blank"]]
	65	+* 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
	68	+* 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
	76	+~*~* Indicates a next-generation-architecture only feature.
64	64	{{/info}}
65	65	)))
66	66