Skip to Content

Changes for page 233 - Policy Polish

Last modified by Carlijn Kokkeler on 2024/11/06 14:06
From version 317.1
edited by Erik Bakker
on 2024/09/09 15:19
Change comment: There is no comment for this version
To version 310.1
edited by Erik Bakker
on 2024/09/09 09:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -229 - XPath Alignment
1 +229 - Xpath Alignment
Content
... ... @@ -1,10 +1,7 @@
1 -During our recent sprint cycle, we made several improvements to keep our model running smoothly. We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Please find all our changes and bug fixes below.
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.
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.229 - XPath Alignment||target="blank"]].
4 4  
5 -====Minor changes====
6 -* Deploy - Deployment plan: We updated the deployment step that temporarily disables the triggers in your model. As a result, you can now 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, which 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 before deploying. This can be done via the Manage phase. (#1367)
7 -
8 8  ====Bug fixes====
9 -* Create - Flow Designer: Improved the help text of the edit/new header menu in the XPath header enricher component, to better inform how a list of results can be handled. (#727)
10 -* Create - Transformation: Fixed a bug that caused the value input field to disappear if you switch from “custom xpath“ to “if it exists“. (#1010)
6 +* Create - Flow Designer: Improved the helptext of the edit/new header menu in the XPath header enricher component (#727)
7 +* Create - Transformation: Fixed bug that causes the value input field to disappear if you switch from custom xpath to if exists. (#1010)