Siebel Business Process Designer Administration Guide > For Administrators: Administering Workflow Processes > About Deploying Workflow Processes >

Deploying Workflow Processes

There are two steps involved in deploying a workflow process because the workflow process definitions are stored as repository objects, while deployed workflow processes are stored in run-time tables along with their deployment parameters. You deploy workflow processes from the Siebel Tools repository to the Business Process Designer Administration client.

The first step to deploying a workflow process uses the Deploy button in the Object List Editor of Siebel Tools. The second step uses the Workflow Deployment view in the run-time client to change the status of the workflow process to Active and make it available for deployment.

NOTE:  If the workflow process you are deploying includes subprocess steps or new repository objects such as business components, business services, and views, you must first make sure these subprocess steps or repository objects are available to the workflow you are deploying. In the case of subprocess steps, deploy the subprocess workflows before deploying the parent workflow, so the subprocesses are accessible to the parent workflow process. In the case of new repository objects, first compile the new repository objects so they are accessible to the workflow process you are deploying.

See About Process Monitoring Levels for detailed information on deployment parameters.

To deploy a workflow process

1. After validating the workflow process by testing it, select the workflow process in the Object List Editor and click Deploy.

   The workflow's status changes from In-progress to Completed and is available as follows:

   • If you are connected to the server data source, the completed workflow process is available at run time to be activated.
   • If you are connected to the local data source, check in the workflow process. After you check in the workflow, it is available at run time to be activated.
2. In the run-time client, from the application-level menu, choose Navigate > Site Map > Administration - Business Process > Workflow Deployment and query for the workflow you just deployed.
3. With the workflow process selected, click the Activate button.

   This checks the syntax for validity, registers run-time events if used, and changes the status of the process to Active. It also changes the status of the previous active version to Outdated.

   1. If your workflow process has run-time events, you will also need to load the run-time events. From the application-level menu, choose Navigate > Site Map > Administration - Runtime Events, then click the applet menu and select Reload Runtime Events. This will load the run-time events in the current object manager session. For more information, see Siebel Personalization Administration Guide.
4. Set the deployment parameters for the workflow process:
   1. Set the activation date in the Activation Date/Time field.
   2. Set the expiration date in the Expiration Date/Time field.
   3. Set the replication to None, unless you are deploying the workflow process to mobile clients. If you are deploying the workflow to mobile clients, see Deploying Workflow Processes to Mobile Clients.
   4. Set the monitoring level in the Monitoring Level field. For more information, see About Process Monitoring Levels.

Now you can invoke the workflow process from any of the invocation modes: the Process Simulator, a script, or Workflow Policies.