Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-210 - Deployment Delights
	1	+214 - System Symphony

Content

...	...	@@ -3,56 +3,45 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also several for the Store. Lastly, we made some changes to the alerts that you may be receiving.
	6	+**Hi there, eMagiz developers!** This release contains multiple bug fixes, as well as some other improvements. The monitoring graphs have been improved, such that they can now show data up to the last 30 days. Moreover, support for deploying to on premise Windows machines is now available. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done.
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		-
16	16	== **Feedback Items** ==
17	17
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.
	10	+//__On premise Windows machines__//
	11	+Support for deploying to on premise Windows machines has been delivered.
20	20
21		-[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
	13	+//__Adding multiple attributes__//
	14	+It is now possible to add multiple existing attributes to an entity at once.
22	22
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.
	16	+//__Monitoring graphs__//
	17	+The monitoring graphs can now show data up to the last 30 days.
25	25
26		-//__Rebuilding of images__//
27		-Changing the list of flows that should run on a container will now trigger the rebuilding of images.
28		-
29	29	== **Bug Fixes** ==
	20	+//__Image versions__//
	21	+The deletion of releases with deployed container versions will not be blocked anymore. Automated release clean up behaviour will also not exclude these releases from deletion. Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases.
30	30
31		-//__Runtime metrics processing__//
32		-The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
	23	+//__Failover group helptext__//
	24	+The helptext of the Group attribute has been improved.
33	33
34		-//__Deployment plan__//
35		-We solved a bug where a deployment step in the deployment plan could randomly get stuck.
	26	+[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
36	36
37		-//__Store message merging__//
38		-The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
	28	+//__Failover group refresh__//
	29	+A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in Group tab of "Start/Stop Flows" screen.
39	39
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.
	31	+[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
42	42
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.
	33	+//__Resource paths__//
	34	+After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
45	45
46		-//__Max fetch size__//
47		-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.
48		-
49	49	== **Fancy Forum Answers** ==
50	50
51	51	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:
52	52
53		-* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	40	+* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
	41	+* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
	42	+* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
54	54
55		-== **Key takeaways** ==
	44	+== **Key Takeaways** ==
56	56
57	57	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:
58	58
...	...	@@ -63,7 +63,6 @@
63	63	* Check out the release notes [here]
64	64	* Start thinking about how the license tracker can aid your development
65	65	* Start thinking about major, minor, and patch
66		-* Upgrade to the latest build number
67	67	* Keep making great integrations
68	68
69	69	Let's stay in touch and till next time!
...	...	@@ -71,7 +71,6 @@
71	71	{{info}}
72	72	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73	73
74		-~*~* Indicates a next-generation-architecture only feature.
75	75	{{/info}}
76	76	)))
77	77