Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 323.1
edited by Carlijn Kokkeler
on 2024/09/23 13:48
Change comment: There is no comment for this version
To version 285.1
edited by Carlijn Kokkeler
on 2024/07/29 14:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -230 - Petite Peaks
1 +226 - Alerting Alchemy
Content
... ... @@ -1,10 +1,12 @@
1 -During our recent sprint cycle, we improved the functionality of adding an integration to an existing API in Design, ensured that queues with illegal characters will not generate errors anymore, and we fixed an issue where the execution of a deployment step would be blocked. Read all about it below!
1 +During our recent sprint cycle, we have worked to release a new design for queue alerting. 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. Moreover, we have worked on tenant items, machine pop-ups and progress bars, as well as the Infinispan Cache Manager. Please find out all below!
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.230 - Petite Peaks||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.226 - Alerting Alchemy||target="blank"]].
4 4  
5 5  ====Minor changes====
6 -* Design - Solution Design: When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
7 -
8 -====Bug fixes====
9 -* Manage - Explore: Queues with illegal characters will not generate errors anymore.
10 -* Deploy - Deployment: We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
6 +* Create - Flow Designer: The Infinispan Cache Manager has been updated to provide an additional 'transport type' to offer more means for creating a clustered setup, provide clearer helptexts, and include validation on fields depending on the selected 'transport type'.
7 +* Design - Tenant: The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
8 +* Create - Tenant: A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
9 +* Deploy - Architecture: The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
10 +* Deploy - Architecture: The machine health indicator and other progress bars have been improved visually.
11 +* Deploy - Properties: A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
12 +* Manage - Alerting: Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. Find out more information in our [[release blog>>Main.Release Information.Release Blogs.226 - Alerting Alchemy||target="blank"]] and our [[new alerting microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]].