Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 859.1
edited by Erik Bakker
on 2025/02/25 08:58
Change comment: There is no comment for this version
To version 782.1
edited by Carlijn Kokkeler
on 2024/11/18 10:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -239 - Modern Talking
1 +234 - Alert Adventures
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -3,41 +3,52 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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.
6 +**Hi there, eMagiz developers!** In this release, our new error alerting will be available! Please find out more about it here (LINK). Apart from this, .
7 7  
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:
8 +== **Feedback Items** ==
9 +//__Error alerting__//
10 +Alerting for message queues 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"]] a couple of months ago.
11 11  
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"]]
12 +//__Failover__//
13 +Several improvements for our failover functionality have been done:
14 +* We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.
15 + [[image:Main.Images.Release Blog.WebHome@release-233-balance-failover.png]]
16 +* We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment. This action can be found in Deploy Architecture, when right clicking on the white canvas.
17 +* We have added a visualization of connector systems that are pending a failover enable or disable in Deploy Architecture. Besides that, you will also see this shown in the pending changes list when you apply your changes to the environment.
18 + [[image:Main.Images.Release Blog.WebHome@release-233-failover-system.png]]
14 14  
15 -{{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}}
20 +//__Empty status__//
21 +The status of error messages can now be reset to empty.
22 +[[image:Main.Images.Release Blog.WebHome@release-233-reset-status.png]]
23 23  
24 -== **Minor Changes** ==
24 +//__SMB session factory__//
25 +We have added two additional configuration options to the SMB session factory support object.
26 +* Connect as guest: We have added the option to toggle whether the session factory should attempt to connect as a guest if the login attempt with the provided username and password is rejected.
27 +* Force SMB version 2: We have added the option to enforce the usage of SMB version 2. This effectively disables backwards-compatible version negotiation.
25 25  
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.
28 -
29 29  == **Bug Fixes** ==
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.
30 +//__Support object alert__//
31 +If a component misses a support object, an alert is now shown in the Flow Designer, displaying which support object is missing.
32 32  
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.
33 +[[image:Main.Images.Release Blog.WebHome@release-233-support-object-alert.png]]
35 35  
35 +//__XML to flat file__//
36 +The XML to flat file and flat file to XML transformers have been restyled, such that they are similar to all other components.
37 +
38 +//__Queue browser__//
39 +When clicking the queue browser button, the user will not be redirected to the home page anymore.
40 +
41 +//__Edit freeze__//
42 +We fixed an issue where the browser page would get frozen when editing a flow component.
43 +
44 +//__Release version__//
45 +The version number of releases that have been activated, cannot be reused anymore for new releases. Note that this check only applies to release version numbers that are activated since this Release 233.
46 +
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  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:
39 39  
40 -* [[value comparison on substring>>https://my.emagiz.com/p/question/172825635704067769||target="blank"]]
51 +* [[JSON-TO-JSON java.lang.NumberFormatException in string field>>https://my.emagiz.com/p/question/172825635703991104||target="blank"]]
41 41  
42 42  == **Key Takeaways** ==
43 43  
... ... @@ -47,7 +47,7 @@
47 47  * If you have feedback or ideas for us, talk to the Platypus
48 48  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
49 49  * Clear your browser cache (Ctrl + Shift + Del)
50 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.239 - Modern Talking.WebHome||target="blank"]]
61 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.233 - Policy Polish.WebHome||target="blank"]]
51 51  * Start thinking about how the license tracker can aid your development
52 52  * Start thinking about major, minor, and patch
53 53  * Keep making great integrations