Skip to Content

Changes for page 234 - Alert Adventures

Last modified by Carlijn Kokkeler on 2024/11/18 15:29
From version 200.1
edited by Carlijn Kokkeler
on 2024/02/16 12:08
Change comment: There is no comment for this version
To version 312.1
edited by Erik Bakker
on 2024/09/09 09:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -214 - System Symphony
1 +229 - Xpath Alignment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,21 +1,10 @@
1 -In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
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.214 - System Symphony||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=====
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.
6 6  
7 -* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once. (#1141)
8 -* Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
9 -
10 -=====Minor changes=====
11 -
12 -* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore. (#1216)
13 -* Manage - Monitoring: New functionality to ensure that the monitoring graphs in Manage can show data from the last thirty days.
14 -
15 15  ====Bug fixes====
16 -
17 -* Create - Flow Designer: The help text of the Group attribute has been improved.
18 -* Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802)
19 -* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed.
20 -
21 -
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)