Changes for page 198 - Great Migration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+198 - Great Migration

Content

...	...	@@ -2,72 +2,46 @@
2	2	{{container layoutStyle="columns"}}(((
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 the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving the migration towards our next-generation architecture as well as improved the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our own infrastructure to ensure that all data flowing via this infrastructure now more and more customers are migrating can be handled as good if not better as before.
6	6
7		-== **3rd generation runtime bolstering** ==
	7	+== **3rd generation improvements and bug fixes** ==
8	8
9		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
	9	+//__"Stop" action when running a hybrid situation is not causing issues anymore__//
	10	+Before, it could happen when running a double-lane setup in a hybrid situation (i.e karaf based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release that behavior is changed.
10	10
11		-//__Migration of JMS backup configuration improved__//
	12	+{{info}}Note that this fix is part of a new runtime image for the karaf based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
12	12
13		-//__Prechecks on Upgrade option made available for 3rd generation runtime__//
	14	+//__Removed certain dependencies between Deploy Architecture and Releases__//
	15	+In this release, we have removed several specific dependencies that caused confusion between the functionality in the Deploy Architecture overview compared to the functionality that is linked to a release and specifically the deployment of a release.
14	14
15		-//__Autogenerated exits can be deployed at once__//
	17	+//__Improved validation errors on invalid configuration of HTTP outbound components__//
	18	+This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
16	16
17		-//__Code mapping functionality available on 3rd generation runtime__//
	20	+//__Improved migration behavior__//
	21	+This release introduces several improvements with regards to the migration behavior via "Transfer settings from Design". Among these are a smoother migration of your JMS (and backup JMS) process, additional feedback given to the user and feedback when the migration process is finished.
18	18
19		-//__Improved the performance of deploying or activating a release__//
	23	+//__Improved auto-healing when running in a hybrid situation__//
	24	+In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
20	20
21		-//__Failing runtimes won't be restarted indefinetly anymore__//
	26	+//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
	27	+To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
22	22
23		-== **Exportable Release Audit** ~* ==
	29	+{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
24	24
25		-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.
26		-
27		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
28		-
29		-{{warning}}Note that the following restrictions apply when exporting an audit document:
30		- * Changes made on definition and transformation level are **not** restored
31		- * You will **not** be able to restore to any flow version that was created before October 17th, 2022
32		- * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
33		- * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
34		-
35	35	== **Feedback items ** ==
36	36
37		-We have also solved other feedback items besides the flow designer's critical updates.
	33	+//__Make sure the message format can be viewed without "Start editing"__//
	34	+With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
38	38
39		-//__Data Sink Refactor__//
40		-We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
	36	+//__Various styling improvements in the flow testing functionality__//
	37	+Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
41	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. With this release we have 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	63	== **Fancy Forum Answers** ==
64	64
65	65	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:
66	66
67		-* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
68		-* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
69		-* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
70		-* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
	43	+* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
	44	+* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
71	71
72	72	== **Key takeaways** ==
73	73