Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 644.1
edited by Carlijn Kokkeler
on 2024/07/30 13:10
Change comment: There is no comment for this version
To version 638.1
edited by Carlijn Kokkeler
on 2024/07/29 13:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,7 +3,7 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** The past few weeks we have worked hard to release our new queue alerting design. Please find out all new features in our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning. Note that the new queue alerting will not yet be availalbe for queues with message redelivery. Next to alerting, we have worked on tenant items, machine pop-ups and progress bars, as well as the Infinispan Cache Manager. Find out all below!
6 +**Hi there, eMagiz developers!** The past few weeks we have worked hard to release our new queue alerting design. Please find out all new features in our [[Standard Alerting eMagiz microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]]. Note that the new queue alerting will not yet be availalbe for queues with message redelivery. Next to alerting, we have worked on tenant items, machine pop-ups and progress bars, and the Infinispan Cache Manager. Find out all below!
7 7  
8 8  == **Feedback Items** ==
9 9  //__Queue alerting__//
... ... @@ -16,16 +16,16 @@
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 -[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
19 +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.
20 20  
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}}
21 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/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.
23 +{{info}}Please check out our [[Standard Alerting eMagiz microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] for an elaborate explanation of our new queue alerting design. {{/info}}
24 24  
25 -{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}}
25 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
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.
28 + 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.
... ... @@ -61,7 +61,7 @@
61 61  * If you have feedback or ideas for us, talk to the Platypus
62 62  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
63 63  * Clear your browser cache (Ctrl + Shift + Del)
64 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
64 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
65 65  * Start thinking about how the license tracker can aid your development
66 66  * Start thinking about major, minor, and patch
67 67  * Keep making great integrations