Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 816.1
edited by Carlijn Kokkeler
on 2024/12/02 09:51
Change comment: There is no comment for this version
To version 862.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 -235 - TBD
1 +239 - Modern Talking
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -3,59 +3,41 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
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 -//__Error alerting__//
12 -Error alerting has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, following our queue alerting design that has been [[released>>doc:Main.Release Information.Release Blogs.226 - Alerting Alchemy.WebHome||target="blank"]] several months ago. The new error alerting feature allows you to trigger an alert on **all** incoming errors, or choose to trigger when **specific filters** on the error’s headers, message or class have been met. Furthermore, you can select the specific runtime the error 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 Level.Mendix connectivity||target="blank"]]
13 13  
14 14  {{info}}
15 -Please take into consideration the following migration actions:
16 -* All existing error 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., "Error Trigger 1").
22 -** **Users are advised to review and update these names to appropriately reflect each trigger's purpose**.
23 -* If an error message alert trigger has the following specific configuration, its trigger conditions will be migrated such that alerts are triggered for **all** incoming error messages:
24 -** "Check header" is disabled.
25 -** "Check error message" is enabled.
26 -** The "Error message contains" field includes only a single character.
27 -* The new feature introduces duplicate detection when saving an individual error trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate error alerts.{{/info}}
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]].
22 +{{/info}}
28 28  
29 -{{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 queue-related triggers. These triggers can be found under the ‘Other’ tab on the alert triggers page.{{/warning}}
24 +== **Minor Changes** ==
30 30  
31 -{{warning}}Please check out our [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-error-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.
32 32  
33 -//__Attribute selection__//
34 -When selecting an attribute in a datamodel, the selected attribute and associated entity are now highlighted.
35 -
36 -[[image:Main.Images.Release Blog.WebHome@release-234-cdm.png]]
37 -
38 -//__Runtime image__//
39 -We have removed some deprecated components from our runtime image.
40 -* TCP support object 'Byte array text length header (de)serializer'
41 -* Mikrotik service activator
42 -
43 -Please find out more [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]].
44 -
45 -{{warning}}We recommend evaluating custom groovy scripts and SpEL expressions to ensure that they do not rely on functionality that may have been removed due to one of the library removals.
46 -* Calls to com.emagiz.util.Assert can be replaced with org.springframework.util.Assert
47 -* Calls to com.emagiz.util.StringUtils can be replaced with org.springframework.util.StringUtils
48 -* Calls to com.emagiz.util.CollectionUtils can be replaced with org.springframework.util.CollectionUtils{{/warning}}
49 -
50 50  == **Bug Fixes** ==
51 -//__Failover container__//
52 -The failover container will now be shown correctly.
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.
53 53  
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.
35 +
54 54  == **Fancy Forum Answers** ==
55 55  
56 56  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:
57 57  
58 -* [[H2 database following a queue channel without message store>>https://my.emagiz.com/p/question/172825635704003822||target="blank"]]
40 +* [[value comparison on substring>>https://my.emagiz.com/p/question/172825635704067769||target="blank"]]
59 59  
60 60  == **Key Takeaways** ==
61 61  
... ... @@ -65,7 +65,7 @@
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 66  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.234 - Alert Adventures.WebHome||target="blank"]]
50 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.239 - Modern Talking.WebHome||target="blank"]]
69 69  * Start thinking about how the license tracker can aid your development
70 70  * Start thinking about major, minor, and patch
71 71  * Keep making great integrations