| Table of Contents |
|---|
Upgrading From An Existing Joget v5 or v6
...
Folders
The following are the changes you need to run Joget DX if you are upgrading from Joget v6 folders:
...
The upgrade steps are as follows if you are upgrade upgrading to Joget DX in v5 or v6 folders:
- Backup your Joget v6 files and v6 database.
- Make the above changes in startup script and Glowroot folders.
- Delete ".\apache-tomcat-8.5.41\work\*" folder.
- Delete ".\apache-tomcat-8.5.41\webapps\jw" folder and jw.war file.
- Copy Joget DX "jw.war" file into ".\apache-tomcat-8.5.41\webapps\".
- Edit ".\wflow\app_datasource-default.properties" to point to your existing v6 database.
- Start Joget Apache Tomcat and monitor the joget.log.
...
Lastly, you can download and install new plugins specially for Joget DX from https://archives.joget.org/addons/ to try out.
Important Note About Joget DX New Process ID Using UUID
One of the top requested features for Joget DX was to change the process id to use UUID for data security. Using UUID makes the URL unguessable, thus protecting unauthorized access to the process records in a Form. With the old processId of "[seq#]_appid_process1", it was easy for users to access other process records by just incrementing the process seq number in the browser URL and viewing the records not belonging to them.
Here is a process id related checklist when migrating apps from v5 or v6 to Joget DX:
- In Beanshell, have two separate variables to store the @processId@ and @recordId@ at the top of your code:
- RecordId contains the UUID primary key (id). This is used when you have to query or update the process database table using SQL syntax.
- ProcessId is used when you are using Joget methods to manipulate the process data.
- See an example app using RecordId in BeanShell code at "Multiple Approval App For Joget DX":https://dev.joget.org/community/display/DX7/Demonstration+Multiple+Approval+App+For+Joget+DX .
- Similarly, if you use process Database Update Tool where SQL is included, ensure you replace any "where id = '#assignment.processId#' " with "where id = '#process.recordId#' ".
- If your forms (that are used in processes) has subform or Ajax subform with references to the parent form id stored in a hidden field, ensure you initialize the hidden field with the "#process.recordId#" hash and not the "#process.processId#".
The apps that has zero BeanShell or SQL in JDBC calls should have no issues running on Joget DX. Nevertheless, please thoroughly test all older apps if you are migrating them to Joget DX.
Related References:
- General Settings > System Administration Settings > Run Process Primary Key option.
- Hash Variable > Workflow Process Hash Variable
Perform Cursory Test
We highly recommend that you spend some time to perform a cursory test on the Joget apps that you have created based on older versions. A quick test can quickly determine if your app is fully compatible with Joget DX. Be sure to check the server log also as it would generate error logs on possible missing/incompatible plugins or other issues.
...