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 859.1
edited by Erik Bakker
on 2025/02/25 08:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -236 - Another Agent
1 +239 - Modern Talking
Parent
... ... @@ -1,1 +1,1 @@
1 -WebHome
1 +Main.Release Information.Release Blogs.WebHome
Content
... ... @@ -3,65 +3,41 @@
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 testing the eMagiz Mendix Connector and solving internal feedback on the process and the connector itself. With that behind us, we are ready to launch the new eMagiz Mendix Connector in our community. With this release, we will make it available for all new Mendix systems in models running on the current-generation architecture. In a future release, we will bring a migration wizard aiding a simple and smooth migration to the new eMagiz Mendix Connector. On top of that, we have some minor updates to improve the quality of the 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 eMagiz Mendix Connector** ==
9 +
10 +This release introduces the new eMagiz Mendix Connector to our platform. This means that when you add a new Mendix system to any eMagiz model that runs on the current-generation architecture (new and existing), eMagiz will configure this Mendix system to act as the new eMagiz Mendix Connector. We have created this eMagiz Mendix Connector to simplify the configuration and management of the eMagiz Mendix Connector, to enhance the stability of the connection between your Mendix app and your eMagiz model, and to simplify problem detection if something goes wrong. As a result, the whole way of working with the eMagiz Mendix Connector has changed both in Mendix and in eMagiz. This means that less communication is needed during the development of integrations with Mendix, smoothening the development process and that the functionality within Mendix resembles how we run all our runtimes in the current-generation architecture. For more information, please check out these courses:
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.
12 +* [[eMagiz Mendix Connector - Introduction>>Main.eMagiz Academy.Microlearnings.Novice.Mendix Connectivity||target="blank"]]
13 +* [[eMagiz Mendix Connector - Detailed Configuration>>>Main.eMagiz Academy.Microlearnings.Intermediate.Mendix Connectivity||target="blank"]]
13 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.
16 +* **Before using this, please take into consideration the following**:
17 +* Your Mendix app needs to run on **Java 17**
18 +* Your Mendix app needs to run on version 9.24.25 or higher
19 +** We have tested and support the LTS and MTS versions of Mendix with this eMagiz Mendix Connector
20 +* Share the activation key after the integrations are added to a release that is **activated**.
21 +* Should problems arise while implementing this, please contact us via 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}}
24 +== **Minor Changes** ==
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}}
26 +//__Added View option on support objects__//
27 +We have added a view option that allows you to browse the list of support objects when you are **not** in "Start Editing" mode. This makes determining whether particular support objects exist and which ones you need before diving into building a flow much easier.
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.
30 +//__Auto-creation connector infra SOAP hosted endpoint__//
31 +We have changed the auto-creation behavior for SOAP web service systems. This means that we now properly create two support objects, Payload Root Endpoint Mapping, and SOAP Web service interceptors, to avoid errors when opening the entry flow for the first time.
48 48  
49 -[[image:Main.Images.Release Blog.WebHome@release-235-resources.png]]
33 +//__Manage Dashboard Error__//
34 +We now prevent errors in the Manage Dashboard overview when an error occurs in a component with an id that does not follow the [id].[system].[flow] convention or when that value is longer than expected.
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"]]
40 +* [[value comparison on substring>>https://my.emagiz.com/p/question/172825635704067769||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"]]
50 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.239 - Modern Talking.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