229 - XPath Alignment

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.

Please find out more on our Release blog.

Minor changes

• 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)
• Create - Flow Designer: SFTP (caching) session factories now have an additional option to specify the authentication methods that should be used, and in which order. Note that the latest runtime image is needed to make the functionality work in eMagiz. 

Bug fixes

• Create - Flow Designer: Improved the help text of the edit/new header menu in the XPath header enricher component, to better inform how a list of results can be handled. (#727)
• Create - Transformation: Fixed a bug that caused the value input field to disappear if you switch from “custom xpath“ to “if it exists“. (#1010)
• Create - Flow designer: We fixed an issue related to the legacy property “web service-URL “ of an exit connector flow to a Mendix (connector) system. In your Mendix application, you can download and start them as you are used to.