...
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
...
| Info | ||
|---|---|---|
| ||
Each process version belongs to only one app version. |
Determine current process version
...
In this case, app version 1 will now hold process version 3 and not 2.
Important Notes
- One will always start a new process instance using the latest process version of the current published version.
By updating the process design in the same app version: all existing running process instances in the same app version will automatically be updated
...
to the new process flow in the background. Do not perform this unless it is absolutely necessary in a production server.
Warning title Do not repetitively update process design in a short time Process migration will takes place once process design is changed. Repetitive process change deployment will disrupt existing process instances migration in the background.
By updating the process design in the same app version: all existing running process instances in the same app version will automatically be updated to the new process flow in the background. Do not perform this unless it is absolutely necessary in a production server.
After you update the process design, do remember to check all the activity/plugin mappings to make sure that they are current and in sync with your process design.
Access of Forms
Process instance that contains activity mapping(s) make use of the forms created under the same app version. Regardless of the current published app version, the process instance's assignment will show form mapped to it, of the same app version the process instance falls under.
...