These are the instances where versioning is involved with:-
| Component | Application Version | Process Version |
|---|---|---|
| Process | Yes | Yes |
| Form | Yes | |
| Datalist | Yes | |
| Userview | Yes | |
| App Properties | Yes |
Each app version may hold more than one process version but one can only start a process instance of the current latest process version the app version is holding. |
Inside an app version, it contains process design but process design has its own set of versioning called process version.
Under each process in processes tab, click on "Show Additional Info" link to reveal the Process Definition ID. You can find the process version in between the 2 hashes.
| Component | Application Version | Process Version |
|---|---|---|
| Process | Yes | Yes |
| Form | Yes | |
| Datalist | Yes | |
| Userview | Yes | |
| App Properties | Yes |
These are the instances when process version will change.
Process design update via deployment from Process Builder or by uploading .xpdl definition file.
When one of the above takes place, Joget Workflow will find the next available process version and assign to it.
| App Version | Process Version | Action Taken |
|---|---|---|
| 1 | 1 | |
| 1 | 1 -> 2 | Process design update |
For example, in the table above, upon process design update via process builder, the process version will now turn to 2 from 1.
In some cases, one may perform a process design update on older app version even though there's a newer app version in place as illustrated in the table below.
| App Version | Process Version | Action Taken |
|---|---|---|
| 1 | 1 | |
| 1 | 1 -> 3 | Process design update |
| 2 | 2 |
In this case, app version 1 will now hold process version 3 and not 2.
Each process version belongs to only one app version. |