Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 625.1
edited by Carlijn Kokkeler
on 2024/07/29 12:28
Change comment: There is no comment for this version
To version 629.1
edited by Carlijn Kokkeler
on 2024/07/29 12:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,12 +16,19 @@
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 -If you 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.
20 20  
20 +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.
21 +
22 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
23 +
21 21  //__Tenant technical name__//
22 -
25 + The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
26 +
23 23  //__Tenant transfer__//
28 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
29 +
24 24  //__Property placeholder__//
31 +A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
25 25  
26 26  == **Bug Fixes** ==
27 27