Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 311.1
edited by Erik Bakker
on 2024/09/09 09:52
Change comment: There is no comment for this version
To version 287.1
edited by Carlijn Kokkeler
on 2024/08/12 11:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -229 - Xpath Alignment
1 +227 - Fix Frenzy
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,10 +1,12 @@
1 -During our recent sprint cycle, we have done several improvements to keep our model running smoothly. Moreover, we have made some small changes to various XPath related parts of the portal. Please find out all our changes & bug fixes below.
1 +During our recent sprint cycle, we have ......
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.229 - XPath Alignment||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]].
4 4  
5 5  ====Minor changes====
6 -* Deploy - Deployment plan: We updated the deployment step that temporary disables the triggers in your model. As a result you now have the ability to define after which waiting period (determined in minutes) you want eMagiz to take action. When it reaches this point, eMagiz will act according to the selected option. You can opt to "automatically re-enable triggers", "receive a notification mail", or "both". On top of that we reintroduced the automatic "enable trigger" step that can be added as the last step of your deployment plan to automatically re-enable triggers. Be aware that you *still* need to enable triggers manually if you have manually disabled them prior to deploying. This can be done via the Manage phase.
7 -
8 -====Bug fixes====
9 -* Create - Flow Designer: Improved the helptext of the edit/new header menu in the XPath header enricher component (#727)
10 -* Create - Transformation: Fixed bug that causes the value input field to disappear if you switch from custom xpath to if exists. (#1010)
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"]].