Skip to Content

Changes for page 233 - Policy Polish

Last modified by Carlijn Kokkeler on 2024/11/06 14:06
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 329.1
edited by Carlijn Kokkeler
on 2024/10/07 15:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -229 - Xpath Alignment
1 +231 - Microscopic Madness
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,10 +1,18 @@
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 improved the search options for flow testing logs and monitoring logs. Next to this, we fixed the unused properties overview and improved the deletion functionality of router containers.
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.231 - Microscopic Madness||target="blank"]].
4 4  
5 +
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 +* Create - Flow Testing: Search options for flow testing logs have been improved.
8 +** Improved search options for flow test logs. You can now search for 'logger' and 'message', search for 'timestamp from' and 'to' have been removed.
9 +** Unified the UI with Manage phase logging for a more streamlined experience
10 +* Manage - Monitoring: Search options for monitoring logs have been improved.
11 +** Unified the UI with flow testing log interface, showing the message and stack trace (if available) in 2 different tabs
12 +** Added the 'logger' column that shows the last part of the logger name.
13 +** Added a search field for ‘logger’
7 7  
15 +
8 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)
17 +* Deploy - Architecture: Router containers that were deleted from the Deploy Architecture, are now cleaned up completely from the environment.
18 +* Deploy - Releases: We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. (#1442)