Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 724.1
edited by Carlijn Kokkeler
on 2024/09/25 16:55
Change comment: There is no comment for this version
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 -230 - Petite Peaks
1 +239 - Modern Talking
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -3,33 +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, we have some small improvements and bug fixes. First of all, the pop-up when adding an integration to an existing API in Design has been improved. Secondly, queues with illegal characters will not cause errors anymore. Thirdly, an issue has been fixed where a deployment step would get blocked. Please find out all below!
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 during this deployment, Kafka metrics will be unavailable and lost for the duration of the deployment. After the deployment is complete, Kafka metrics will resume and be reflected in the monitoring graphs, but no metrics will be present corresponding to the deployment period.{{/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 -//__Add integration__//
12 -When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
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 -[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]]
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}}
15 15  
16 -//__Failover__//
17 -We have introduced a new failover feature, allowing you to enable failover on messaging flows with minimal setup required. Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more on our documentation page (LINK).
18 -
24 +== **Minor Changes** ==
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 +
19 19  == **Bug Fixes** ==
20 -//__Queues with illegal characters__//
21 -Existing queues with illegal characters will not generate errors anymore. They can now be searched, deleted, explored, wiretapped, etc. in Manage -> Explore.
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.
22 22  
23 -//__Blocked deployment step__//
24 -We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
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.
25 25  
26 26  == **Fancy Forum Answers** ==
27 27  
28 28  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:
29 29  
30 -* [[Error being stamped on the wrong "last flow">>https://my.emagiz.com/p/question/172825635703952578||target="blank"]]
31 -* [[AMQP broker hostname for JMS-host instead of IP>>https://my.emagiz.com/p/question/172825635703965465||target="blank"]]
32 -* [[Calling a soap webservice that is secured with a client certificate>>https://my.emagiz.com/p/question/172825635703965402||target="blank"]]
40 +* [[value comparison on substring>>https://my.emagiz.com/p/question/172825635704067769||target="blank"]]
33 33  
34 34  == **Key Takeaways** ==
35 35  
... ... @@ -39,7 +39,7 @@
39 39  * If you have feedback or ideas for us, talk to the Platypus
40 40  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
41 41  * Clear your browser cache (Ctrl + Shift + Del)
42 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.230 - Petite Peaks.WebHome||target="blank"]]
50 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.239 - Modern Talking.WebHome||target="blank"]]
43 43  * Start thinking about how the license tracker can aid your development
44 44  * Start thinking about major, minor, and patch
45 45  * Keep making great integrations