Changes for page 215 - Tiny Tales

Summary

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

Details

Page properties

Title

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

Content

...	...	@@ -3,54 +3,43 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
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.
	6	+**Hi there, eMagiz developers!** We have...
7	7
8		-== **Feedback Items** ==
	8	+== **Release Maintenance** ==
9	9
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.
12	12
13		-[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]
14		- [[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-windows.png]]
15	15
16		-//__Adding multiple attributes__//
17		-It is now possible to add multiple existing attributes to an entity at once. This saves time when having to add multiple attributes to an entity.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]
20	20
21		-//__Monitoring graphs__//
22		-The monitoring graphs can now show data up to the last thirty days.
	14	+== **Feedback Items** ==
23	23
24		-== **Bug Fixes** ==
25		-//__Image versions__//
26		-To keep the overview of releases compact we now have improved the (automatic) deletion behavior in the following way:
27		-* The deletion of releases with deployed container versions will not be blocked anymore.
28		-* Automated release clean up behaviour will also not exclude these releases from deletion.
29		-* 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.
	16	+//__Container version overview__//
	17	+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.
30	30
31		-//__Failover group helptext__//
32		-The helptext of the Group attribute has been improved.
	19	+[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
33	33
34		-[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
	21	+//__Unchanged containers__//
	22	+When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
35	35
36		-//__Failover group refresh__//
37		-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 the Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed.
	24	+//__Rebuilding of images__//
	25	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
38	38
39		-[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
40	40
41		-//__Resource paths__//
42		-After migrating a gateway away fom the legacy runtime architecture, the path references in the event processors would be broken. This has been fixed.
	28	+== **Bug Fixes** ==
43	43
	30	+//__Runtime metrics processing__//
	31	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
	32	+
	33	+//__Deployment plan__//
	34	+We solved a bug where a deployment step in the deployment plan could randomly get stuck.
	35	+
44	44	== **Fancy Forum Answers** ==
45	45
46	46	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:
47	47
48		-* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]]
49		-* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]]
50		-* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]]
51		-* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]]
	40	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
52	52
53		-== **Key Takeaways** ==
	42	+== **Key takeaways** ==
54	54
55	55	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:
56	56
...	...	@@ -61,6 +61,7 @@
61	61	* Check out the release notes [here]
62	62	* Start thinking about how the license tracker can aid your development
63	63	* Start thinking about major, minor, and patch
	53	+* Upgrade to the latest build number
64	64	* Keep making great integrations
65	65
66	66	Let's stay in touch and till next time!
...	...	@@ -68,6 +68,7 @@
68	68	{{info}}
69	69	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70	70
	61	+~*~* Indicates a next-generation-architecture only feature.
71	71	{{/info}}
72	72	)))
73	73