Changes for page 215 - Tiny Tales

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,62 +3,51 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
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.
	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 thirty days. Moreover, we can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. 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’ 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		-//__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.
	10	+//__On premise Windows machines__//
	11	+We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
20	20
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.
	13	+[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]
23	23
24		-[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
	15	+//__Adding multiple attributes__//
	16	+It is now possible to add multiple existing attributes to an entity at once.
25	25
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.
	18	+[[image:Main.Images.Microlearning.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]
28	28
29		-//__Rebuilding of images__//
30		-Changing the list of flows that should run on a container will now trigger the rebuilding of images.
	20	+//__Monitoring graphs__//
	21	+The monitoring graphs can now show data up to the last thirty days.
31	31
32	32	== **Bug Fixes** ==
	24	+//__Image versions__//
	25	+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.
33	33
34		-//__Runtime metrics processing__//
35		-The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
	27	+//__Failover group helptext__//
	28	+The helptext of the Group attribute has been improved.
36	36
37		-//__Deployment plan__//
38		-We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
	30	+[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
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.
	32	+//__Failover group refresh__//
	33	+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.
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.
	35	+[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
45	45
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.
	37	+//__Resource paths__//
	38	+After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
48	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		-* [[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"]]
	44	+* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]]
	45	+* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]]
	46	+* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]]
	47	+* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]]
58	58
	49	+== **Key Takeaways** ==
59	59
60		-== **Key takeaways** ==
61		-
62	62	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:
63	63
64	64	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
...	...	@@ -68,7 +68,6 @@
68	68	* Check out the release notes [here]
69	69	* Start thinking about how the license tracker can aid your development
70	70	* Start thinking about major, minor, and patch
71		-* Upgrade to the latest build number
72	72	* Keep making great integrations
73	73
74	74	Let's stay in touch and till next time!
...	...	@@ -76,7 +76,6 @@
76	76	{{info}}
77	77	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78	78
79		-~*~* Indicates a next-generation-architecture only feature.
80	80	{{/info}}
81	81	)))
82	82