Relocate Processes to a new modelling client

Processes have a complex structure. To avoid inconsistencies in the data between systems or clients, processes may only be edited in their modeling client, which always contains the most up-to-date status of the process.

If the client in which a process is modeled changes, the modeling client of the process must be relocated.

Number ranges

Process objects receive their numbers from a dedicated number range. 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.

Workflow versions

Workflows create new versions in the target system when they are imported via transport. If the new modeling client is set up via transports, not all workflow versions are transferred. This can therefore lead to differences in the assignment of workflow and process versions. However, this only affects old process versions and is therefore not a problem.

Relocation

• 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 in the new modeling client to the status in the old client. The 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 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 full, 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.

• Move the process in the new modeling client (move to local). This synchronizes the process and workflow versions and adjusts the original system of the workflow.