Skip to Content

Changes for page 230 - Petite Peaks

Last modified by Carlijn Kokkeler on 2024/09/27 09:36
From version 326.1
edited by Carlijn Kokkeler
on 2024/09/27 09:36
Change comment: There is no comment for this version
To version 316.1
edited by Erik Bakker
on 2024/09/09 11:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -230 - Petite Peaks
1 +229 - XPath Alignment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,13 +1,10 @@
1 -During our recent sprint cycle, we improved the functionality of adding an integration to an existing API in Design, ensured that queues with illegal characters will not generate errors anymore, and we fixed an issue where the execution of a deployment step would be blocked. Read all about it below!
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.230 - Petite Peaks||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 -* All - Failover: We have introduced a new failover feature, allowing you to enable failover on messaging flows with minimal setup required. Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]].
7 -
8 8  ====Minor changes====
9 -* Design - Solution Design: When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
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)
10 10  
11 11  ====Bug fixes====
12 -* Manage - Explore: Queues with illegal characters will not generate errors anymore. As a result they can be explored and if needed removed from your model.
13 -* Deploy - Deployment: We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
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)