Wiki source code of 229 - XPath Alignment

Version 708.1 by Danniar Firdausy on 2024/09/09 12:34

Hide last authors
eMagiz 1.1 1 {{container}}
CarlijnKokkeler 254.1 2 {{container layoutStyle="columns"}}
3 (((
Erik Bakker 401.1 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
eMagiz 1.1 5
Erik Bakker 705.1 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!
CarlijnKokkeler 567.1 7
Erik Bakker 705.1 8 == **Deployment Plan Improvements** ==
Erik Bakker 700.1 9
Erik Bakker 705.1 10 //__Monitoring Trigger - Improvements__//
Erik Bakker 697.1 11
Erik Bakker 705.1 12 * For the step type "Monitoring Trigger," we have re-introduced the "Enable" option.
Erik Bakker 698.1 13
Erik Bakker 705.1 14 [[image:Main.Images.Release Blog.WebHome@release-229-enable-option.png]]
Erik Bakker 699.1 15
Erik Bakker 705.1 16 * The "Disable" option under this step type comes with two new options.
Danniar Firdausy 708.1 17 ** End Action. Here, you can opt for the following three options:
Erik Bakker 705.1 18 *** Auto-enable triggers
19 *** Send email
20 *** Both
Danniar Firdausy 708.1 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.
Erik Bakker 701.1 22
Erik Bakker 705.1 23 [[image:Main.Images.Release Blog.WebHome@release-229-disable-option.png]]
Erik Bakker 697.1 24
Erik Bakker 705.1 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}}
CarlijnKokkeler 677.1 28
29
Erik Bakker 705.1 30 //__Default Plan - Improvements__//
Erik Bakker 693.1 31
Erik Bakker 705.1 32 * When you press the "Default Plan" option, the following changes will occur (assuming you also have a default plan on your environment).
Erik Bakker 693.1 33
Erik Bakker 705.1 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.
Erik Bakker 697.1 36
Erik Bakker 705.1 37 [[image:Main.Images.Release Blog.WebHome@release-229-new-default-plan.png]]
CarlijnKokkeler 664.1 38
CarlijnKokkeler 651.1 39 == **Bug Fixes** ==
Erik Bakker 705.1 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.
CarlijnKokkeler 651.1 42
Erik Bakker 705.1 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.
CarlijnKokkeler 680.1 45
eMagiz 1.1 46 == **Fancy Forum Answers** ==
47
Erik Bakker 30.1 48 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:
eMagiz 1.1 49
Erik Bakker 705.1 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"]]
eMagiz 1.1 52
CarlijnKokkeler 348.1 53 == **Key Takeaways** ==
eMagiz 1.1 54
Erik Bakker 149.1 55 Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
eMagiz 1.1 56
Erik Bakker 30.1 57 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
eMagiz 1.1 58 * If you have feedback or ideas for us, talk to the Platypus
Erik Bakker 151.1 59 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
eMagiz 1.1 60 * Clear your browser cache (Ctrl + Shift + Del)
Erik Bakker 706.1 61 * Check out the release notes [[here>>doc:Main.Release Information.Portal.229 - Xpath Alignment.WebHome||target="blank"]]
eMagiz 1.1 62 * Start thinking about how the license tracker can aid your development
63 * Start thinking about major, minor, and patch
64 * Keep making great integrations
65
66 Let's stay in touch and till next time!
Danniar Firdausy 582.1 67
Danniar Firdausy 580.2 68 {{info}}
69 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
Danniar Firdausy 574.46 70
Danniar Firdausy 580.2 71 {{/info}}
CarlijnKokkeler 254.1 72 )))
73
74 (((
75 {{toc/}}
76 )))
eMagiz 1.1 77 {{/container}}
CarlijnKokkeler 254.1 78 {{/container}}