...
Process objects receive their numbers from a dedicated number range (object /PCH/BPFCU, see https://pronovia.atlassian.net/wiki/spaces/CUSTEN/pages/583306080/Maintaining+the+number+ranges#Definition-interval). If the modeling client is changed, it must be ensured that there are no inconsistencies in the number assignment. Depending on whether the process is to be moved temporarily or permanently, the consistency of the number ranges must be ensured.
...
Set the modeling client in the original modeling client to the new modeling client. This ensures that no further changes are made to the process that are not transferred to the new client.
Adjust the number status last used number (number object /PCH/BPFCU) in the new modeling client to the status in last used number of the old client. The last used number status in the new client must not be lower than in the original client. If you use number ranges, this only ever applies to the corresponding number range.
Import Transfer the process into the new modeling client and the associated workflow into the new development system. Make sure that the process has been imported in fulltransfered completely, including the latest changes. If the new modeling client was created as a system copy, make sure that all interim changes to the process are imported.
| Info |
|---|
The highest process version and the associated workflow must be present in the client. However, it is recommended to import transfer all process versions. |
Move the process in the new modeling client (move to local). See https://pronovia.atlassian.net/wiki/spaces/CUSTEN/pages/826572807/Relocate+modelling+clients+for+processes#Relocate-to-current-client. This synchronizes the process and workflow versions and adjusts the original system of the workflow.