Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 852.2
edited by Erik Bakker
on 2025/02/10 09:16
Change comment: Update document after refactoring.
To version 714.2
edited by Carlijn Kokkeler
on 2024/09/23 11:36
Change comment: Update document after refactoring.

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,68 +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 improving the flow back and forth between the various phases in eMagiz by solving several feedback items related to Design, Create, and Deploy and the interaction between these three phases. We have also improved the memory calculation for all runtimes running on a Windows machine. Moreover, we have updated the styling of our graphs in the Manage phase.
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 -== **Runtime Memory Update (Windows Machines Only)** - Reverted ==
9 -
10 -As part of this release, we will update the underlying memory calculations for all runtimes running on a Windows machine. Consequently, these runtimes will have a slightly increased memory footprint on your machine.
8 +== **Deployment Plan Improvements** ==
11 11  
12 -{{info}}
13 -* **Please take into consideration the following**:
14 -* The new memory settings will take effect on the **first** deployment you will execute after **this** release.
15 -** When executing this deployment, you will see a pop-up notifying you of the **new** used memory. Here, you can also see whether the new **used** memory exceeds the available memory.
16 -* Should the **used** memory increase the available memory (as determined by eMagiz), you can manually override this setting in Design -> Architecture under the "Edit machine" option by filling in the memory field.
17 -
18 -[[image:Main.Images.Release Blog.WebHome@release-237-manual-override-memory-on-prem.png]]
10 +//__Monitoring Trigger - Improvements__//
19 19  
20 -* Should you encounter any problems, please get in touch with our [[support department>>mailto:support@emagiz.com]]!
21 -{{/info}}
12 +* For the step type "Monitoring Trigger," we have re-introduced the "Enable" option.
22 22  
23 -== **Certificate Update** ==
24 -
25 -As announced on our [[status page>>https://status.emagiz.com/incidents/4wb8tt5x9v95||target="blank"]], we will update our emagizcloud certificate as part of this release. Should you encounter any problems, please get in touch with our [[support department>>mailto:support@emagiz.com]]!
14 +[[image:Main.Images.Release Blog.WebHome@release-229-enable-option.png]]
26 26  
27 -== **Minor changes** ==
28 -//__SMB component improvements__//
29 -Validation feedback and help text updates for the following components: SMB outbound gateway, SMB session factory, and SMB composite list filter.
30 -
31 -//__EDI Components - Styling Update__//
32 -The styling of the following components has been updated.
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.
33 33  
34 -* XML to EDI transformer
35 -* EDI to XML transformer
36 -* XML to UN/EDIFACT transformer
37 -* UN/EDIFACT to XML transformer
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.
38 38  
39 -//__Manage Statistics UI Update__//
40 -We have updated our monitoring graph technology, including minor styling updates across the different current-generation monitoring dashboards.
27 +In the coming weeks, we will actively monitor eMagiz models to see to what extent this advice has been implemented.{{/warning}}
41 41  
42 -[[image:Main.Images.Release Blog.WebHome@release-237-ui-changes-manage-statistics.png]]
29 +//__Default Plan - Improvements__//
43 43  
44 -== **Bug Fixes** ==
45 -//__Import from Store - Design__//
46 -The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. This is to avoid broken transformations within the Create phase of eMagiz.
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.
47 47  
48 -//__Removing integrations from Create__//
49 -When the last integration is removed from a system in create, the container infra flows are also removed from the create phase release.
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]]
50 50  
51 -//__Flow Test Logging - Navigation__//
52 -We have improved the navigation of the logging shown on the flow test level in Create.
53 -
54 -//__Create Phase - Synchronization process updated__//
55 -The flow version for the Create release on the Deploy phase is synced for that specific flow automatically when the user resets the flow in the Create phase.
56 -
57 -//__Update on search functionality in "Start/Stop flows" overview__//
58 -Searching in the start/stop flows overview and the queue browser can now be done from any page in the overviews.
59 -
60 -//__Windows line break fix__//
61 -If the message in a log or error contained a Windows line break (\r\n), and a log or error alert was configured that matched it, an alert would be generated, but no email would be sent out.
48 +== **Bug Fixes** ==
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.
62 62  
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 +
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  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:
66 66  
67 -* [[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"]]
68 68  
69 69  == **Key Takeaways** ==
70 70  
... ... @@ -74,7 +74,7 @@
74 74  * If you have feedback or ideas for us, talk to the Platypus
75 75  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76 76  * Clear your browser cache (Ctrl + Shift + Del)
77 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.237 - Fabulous Flow.WebHome||target="blank"]]
70 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.229 - Xpath Alignment.WebHome||target="blank"]]
78 78  * Start thinking about how the license tracker can aid your development
79 79  * Start thinking about major, minor, and patch
80 80  * Keep making great integrations