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	+197 - Pay Attention

Content

...	...	@@ -2,72 +2,59 @@
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 our next-generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore, several smaller feedback items and bugs have been resolved with this release. So without further ado, let us dive into all we have to offer.
6	6
7		-== **3rd generation runtime bolstering** ==
	7	+== **Event streaming alerting** ==
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	+This release expands our alerting functionality into the event streaming pattern. As of now, one new "static" alert has been introduced for all clients (using event streaming), and two "dynamic" alerts have been introduced that you can configure yourself if there is a need for it.
10	10
11		-//__Migration of JMS backup configuration improved__//
	11	+The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights into whether messages on it are deleted due to a size or time constraint. In cases where data is deleted, the topic was too full way before the messages should have been removed due to the retention hours constraint. This alert can indicate that messages might be deleted before consumer groups had the option to consume the messages.
12	12
13		-//__Prechecks on Upgrade option made available for 3rd generation runtime__//
	13	+The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
14	14
15		-//__Autogenerated exits can be deployed at once__//
	15	+[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
16	16
17		-//__Code mapping functionality available on 3rd generation runtime__//
	17	+The first new "dynamic" alert allows you to raise an alert once the number of messages on one (or more topics) is less than a certain number per defined time unit. So, for example, you can configure an alert once the number of messages placed on a topic called "Exception" is less than 15 messages within 5 minutes.
18	18
19		-//__Improved the performance of deploying or activating a release__//
	19	+[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
20	20
21		-//__Failing runtimes won't be restarted indefinetly anymore__//
	21	+The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups are more than X messages behind on one or more topics. The configuration of this is comparable to what we saw before.
22	22
23		-== **Exportable Release Audit** ~* ==
	23	+For more information on the generic way of working surrounding alerting, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
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.
	25	+== **3rd generation improvements** ==
26	26
27		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
	27	+//__Increased grace period for shutdown__//
	28	+In this release, we have increased a container's grace period to shut down before it is forcefully shut down. This should reduce the chance of unwanted failover behavior within your model.
28	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}}
	30	+//__Update at once or not__//
	31	+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.
34	34
35		-== **Feedback items ** ==
	33	+//__Improved user feedback while executing a deployment plan__//
	34	+This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information about why this cannot be executed is shown to the user. This way, they can take this information and act upon it instead of assuming everything went well.
36	36
37		-We have also solved other feedback items besides the flow designer's critical updates.
	36	+//__Improved auto-healing when running in a hybrid situation__//
	37	+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.
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.
	39	+//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
	40	+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.
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.
	42	+{{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}}
44	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
	44	+== **Feedback items ** ==
47	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
	46	+//__Make sure the message format can be viewed without "Start editing"__//
	47	+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.
62	62
	49	+//__Various styling improvements in the flow testing functionality__//
	50	+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.
	51	+
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"]]
	56	+* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
	57	+* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
71	71
72	72	== **Key takeaways** ==
73	73