Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 841.1
edited by Carlijn Kokkeler
on 2024/12/04 14:06
Change comment: There is no comment for this version
To version 849.1
edited by Erik Bakker
on 2025/01/27 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -235 - Last Log
1 +237 - Fabulous Flow
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.Release Information.Release Blogs.WebHome
1 +WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -3,65 +3,66 @@
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, 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 Design 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.
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 +== **Runtime Memory Update (Windows Machines Only)** ==
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.
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 -* **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.
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 +[[image:Main.Images.Release Blog.WebHome@release-237-manual-override-memory-on-prem.png]]
18 +* Should you encounter any problems, please get in touch with our [[support department>>mailto:support@emagiz.com]]!
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}}
21 +== **Certificate Update** ==
22 +
23 +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]]!
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}}
25 +== **Minor changes** ==
26 +//__SMB component improvements__//
27 +Validation feedback and help text updates for the following components: SMB outbound gateway, SMB session factory, and SMB composite list filter.
28 +
29 +//__EDI Components - Styling Update__//
30 +The styling of the following components has been updated.
30 30  
31 -//__Tooltip alerting__//
32 -We have improved the visibility of titles of larger columns in the new Alerting page.
32 +* XML to EDI transformer
33 +* EDI to XML transformer
34 +* XML to UN/EDIFACT transformer
35 +* UN/EDIFACT to XML transformer
36 +
37 +//__Manage Statistics UI Update__//
38 +We have updated our monitoring graph technology, including minor styling updates across the different current-generation monitoring dashboards.
33 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.
40 +[[image:Main.Images.Release Blog.WebHome@release-237-ui-changes-manage-statistics.png]]
38 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.
43 +//__Import from Store - Design__//
44 +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]]
46 +//__Removing integrations from Create__//
47 +When the last integration is removed from a system in create, the container infra flows are also removed from the create phase release.
48 +
49 +//__Flow Test Logging - Navigation__//
50 +We have improved the navigation of the logging shown on the flow test level in Create.
51 +
52 +//__Create Phase - Synchronization process updated__//
53 +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.
54 +
55 +//__Update on search functionality in "Start/Stop flows" overview__//
56 +Searching in the start/stop flows overview and the queue browser can now be done from any page in the overviews.
57 +
58 +//__Windows line break fix__//
59 +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.
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"]]
65 +* [[Issue with importing XSD into eMagiz, replacing '=ref' references>>https://my.emagiz.com/p/question/172825635704054981||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"]]
75 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.237 - Fabulous Flow.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