Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 625.1
edited by Carlijn Kokkeler
on 2024/07/29 12:28
Change comment: There is no comment for this version
To version 706.1
edited by Erik Bakker
on 2024/09/09 10:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -226 - Alerting Alchemy
1 +229 - Xpath Alignment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -3,35 +3,52 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release,
6 +**Hi there, eMagiz developers!** In this release, 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. Find out all the improvements and bug fixes below!
7 7  
8 -== **Feedback Items** ==
9 -//__Queue alerting__//
10 -Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, which includes the following improvements:
11 -* New UI that shows all queues and the alerting that is active on them.
12 -* Every queue in the model will be automatically added to the list of queues in Manage - Alerting.
13 -* Triggers of a queue will be automatically enabled or disabled based on whether that queue is included in the release.
14 -* Added 2 new trigger types "inactivity check" and "periodic activity check" that replace the "queue throughput" alert.
15 -** These checks can now run for a (very) long time, whereas the "queue throughput" was limited by 1 hour.
16 -* The alert generation has been solidified to reduce the likelihood that your alerting is affected with false positives or false negatives during eMagiz maintenance.
17 -* When the same check of multiple queues trigger at the same time, the alerts will be aggregated into a single summarized email instead of a single email per alert.
18 -
19 -If you model is running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, you will be migrated on the day of release. eMagiz will transfer the queue alerts that you have currently configured to the closest match in the new alerting stack. Models that are in the process of migrating to the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture during the time of the release of this feature will be able to pre-configure their new queue alert triggers, but will not be able to make active use of them until the runtime migration has finished.
8 +== **Deployment Plan Improvements** ==
20 20  
21 -//__Tenant technical name__//
22 -
23 -//__Tenant transfer__//
24 -//__Property placeholder__//
10 +//__Monitoring Trigger - Improvements__//
25 25  
12 +* For the step type "Monitoring Trigger," we have re-introduced the "Enable" option.
13 +
14 +[[image:Main.Images.Release Blog.WebHome@release-229-enable-option.png]]
15 +
16 +* The "Disable" option under this step type comes with two new options.
17 +** End Action. Here, you can opt for the following three options
18 +*** Auto-enable triggers
19 +*** Send email
20 +*** Both
21 +* Duration. Here, you can define a waiting period that states how long eMagiz should wait before executing the end action. The value of this field needs to lie between 15 and 120 minutes. Note that the timer starts when your deployment plan's "disable" step is finished.
22 +
23 +[[image:Main.Images.Release Blog.WebHome@release-229-disable-option.png]]
24 +
25 +{{warning}}Note that the end action is only triggered when the deployment plan cannot complete all steps. When all steps are completed, the timer is **stopped**. Therefore, we advise adding the "enable" step back to the end of your deployment plan to ensure that triggers are automatically re-enabled when the deployment is successfully finished. This also covers cases where the deployment plan is automatically executed (by pressing the play button), after which the user moves on to other things and forgets to move away from the page once the deployment plan is completed.
26 +
27 +In the coming weeks, we will actively monitor eMagiz models to see to what extent this advice has been implemented.{{/warning}}
28 +
29 +
30 +//__Default Plan - Improvements__//
31 +
32 +* When you press the "Default Plan" option, the following changes will occur (assuming you also have a default plan on your environment).
33 +
34 +* The existing "Disable" step is extended to define that eMagiz will automatically enable triggers after 60 minutes have passed.
35 +* The "Enable" step is added as the last step of your deployment plan.
36 +
37 +[[image:Main.Images.Release Blog.WebHome@release-229-new-default-plan.png]]
38 +
26 26  == **Bug Fixes** ==
40 +//__XPath Header Enricher - Help Text Improvement__//
41 +We have added various help text segments that explain which results the XPath expression will yield in this context and how to ensure that a list of results is returned when executing this action.
27 27  
43 +//__XPath Configuration - Transformation__//
44 +We fixed a bug that caused data loss once you switched between the "custom xpath" and "if exists" options when adding a filter or transformation in the Create Transformation tooling.
45 +
28 28  == **Fancy Forum Answers** ==
29 29  
30 30  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
31 31  
32 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
33 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
34 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
50 +* [[Spaces handled differently in folder name after using SMB components for file connectivity>>https://my.emagiz.com/p/question/172825635703940018||target="blank"]]
51 +* [[How to process messages with invalid XML content like "&#x2">>https://my.emagiz.com/p/question/172825635703939917||target="blank"]]
35 35  
36 36  == **Key Takeaways** ==
37 37  
... ... @@ -41,7 +41,7 @@
41 41  * If you have feedback or ideas for us, talk to the Platypus
42 42  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
43 43  * Clear your browser cache (Ctrl + Shift + Del)
44 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
61 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.229 - Xpath Alignment.WebHome||target="blank"]]
45 45  * Start thinking about how the license tracker can aid your development
46 46  * Start thinking about major, minor, and patch
47 47  * Keep making great integrations