Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 846.1
edited by Erik Bakker
on 2025/01/13 15:09
Change comment: There is no comment for this version
To version 711.1
edited by Danniar Firdausy
on 2024/09/09 12:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -236 - Another Agent
1 +229 - XPath Alignment
Parent
... ... @@ -1,1 +1,1 @@
1 -WebHome
1 +Main.Release Information.Release Blogs.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -3,46 +3,51 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, our new environment template will be available! Please find out more about it [[here>>Main.Release Information.Cloud Templates||target="blank"]]. Moreover, we have addressed several key feedback points within our 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 -== **New Environment Templates** ==
9 -
10 -As announced on our [[status page>>https://status.emagiz.com/incidents/nc5jxhxtkvfg||target="blank"]] we will release a new environment template to our community. This environment template contains two significant changes on your environment of which the eMagiz agent is key. This agent is responsible for communicating between the various machines within your model (both on-premises and our cloud).
8 +== **Deployment Plan Improvements** ==
11 11  
12 -{{info}}
13 -* **Please take into consideration the following migration actions**:
14 -* You can use the [[(automatic) upgrade procedure>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.novice-emagiz-cloud-management-cloud-templates-explained||target="blank"]] as provided within the platform to update your environments to this new environment template.
15 -* Please ensure to update the environment template before the **February, 13th 2025**. We impose this deadline to avoid delays for subsequent updates to our infrastructure.
16 -* Should you encounter any problems please get in touch with our [[support department>>mailto:support@emagiz.com]]!
17 -{{/info}}
10 +//__Monitoring Trigger - Improvements__//
18 18  
19 -== **Minor changes** ==
20 -//__Help text improvements__//
21 -We have added updated the help texts on our (S)FTP components to better explain the local filter options. This to avoid confusion on the intention of those settings.
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.
22 22  
23 -//__Migration functionality removed__//
24 -We have removed Spring 6 related migration functionality from our portal given that all our customers are already migrated to the latest runtime image. As a result, this functionality became obsolete.
25 -
26 -//__Manage Alerting feedback__//
27 -We have slightly altered the user experience when configuring an alert in eMagiz with regards to the "Notification" part of the trigger. In here we now provide an explanation of what is going wrong when trying to activate the notifications **without** selecting **any** recipient. On top of that we now filter out **all** inactive users to ensure they cannot be selected as a recipient on a trigger.
27 +In the coming weeks, we will actively monitor eMagiz models to see to what extent this advice has been implemented.{{/warning}}
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@release-236-ux-improvement-notifications-alerting.png]]
30 30  
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 +** The existing "Disable" step is extended to define that eMagiz will automatically enable triggers after 60 minutes have passed.
34 +** The "Enable" step is added as the last step of your deployment plan.
35 +
36 +[[image:Main.Images.Release Blog.WebHome@release-229-new-default-plan.png]]
37 +
31 31  == **Bug Fixes** ==
32 -//__Import from Store - Design__//
33 -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.
39 +//__XPath Header Enricher - Help Text Improvement__//
40 +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.
34 34  
35 -//__Changing number of runtimes__//
36 -As a regular user, you can now increase and decrease the number of runtimes for existing Systems. This allows you to transfer them from Design Architecture to Deploy Architecture to be utilized in future deployments.
42 +//__XPath Configuration - Transformation__//
43 +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.
37 37  
38 38  == **Fancy Forum Answers** ==
39 39  
40 40  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:
41 41  
42 -* [[Encoding mode and REST template>>https://my.emagiz.com/p/question/172825635704029463||target="blank"]]
43 -* [[Empty header causes error in JDBC Outbound Gateway>>https://my.emagiz.com/p/question/172825635704029580||target="blank"]]
44 -* [[Handle special characters in Web service outbound gateway payload>>https://my.emagiz.com/p/question/172825635704029803||target="blank"]]
45 -* [[Invalid packet length>>https://my.emagiz.com/p/question/172825635704042225||target="blank"]]
49 +* [[Spaces handled differently in folder name after using SMB components for file connectivity>>https://my.emagiz.com/p/question/172825635703940018||target="blank"]]
50 +* [[How to process messages with invalid XML content like "&#x2">>https://my.emagiz.com/p/question/172825635703939917||target="blank"]]
46 46  
47 47  == **Key Takeaways** ==
48 48  
... ... @@ -52,7 +52,7 @@
52 52  * If you have feedback or ideas for us, talk to the Platypus
53 53  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
54 54  * Clear your browser cache (Ctrl + Shift + Del)
55 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.236 - Another Agent.WebHome||target="blank"]]
60 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.229 - Xpath Alignment.WebHome||target="blank"]]
56 56  * Start thinking about how the license tracker can aid your development
57 57  * Start thinking about major, minor, and patch
58 58  * Keep making great integrations