Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 643.1
edited by Carlijn Kokkeler
on 2024/07/30 13:10
Change comment: There is no comment for this version
To version 648.1
edited by Carlijn Kokkeler
on 2024/07/30 16:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -15,17 +15,18 @@
15 15  ** These checks can now run for a (very) long time, whereas the "queue throughput" was limited by 1 hour.
16 16  * The alert generation has been solidified to reduce the likelihood that your alerting is affected with false positives or false negatives during eMagiz maintenance.
17 17  * When the same check of multiple queues trigger at the same time, the alerts will be aggregated into a single summarized email instead of a single email per alert.
18 -
18 +
19 19  [[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
20 20  
21 +
21 21  {{info}}Please check out our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning for an elaborate explanation of our new queue alerting design. {{/info}}
22 22  
23 -If your model is running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, you will be migrated on the day of release. eMagiz will transfer the queue alerts that you have currently configured to the closest match in the new alerting stack. Models that are in the process of migrating to the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture during the time of the release of this feature will be able to pre-configure their new queue alert triggers, but will not be able to make active use of them until the runtime migration has finished.
24 +eMagiz will migrate your dynamic queue alerts on the **release day** when you are **fully** or **partially** migrated to the [[current runtime architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]. When doing so, we will configure the new queue alert in a similar fashion to best match its current behaviour. Note that the queue alerting will only function for models that are **fully** migrated to the [[current runtime architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]. Should you want to change or create new queue alerts, you can do so starting the day **after** the release to avoid conflicts with our migration.
24 24  
25 -{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}}
26 +{{warning}}Please note that the new queue alerting will not yet be available for models with message redelivery. {{/warning}}
26 26  
27 27  //__Tenant technical name__//
28 -The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
29 +For multi-tenant system integrations, the technical name of a tenant cannot be changed once the tenant has been transferred to Create.
29 29  
30 30  //__Tenant transfer__//
31 31  A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.