Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 841.2
edited by Erik Bakker
on 2025/01/13 09:29
Change comment: Update document after refactoring.
To version 844.1
edited by Erik Bakker
on 2025/01/13 10:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,65 +3,46 @@
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 log alerting will be available! Please find out more about it [[here>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-log-alerting.WebHome||target="blank"]]. Furthermore, we have implemented improvements for SMB and did some performance improvements. Lastly, from now on we no longer support our legacy Mendix connector (< version 4.x).
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.
7 7  
8 -{{info}}Please note that this is our last release of the year. Our next release will be on the 16th of January!{{/info}}
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).
9 9  
10 -== **Feedback Items** ==
11 -//__Log alerting__//
12 -We have added log message alert triggers to our new alerting stack for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. This new feature allows you to trigger on all incoming log messages with an error log-level, or trigger for log messages with a specific log message and log level (info, warning or error) combination. Furthermore, you can specify the specific runtime the log message originated from as one of the filters as well.
13 -
14 14  {{info}}
15 15  * **Please take into consideration the following migration actions**:
16 -* All existing log message alert triggers from the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture models will be automatically migrated to the new alerting feature.
17 -* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
18 -** The ‘Description’ field has been replaced by the new ‘Instructions’ field (note: the 'Description' field no longer exists).
19 -** The values of the old description field will be transferred into the instructions field
20 -* Additionally, a new field, ‘Name’, has been introduced for identification purposes. The ‘Name’ field will be included in email notifications when a trigger is activated.
21 -** This field will be automatically populated with a default name (e.g., "Log Trigger 1").
22 -** **Users are advised to review and update these names to appropriately reflect each trigger's purpose.**
23 -* A new filter for ‘Log level’ has also been added to the new Log alert triggers, which will be configured such that your existing triggers will generate an alert for **all** log types.
24 -* The new feature introduces duplicate detection when saving an individual log trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate log alerts.
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 your partner manager!
25 25  {{/info}}
26 26  
27 -{{warning}}To keep a better overview, we recommend you to remove your old dynamic triggers after the new error triggers are activated, these have already been disabled by our migration process. The same applies for your log-related triggers. These triggers can be found under the ‘Other’ tab on the alert triggers page.{{/warning}}
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.
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.
28 28  
29 -{{warning}}Please check out our [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-log-alerting.WebHome||target="blank"]] for an elaborate explanation of our new error alerting. {{/warning}}
29 +[[image:Main.Images.Release Blog.WebHome@release-236-ux-improvement-notifications-alerting.png]]
30 30  
31 -//__Tooltip alerting__//
32 -We have improved the visibility of titles of larger columns in the new Alerting page.
33 -
34 -//__SMB improvements__//
35 -Some configuration options have been added to our SMB connectors that will solidify the connections with a SMB share:
36 -* It is now possible to add a local filter to the SMB inbound channel adapter.
37 -* It is now possible to add a 'Request handler advice chain' to the SMB outbound channel adapter, SMB outbound gateway, FTP outbound gateway and SFTP outbound gateway.
38 -
39 -[[image:Main.Images.Release Blog.WebHome@release-235-local-filter.png]]
40 -[[image:Main.Images.Release Blog.WebHome@release-235-request-handler.png]]
41 -
42 -//__Mendix connector support__//
43 -We no longer support our legacy Mendix connector (< version 4.x).
44 -
45 45  == **Bug Fixes** ==
46 -//__Resource buttons__//
47 -The delete and download buttons in Resources have been re-aligned such that their positions are consistent when switching from view to edit mode.
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.
48 48  
49 -[[image:Main.Images.Release Blog.WebHome@release-235-resources.png]]
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.
50 50  
51 -//__Performance improvement__//
52 -The performance of selecting a runtime when editing properties in Deploy has been improved.
53 -
54 -//__Flowtest errors__//
55 -The error that is sometimes thrown while switching between traces in flowtester is fixed.
56 -
57 57  == **Fancy Forum Answers** ==
58 58  
59 59  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:
60 60  
61 -* [[Access a WSDL in your browser>>https://my.emagiz.com/p/question/172825635704016587||target="blank"]]
62 -* [[Operation is not present in wsdl>>https://my.emagiz.com/p/question/172825635704016691||target="blank"]]
63 -* [[Code Mappings on Gen3 error during restart ISPN000323>>https://my.emagiz.com/p/question/172825635704016854||target="blank"]]
64 -* [[How to add Basic Authentication on a soap webservice?>>https://my.emagiz.com/p/question/172825635704017021||target="blank"]]
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"]]
65 65  
66 66  == **Key Takeaways** ==
67 67  
... ... @@ -71,7 +71,7 @@
71 71  * If you have feedback or ideas for us, talk to the Platypus
72 72  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
73 73  * Clear your browser cache (Ctrl + Shift + Del)
74 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.235 - Last Log.WebHome||target="blank"]]
55 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.236 - Another Agent.WebHome||target="blank"]]
75 75  * Start thinking about how the license tracker can aid your development
76 76  * Start thinking about major, minor, and patch
77 77  * Keep making great integrations