Changes for page 240 - Spring Cleaning
Last modified by Erik Bakker on 2025/03/10 10:00
From version 861.1
edited by Erik Bakker
on 2025/02/25 08:58
on 2025/02/25 08:58
Change comment:
There is no comment for this version
To version 726.1
edited by Carlijn Kokkeler
on 2024/10/07 11:24
on 2024/10/07 11:24
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -23 9- ModernTalking1 +231 - Microscopic Madness - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -3,41 +3,26 @@ 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!** 7 7 8 -== ** NeweMagiz Mendix Connector** ==9 - 10 - This releaseintroduces the new eMagiz MendixConnector to our platform. This means that when you addaewMendixsystemto anyeMagiz modelthat runson thecurrent-generation architecture (new and existing),eMagiz will configure thisMendix system to act as the new eMagiz Mendix Connector. We have createdthis eMagiz MendixConnector to simplifythe configuration and management of the eMagiz Mendix Connector, to enhance the stability of theonnection between yourMendixapp and youreMagiz model, and to simplify problemdetection ifsomething goeswrong.As a result, the whole way of working with the eMagiz Mendix Connectorhas changed bothinMendix and in eMagiz. This meansthat lesscommunication isneeded duringthe development of integrations with Mendix,smootheningthe development processand that thefunctionality within Mendixresembles how weun all our runtimesin the current-generation architecture. For moreinformation, please check out these courses:8 +== **Feedback Items** == 9 +//__Unused properties__// 10 +We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. 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 Level.Mendix Connectivity||target="blank"]] 12 +[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.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}} 23 23 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 - 29 29 == **Bug Fixes** == 30 -//__ Auto-creationconnector infra SOAP hostedendpoint__//31 -We havechangedtheauto-creationbehaviorforSOAP web serviceystems.This means that we nowproperlycreatetwosupportobjects, PayloadRoot EndpointMapping,and SOAP Web serviceinterceptors,toavoiderrors whenopeningtheentryflow forhe firsttime.16 +//__Unused properties__// 17 +We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. 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. 35 - 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"]] 23 +* [[Error being stamped on the wrong "last flow">>https://my.emagiz.com/p/question/172825635703952578||target="blank"]] 24 +* [[AMQP broker hostname for JMS-host instead of IP>>https://my.emagiz.com/p/question/172825635703965465||target="blank"]] 25 +* [[Calling a soap webservice that is secured with a client certificate>>https://my.emagiz.com/p/question/172825635703965402||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.23 9-ModernTalking.WebHome||target="blank"]]35 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.230 - Petite Peaks.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