Changes for page 234 - Alert Adventures
Last modified by Carlijn Kokkeler on 2024/11/18 15:29
From version 1.2
edited by eMagiz
on 2022/10/14 13:36
on 2022/10/14 13:36
Change comment:
There is no comment for this version
To version 312.1
edited by Erik Bakker
on 2024/09/09 09:54
on 2024/09/09 09:54
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 185-GetReady1 +229 - Xpath Alignment - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e Magiz1 +XWiki.ebakker - Content
-
... ... @@ -1,18 +1,10 @@ 1 - Releasethatupdatesthe manage statisticssectionsforournewmonitoring stack. On topofthat,wehave releaseda newcloudtemplateand releasedseveral otherfunctionalities.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. Please find all our changes and bug fixes below. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 184-NewBeginnings.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.229 - XPath Alignment||target="blank"]]. 4 4 5 -=====New features===== 6 -* Create - new flow designer has been introduced for all users in the Create phase 7 - ** Right hand panel that displays alerts, properties, support objects and resources 8 - ** Objects can now be put on the canvas without a full configuration 9 - ** Alerts are generated to display incorrect or incomplete configuration 10 - ** Flow versions can be pushed to Deploy only when there are no remaining alerts 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. 11 11 12 - 13 -=====Minor changes===== 14 -* Deploy - Copy property page changed to have a orientation on the runtime. Includes update to that popup for the field runtime 15 - 16 - 17 17 ====Bug fixes==== 18 -* Feedback widget - introduced new version and fixed the interaction 9 +* Create - Flow Designer: Improved the help text 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 it exists. (#1010)