...
Panel |
---|
borderColor | purple |
---|
bgColor | white |
---|
titleColor | black |
---|
borderWidth | 1 |
---|
titleBGColor | #ddccff |
---|
borderStyle | solid |
---|
title | New feature |
---|
|
New Import Feature in Joget DX 8 version 8.1 onwards.- Joget DX 8 version 8.1 onwards support zipping folder like `crm_1` from app_src folder and use it to import app.
- This feature will support the use of zipped files from app_src folder to be imported into Joget DX.
- Steps to use this feature
- Go to
installation folder/wflow/app_src/<app name> eg: crm - Zip one of the app's version folder eg:
crm_1
- A new app version for the
crm app should be created. (Version 2) (new app if does not exist)
|
Import App Troubleshooting
There will be cases where you will get an error when importing an app to a new Joget DX Environment.
Image Added
Figure 6: Import Error
These are potential errors that could cause the error and how to fix it.
- java.sql.SQLException: Column 'id' cannot be null in Joget log.
- The error was caused by a missing id in the appDefinition.xml of the exported app.
- To fix this, go to the exported app .jwa file and open appDefinition.xml, this requires you to search id one-by-one to check if there's an id with no value.Image Added
- In the figure above, in line 1441, an Environment Variable id's value is not set. In this sample case, we will set the id with "test".
- Image Added
- Replace the "<id>test</id>" with the correctly declared one from your original app to avoid possible conflict / mismatch, save it in your .jwa file and test the app import again.
- The error should not re-occur.
App Configuration Management
...
Caution: If the app's transaction records are huge, export and import of the app could take a long time and may cause a performance issue for other Joget users. If you have a lot of data records, it is better to use a database utility to perform a database SQLdump.
Figure 7: Exporting An App
Related Documentation
...