...
| Info | ||
|---|---|---|
| ||
|
These are the instances when process version will change.
Creation of new version from existing app version.
The current app version selected will be cloned (process, form, datalist, userview and properties including default plugin properties, message bundles, and environment variables ) over to the next available version number.- Import of App
Important Notes
...
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.
Coverage of Process Version
...
In the Monitor Apps section, one can navigate to the process instance view and click on the Process Name link to lead to the designer console of the app version. From the screenshot below, this particular instance is of process version 6 1 and it belongs to app version 3.
Important Notes
...
For example, in the table and screenshot below, 123_hr_expenseexpenseclaim_process1 will show forms mapped according to its activity mappings under app version 1 regardless of whether app version 1 or 2 is published or not.
On the other hand, 124_hr_expenseexpenseclaim_process1 will show forms from app version 2.
| App Version | Process Version | Action Taken |
|---|---|---|
| 1 | 1 | Started a process instance 123_hr_expenseexpenseclaim_process1 |
| 2 | 2 | Started a process instance 124_hr_expenseexpenseclaim_process1 |
By accessing the form record created by a process instance of different app version, you may not be seeing the exact form used during the process instance flow process. As such, you can clone the form from the originating app version into the current app version that you are working on so that you can then gain access to the very form used during the process flow.
...
| Info | |||||
|---|---|---|---|---|---|
| |||||
The following code can be used in Bean Shell in:-
|