Upgrade Guide > Preparing Siebel Application Data for Upgrade >

Preparing Siebel Workflow Processes for Upgrade

Upgrades: All Siebel upgrades.

Environments: Development, production test, production.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

This task prepares workflows for upgrade.

At Siebel 7.7 the following changes were made to workflow management:

• The upgrade migrates custom workflows from S_WF_* tables to S_WFR_* tables in the Siebel Repository. The upgrade also updates seed workflows.
• The tables S_WF_PROP_VAL and S_WF_STEP_INST no longer store workflow process instances. Workflow process instances are now stored in S_WFA_INST_LOG, S_WFA_INSTP_Log, and S_WFA_STPRP_LOG.

Upgrades from Releases Prior to Siebel 7.7

Perform the following task before upgrading from releases prior to Siebel 7.7.x.

Preparing workflow processes for upgrade

1. Development environment. Verify that all customized workflows and all seed workflows from the production database are present in the development environment Siebel Database.

   If the workflows from the production environment are not present, they will not be moved to the Siebel Tools Repository. You will have to manually move them using database tools.

   Oracle provides a script and an input file for migrating workflow data between your production database and your development database. See Alert 1016 on Oracle's Siebel SupportWeb.

2. All environments. Verify there are no queued or running workflows.
3. All environments. Purge S_WF_PROP_VAL and S_WF_STEP_INST.

   For information on purging these tables, see the topic on purging workflow process instances in Siebel Business Process Designer Administration Guide.

Upgrades from all Releases

Perform the following task in all environments.

Preparing workflow processes for upgrade

1. Deactivate all workflow processes.

   This ensures that run-time event actions associated with old workflows are cleaned up properly.

2. Verify that all tasks with status = QUEUED are removed from S_SRM_REQUEST.

   The upgrade process does not clear these.