Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+214 - System Symphony

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,90 +1,66 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
	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	6
7		-== **3rd generation runtime bolstering** ==
	8	+== **Feedback Items** ==
8	8
9		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
	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.
10	10
11		-//__Migration of JMS backup configuration improved__//
12		-With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
	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]]
13	13
14		-//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15		-As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
	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.
16	16
17		-//__Autogenerated exits can be deployed at once__//
18		-This release has fixed a bug that prevented you from deploying an exit flow correctly.
	19	+[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]
19	19
20		-//__Code mapping functionality available on 3rd generation runtime__//
21		-As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
	21	+//__Monitoring graphs__//
	22	+The monitoring graphs can now show data up to the last thirty days.
22	22
23		-//__Failing runtimes won't be restarted indefinitely anymore__//
24		-We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
	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.
25	25
26		-== **Exportable Release Audit** ~* ==
	31	+//__Failover group helptext__//
	32	+The helptext of the Group attribute has been improved.
27	27
28		-On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
	34	+[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
29	29
30		-[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
	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.
31	31
32		-{{warning}}Note that the following restrictions apply when exporting an audit document:
33		- * Works **only** for releases that are promoted and made active on **Production**
34		- * You will **only** see changes made during the **current** calendar year
35		- * On the first of April all objects of the **last** calendar year will be **removed**.
36		- ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
	39	+[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
37	37
38		-== **Feedback items ** ==
	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.
39	39
40		-We have also solved other feedback items besides the flow designer's critical updates.
41		-
42		-//__Improved naming convention on Store related pages__//
43		-We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
44		-
45		-//__Press "Enter" to search on multiple pages__//
46		-In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
47		-
48		-* Deploy → Deployment Plan
49		-* Deploy → Properties → History
50		-* Deploy → User Management → Roles
51		-* Manage → Error Messages → Error Messages
52		-* Manage → Error Messages → Flows with Error Messages
53		-* Manage → Error Messages → Exceptions of Error Messages
54		-* Manage → Log Entries
55		-* Manage → Alerts
56		-* Manage → Triggers
57		-* Manage → Tags – Cant find (only Gen2)
58		-* Manage → Notifications
59		-* Manage → Notification Settings
60		-* Manage → Data Usage → History
61		-* Manage → Code mappings → All tabs
62		-
63		-== **Bug fixes ** ==
64		-
65		-//__Loading problems of Deployment plan execution overview__//
66		-We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
67		-
68	68	== **Fancy Forum Answers** ==
69	69
70	70	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:
71	71
72		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
73		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
74		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
	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"]]
75	75
76		-== **Key takeaways** ==
	53	+== **Key Takeaways** ==
77	77
78		-Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	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:
79	79
80	80	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
81	81	* If you have feedback or ideas for us, talk to the Platypus
82		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	59	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
83	83	* Clear your browser cache (Ctrl + Shift + Del)
84	84	* Check out the release notes [here]
85	85	* Start thinking about how the license tracker can aid your development
86	86	* Start thinking about major, minor, and patch
87		-* Upgrade to the latest build number
88	88	* Keep making great integrations
89	89
90	90	Let's stay in touch and till next time!
...	...	@@ -92,6 +92,11 @@
92	92	{{info}}
93	93	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
94	94
95		-~*~* Indicates a GEN3-only feature.
96		-{{/info}})))((({{toc/}}))){{/container}}
	71	+{{/info}}
	72	+)))
	73	+
	74	+(((
	75	+{{toc/}}
	76	+)))
97	97	{{/container}}
	78	+{{/container}}