Workflow Premerge

When you start the repository merge, the workflow premerge step runs and prepares customer-modified seeded workflows for the repository merge.

If the workflow exists in both the Prior Customer Repository and New Siebel Repository, and the version number in the Prior Customer Repository is greater than 0, then the workflow is customer-modified.

For these workflows, the premerge process makes the following changes:

• Deletes version 0 of the customer-modified seeded workflow in the Prior Customer Repository.

• In the Prior Customer Repository, copies the most recent version with status Completed of the customer-modified seeded workflow and sets the copy’s version to 0.

  The most recent version of the workflow is the one with the highest version number and a status of Completed. This is called the version n workflow.

• Sets the copy’s status to Completed.

  The workflow premerge creates a version 0 copy of version n in the Prior Customer Repository because the merge process requires that workflows it compares between repositories must have the same name, must be version 0, and must have a status of Completed.