Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 853.1
edited by Erik Bakker
on 2025/02/10 09:27
Change comment: There is no comment for this version
To version 715.1
edited by Carlijn Kokkeler
on 2024/09/23 11:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -238 - Preparation Paraside
1 +230 - Petite Peaks
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -3,29 +3,61 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we focused on finishing the first iteration of our new eMagiz Mendix Connector and the first iteration of our new base image. We will first utilize the new eMagiz Mendix Connector to get an even better feeling of its performance, but you will notice a UI change straightaway. Once we have passed that hurdle, we will share more information about it and release it to a broader range of customers. Regarding the base image, we will now introduce this to our flow testing offering to see if anything unexpected happens. This is an additional safety measure we have put in place to reduce the chance of something breaking in your model once the new base image is released. On top of that, we have some minor updates to improve the quality of the platform.
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 -== **Updated Base Image** - Flow Testing Only ==
9 -
10 -With this release we introduce the new [[runtime image>>Main.Release Information.Runtime Images||target="blank"]] to our flow testing functionality. This means that as of that moment your flow tests will run against the latest runtime image. We do this to decrease the likelihood of unexpected things happening on your actual environments once we release the image to the community.
8 +== **Deployment Plan Improvements** ==
11 11  
12 -{{info}}
13 -* **Please take into consideration the following**:
14 -* This means that the flow testing results could differ from the results you get once you have deployed your functionality to an environment. If something like that happens please contact us via our [[support department>>mailto:support@emagiz.com]].
15 -{{/info}}
10 +//__Monitoring Trigger - Improvements__//
16 16  
17 -== **New eMagiz Mendix Connector**~* ==
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.
18 18  
19 -The new eMagiz Mendix Connector is ready and will be first implemented in our own infrastructure to further assess the quality and stability of the new connector. Once this is done we will share more information to the community about the changes related to the new eMagiz Mendix Connector and make it available for a broader audience. In the mean time you will already notice a UI change that identifies Mendix systems by showing the Mendix icon on these systems.
27 +In the coming weeks, we will actively monitor eMagiz models to see to what extent this advice has been implemented.{{/warning}}
20 20  
29 +//__Default Plan - Improvements__//
30 +
31 +* When you press the "Default Plan" option, the following changes will occur (assuming you also have a default plan on your environment):
32 +** The existing "Disable" step is extended to define that eMagiz will automatically enable triggers after 60 minutes have passed.
33 +** The "Enable" step is added as the last step of your deployment plan.
34 +
35 +[[image:Main.Images.Release Blog.WebHome@release-229-new-default-plan.png]]
36 +
37 +== **SFTP Authentication Option Added - New Runtime Image** ==
38 +
39 +With this release we launch a new runtime image that provides an additional configuration option on our SFTP (caching) session factory support object. With this option you can define the **order** in which the authentication is handled and which options are **allowed**. The following options are possible. The default configuration option (which is valid in 99% of the cases) is "Keyboard-Interactive and Password".
40 +
41 +* Password
42 +* Keyboard-Interactive
43 +* Password and Keyboard-Interactive
44 +* Keyboard-Interactive and Password
45 +
46 +[[image:Main.Images.Release Blog.WebHome@release-229-new-auth-option-sftp.png]]
47 +
21 21  == **Bug Fixes** ==
22 -//__Removing integrations from Create__//
23 -When removing an exit/entry connector linked to a system and using the same message type can now be removed from eMagiz without problems.
49 +//__XPath Header Enricher - Help Text Improvement__//
50 +We have added a help text segment that explain that you will get the first result back if your XPath returns a list of values. Secondly, we have added an additional help text segment that explains how to change the XPath expression in case you want to get a list of values back.
51 +
52 +//__XPath Configuration - Transformation__//
53 +We fixed a bug that caused the “Value“ input field to disappear once you switched from the "custom xpath" to the "if exists" option when adding a Conditional block in the Create Transformation tooling.
54 +
24 24  == **Fancy Forum Answers** ==
25 25  
26 26  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:
27 27  
28 -* [[Issue with importing XSD into eMagiz, replacing '=ref' references>>https://my.emagiz.com/p/question/172825635704054981||target="blank"]]
59 +* [[Spaces handled differently in folder name after using SMB components for file connectivity>>https://my.emagiz.com/p/question/172825635703940018||target="blank"]]
60 +* [[How to process messages with invalid XML content like "&#x2">>https://my.emagiz.com/p/question/172825635703939917||target="blank"]]
29 29  
30 30  == **Key Takeaways** ==
31 31  
... ... @@ -35,7 +35,7 @@
35 35  * If you have feedback or ideas for us, talk to the Platypus
36 36  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
37 37  * Clear your browser cache (Ctrl + Shift + Del)
38 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.238 - Preparation Paradise.WebHome||target="blank"]]
70 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.229 - Xpath Alignment.WebHome||target="blank"]]
39 39  * Start thinking about how the license tracker can aid your development
40 40  * Start thinking about major, minor, and patch
41 41  * Keep making great integrations