Changes for page 240 - Spring Cleaning

Summary

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

Details

Page properties

Content

...	...	@@ -9,8 +9,7 @@
9	9	//__Error alerting__//
10	10	Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, following our queue alerting design that has been [[released>>doc:Main.Release Information.Release Blogs.226 - Alerting Alchemy.WebHome||target="blank"]] a couple of months ago. The new error alerting feature allows you to trigger an alert on all incoming errors, or choose to trigger when specific filters on the error’s headers, message or class have been met. Furthermore, you can select the specific runtime the error originated from as one of the filters as well.
11	11
12		-{{info}}
13		-Please take into consideration the following migration actions:
	12	+{{info}}Please take into consideration the following migration actions:
14	14	* All existing error message alert triggers from the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture models will be automatically migrated to the new alerting feature.
15	15	* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
16	16	** The 'Description' field has been replaced by the new 'Instructions' field (note: the 'Description' field no longer exists).
...	...	@@ -18,9 +18,12 @@
18	18	* Additionally, a new field, 'Name', has been introduced for identification purposes. The 'Name' field will be included in email notifications when a trigger is activated.
19	19	** This field will be automatically populated with a default name (e.g., "Error Trigger 1").
20	20	** **Users are advised to review and update these names to appropriately reflect each trigger's purpose**.
	20	+* If an error message alert trigger has the following specific configuration, its trigger conditions will be migrated such that alerts are triggered for **all** incoming error messages:
	21	+** "Check header" is disabled.
	22	+** "Check error message" is enabled.
	23	+** The "Error message contains" field includes only a single character.
	24	+* The new feature introduces duplicate detection when saving an individual error trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate error alerts.{{/info}}
21	21
22		-{{/info}}
23		-
24	24	{{warning}}To keep a better overview, we recommend you to remove your old dynamic triggers after the new error triggers are activated, these have already been disabled by our migration process. The same applies for your queue-related triggers. These triggers can be found under the ‘Other’ tab on the alert triggers page.{{/warning}}
25	25
26	26	{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/warning}}