Skip to Content
Last modified by Erik Bakker on 2025/02/25 16:09
From version 3.1
edited by Erik Bakker
on 2022/06/13 14:36
Change comment: There is no comment for this version
To version 2.4
edited by Erik Bakker
on 2022/06/13 14:33
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -eMagiz Mendix Connector 4.2.0 -> 5.0.0
1 +migration-path-emagiz-mendix-connector-4.2.0-to-5.0.0
Content
... ... @@ -1,5 +1,13 @@
1 -{{container}}{{container layoutStyle="columns"}}(((
1 +{{html wiki="true"}}
2 +<div class="ez-academy">
3 + <div class="ez-academy_body">
2 2  
5 +<div class="doc">
6 +
7 +
8 +
9 += Migration Path * eMagiz Mendix Connector 4.2.0 -> 5.0.0 =
10 +
3 3  Below you will find a document describing the migration path to upgrade your eMagiz Mendix Connector from version 4.2.0 to 5.0.0.
4 4  In case you want to implement an eMagiz Mendix Connector in a new Mendix project, ensure that you retrieve the latest version from the Mendix Marketplace as that will guarantee that the latest version is immediately chosen so you can implement it.
5 5  
... ... @@ -21,8 +21,10 @@
21 21  * The configuration will be downloaded automatically
22 22  * The flow overview (XML configuration overview) has returned
23 23  
24 -== 3. eMagiz Mendix Connector 4.2.0 -> 5.0.0 ==
25 25  
33 +
34 +== 3. Migration Path * eMagiz Mendix Connector 4.2.0 -> 5.0.0 ==
35 +
26 26  Below you will find a document describing the migration path to upgrade your eMagiz Mendix Connector from version 4.2.0 to 5.0.0.
27 27  In case you want to implement an eMagiz Mendix Connector in a new Mendix project, ensure that you retrieve the latest version from the Mendix Marketplace as that will guarantee that the latest version is immediately chosen so you can implement it.
28 28  
... ... @@ -44,8 +44,8 @@
44 44  
45 45  * The after startup microflow within the module has been renamed. Ensure that you refer to the new and correct after startup microflow within your own after startup microflow or directly from the Project settings. Note that the after startup microflow is now called AfterStartup
46 46  * The register microflow is not needed anymore in version 5.0.0. To make the solution work in 5.0.0, you need to change the exit flows in the portal to define the correct information.
47 - ** For asynchronous exits you can check out this [microlearning](../microlearning/intermediate-mendix-connectivity-calling-an-asynchronous-webservice-in-mendix.md) on how to exactly configure the exit flow correctly
48 - ** For synchronous exits you can check out this [microlearning](../microlearning/intermediate-mendix-connectivity-calling-a-synchronous-webservice-in-mendix.md) on how to exactly configure the exit flow correctly
57 + * For asynchronous exits you can check out this [microlearning](../microlearning/intermediate-mendix-connectivity-calling-an-asynchronous-webservice-in-mendix.md) on how to exactly configure the exit flow correctly
58 + * For synchronous exits you can check out this [microlearning](../microlearning/intermediate-mendix-connectivity-calling-a-synchronous-webservice-in-mendix.md) on how to exactly configure the exit flow correctly
49 49  * The XML Configuration overview has returned (XmlConfiguration_Overview). So make sure that the relevant role(s) can view this overview in case a migration needs to be performed or a manual download is needed.
50 50  
51 51  ===== Practice =====
... ... @@ -62,4 +62,4 @@
62 62  </div>
63 63  </div>
64 64  
65 -)))((({{toc/}}))){{/container}}{{/container}}
75 +{{/html}}