Consider a scenario where an administrator has used ACME_Process application to create ACME_Process_Ver1, which is active in the BP Server.
Suppose that the organization policy is changed, and the ACME_Process_Ver1 application needs changes. The application developer can modify the ACME_Process_Ver1 process template and create a new process template called ACME_Process_Ver2.
However, there are some active instances of the application ACME_Process_Ver1 and the application developer wants to retain version1. Using the process template versioning, the application developer wants to install a new version of application with the same AppName.
When the new version ACME_Process_Ver2 is installed, it becomes the active version, and the previous version ACME_Process_Ver1 becomes deprecated. No user can create new instances of ACME_Process_Ver1, as the template is deprecated.
Versioning allows the parent process template to have a single child (version), maintaining a one-to-one relationship between parent and child. In this example, when ACME_Process_Ver2 is installed, it is the child of ACME_Process_Ver1. In future, ACME_Process_Ver2 may also be modified to create ACME_Process_Ver3. In that case, ACME_Process_Ver3 will be the child of parent ACME_Process_Ver2.
Figure 6 illustrates the parent-child relationships.
Figure 6. Parent-child relationship in versions
Note that ACME_Process_Ver3 is not a child of ACME_Process_Ver1.
