Upgrade Planning for Siebel Workflow Designer

Platforms: Windows, UNIX, IBM z/OS.

The repository merge process preserves customizations you have made to seeded workflows. A seeded workflow is a Workflow Process object and all child objects shipped as part of a Siebel release.

Special premerge and postmerge steps have been added to the regular repository merge to allow merging customer-modified seeded workflows:

1. Workflow premerge. When you start a repository merge, this step runs and prepares customer-modified seeded workflows in the Prior Customer Repository for the repository merge.

2. Repository merge. After the workflow premerge completes, the main repository merge runs. The repository merge identifies modifications you have made to seeded workflows in the Prior Customer Repository. It then copies the modifications to the corresponding seeded workflows in the New Customer Repository.

3. Workflow postmerge. After the main repository merge completes, the workflow postmerge runs and sets workflow versions in the New Customer Repository.

All three parts of the repository merge display in the status bar of the Merge Repositories dialog box when you perform a repository merge.

The workflow merge steps fit into the overall flow of a repository merge as follows:

• Repository merge starts

• Workflow premerge

• Main repository merge

• Workflow post-merge

• Merge ends

• Run the postmerge utilities