Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-197 - Pay Attention
	1	+194 - Giant Leap

Content

...	...	@@ -2,54 +2,65 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
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.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have worked around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.
6	6
7		-== **Event streaming alerting** ==
	7	+== **3rd generation improvements** ==
8	8
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.
	9	+//__Better feedback in the error log when a corrupt stylesheet is encountered__//
	10	+We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
10	10
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	+//__Better internal error handling to avoid unnecessary alerting and notifications__//
	13	+We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the alerts you receive on this topic when your model runs on the 3rd generation monitoring stack.
12	12
13		-The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
	15	+//__Improved Manage Dashboard__//
	16	+This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime architecture.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
	18	+//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
	19	+When a slot is put into standby mode, we also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. The opposite happens when the slot wakeup is triggered. As a result, not only the cloud runtimes are started but also all on-premise runtimes.
16	16
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.
	21	+//__Improved process of deploy preparation__//
	22	+With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
	24	+//__Improved migration of Streaming container__//
	25	+When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention.
20	20
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.
	27	+//__Add History to Notifications in Manage__//
	28	+To improve the auditability of our platform, we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way, it is always visible when the notifications were paused and who paused or unpaused the notifications.
22	22
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"]].
	30	+//__Improved Manage phase for Event Streaming__//
	31	+Based on the feedback on our first iteration of the Manage phase for Event Streaming, we have improved the graphs and the calculations that fill the graphs with values. On top of that, we have added help texts to clarify what each chart our table displays to you.
24	24
25		-== **3rd generation improvements** ==
	33	+//__Improved help text for network volumes__//
	34	+With this release, we have improved the help text that explains network volumes and how to use them within our solution.
26	26
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.
	36	+{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
29	29
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.
	38	+== **Feedback items ** ==
32	32
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.
	40	+//__Generation of security logic API Gateway in case of API Key as security method is improved__//
	41	+With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
35	35
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.
	43	+//__User Roles are sorted alphabetically__//
	44	+All user roles under User Management are now also sorted alphabetically.
38	38
39		-== **Feedback items ** ==
	46	+//__Name of keystore for user management now includes the environment__//
	47	+To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename.
40	40
41		-//__Make sure the message format can be viewed without "Start editing"__//
42		-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.
	49	+== **Bug fixes ** ==
43	43
44		-//__Various styling improvements in the flow testing functionality__//
45		-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	+//__Consolidated upgrade process cloud template__//
	52	+With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud.
46	46
	54	+//__Ensure users can deploy release on environments they have edit rights on__//
	55	+Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so.
	56	+
47	47	== **Fancy Forum Answers** ==
48	48
49	49	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:
50	50
51		-* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
52		-* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
	61	+* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
	62	+* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
	63	+* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
53	53
54	54	== **Key takeaways** ==
55	55