You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/appstore/use-content/platform-supported-content/modules/genai/mendix-cloud-genai/Mx GenAI Connector.md
+15-15
Original file line number
Diff line number
Diff line change
@@ -89,21 +89,6 @@ Follow the steps below to get started:
89
89
* Add the `Configuration_Overview` page (**USE_ME** > **Configuration**) to your navigation, or add the `Snippet_Configuration` to a page that is already part of your navigation. Alternatively, you can register your key by using the `Configuration_RegisterByString` microflow.
90
90
* Complete the runtime setup of Mendix Cloud GenAI configuration by navigating to the page through the microflow mentioned above. Import a key generated in the [portal](https://genai.home.mendix.com) or provided to you and click **Test Key** to validate its functionality.
91
91
92
-
## Migrating From Add-on Module to App Module
93
-
94
-
Since the module has been changed from an add-on to an app module, updating it via the marketplace will require a migration to ensure it works properly with your application.
95
-
96
-
To do this, follow the steps below:
97
-
98
-
1. Back up your data — either as a full database backup or by exporting individual components:
99
-
100
-
* Keys for MxCloud GenAI Resource Packs can be reimported later.
101
-
* Incoming associations to the protected module’s entities will be deleted.
102
-
2. Delete the add-on module: MxGenAIConnector.
103
-
3. Download the updated module from the Marketplace. Note that the module is now listed under the **Marketplace modules** category in the **App Explorer**.
104
-
4. Test your application locally to ensure everything functions as expected.
105
-
5. Restore any lost data in deployed environments. Typically, keys and incoming associations to the protected module need to be reset.
@@ -294,6 +279,21 @@ To check your JDK version and update it if necessary, follow these steps:
294
279
1. You might get an error saying `FAILURE: Build failed with an exception. The supplied javaHome seems to be invalid. I cannot find the java executable.` In this case, verify that you have selected the correct JDK directory containing the updated JDK version.
295
280
2. You may also need to update Gradle. To do this, go to **Edit** > **Preferences** > **Deployment** > **Gradle directory**. Click **Browse** and select the appropriate Gradle version from the Mendix folder. For Mendix 10.10 and above, use Gradle 8.5. For Mendix 10 versions below 10.10, use Gradle 7.6.3. Then save your settings by clicking **OK**.
296
281
3. Rerun the project.
282
+
283
+
### Migrating From Add-on Module to App Module
284
+
285
+
Since the module has been changed from an add-on to an app module, updating it via the marketplace will require a migration to ensure it works properly with your application.
286
+
287
+
To do this, follow the steps below:
288
+
289
+
1. Back up your data — either as a full database backup or by exporting individual components:
290
+
291
+
* Keys for MxCloud GenAI Resource Packs can be reimported later.
292
+
* Incoming associations to the protected module’s entities will be deleted.
293
+
2. Delete the add-on module: MxGenAIConnector.
294
+
3. Download the updated module from the Marketplace. Note that the module is now listed under the **Marketplace modules** category in the **App Explorer**.
295
+
4. Test your application locally to ensure everything functions as expected.
296
+
5. Restore any lost data in deployed environments. Typically, keys and incoming associations to the protected module need to be reset.
0 commit comments