Bookshelf v7.8: Migrating Custom Workflows

Migrating Custom Workflows

Upgrades: Releases 7.7.x, 7.8.x.

Environments: Development environment only.

This topic is part of an upgrade process. See How to Perform the Upgrade.

Custom workflows are not migrated to the New Customer Repository during the upgrep. You must use Siebel Tools to migrate these workflows to the New Customer Repository.

The migration process has the following characteristics:

Migrate custom workflows to the New Customer Repository during the development environment upgrade and before the upgphys. This ensures that the repository definition exported during upgphys is complete. If you migrate workflows after the upgphys, you must re-export the repository definition.

All workflows that are in the Prior Customer Repository but not the New Customer Repository are copied to the New Customer Repository. Siebel version 0 workflows are not copied.

If you have modified a Siebel version 0 workflow, change the name of this workflow in the Prior Customer Repository before starting the migration process. This causes the migration process to copy the workflow to the New Customer Repository.

You can repeat the migration process as needed. You can also exit the migration process before completion and run it again later. You can perform or repeat the migration process at any time after the upgrep and before the upgphys.

To migrate custom workflows

Start Siebel Tools.

NOTE: The Siebel Tools version must be 7.8.x or later.

Select Tools > Upgrade > Migrate Custom Workflow Processes.

The Select Repositories dialog box appears.

Make the following selections in the dialog box, then click OK:


Field Name	Make This Selection
Prior customized repository	Prior Customer Repository. Or select the repository that you are using as the Prior Customer Repository.
New customized repository	New Customer Repository. Or select the repository you are using as the New Customer Repository.

The Migrate Workflow Process dialog appears. This dialog shows the steps in the migration. An OK in the first column means the workflow was migrated successfully.

To stop the migration before it completes, click Cancel.

To restart the migration later, begin at Step 1 again.

Review the log file for errors.

The log file is located at Tools_install_dir\log\upgwf.log.

NOTE: To locate logged errors, search the log for the word error.

Troubleshooting

If the migration process encounters an error and cannot migrate a workflow, it prints the word error instead of OK in the first column of the Migrate Workflow Processes dialog and in the log file.

In most cases, errors are caused by a problem with the workflow record in the Prior Customer Repository. Examine the record, resolve the error, and rerun the workflow migration.