Siebel Business Process Framework: Workflow Guide > Architectures Used With Siebel Workflow > About Architectures Used with a Workflow Process >

Workflow Deployment Architecture

After defining and testing your workflow process, the workflow is deployed.

Deploying is the act of performing a two step process:

  1. Publishing. Reading object definitions for a workflow process that exist in the Siebel repository tables then writing those definitions along with deployment parameters into the run-time tables.
  2. Activating. Making the workflow process available for use in the Siebel client.

Figure 6 illustrates the relationship between Siebel Tools and the Siebel client when deploying a workflow process.

Figure 6. Workflow Deployment Architecture

Architectural components for workflow deployment include:

  1. The workflow process is marked Completed for deployment.
  2. The workflow process is read from the repository.
  3. When activated, the workflow process is written to the run-time tables.
  4. Some parameters of the deployed workflow process can be modified in the Siebel client.

To deploy a workflow process, it is not necessary to compile the SRF, nor is a merge required. Workflow components and definitions are defined as Siebel Tools objects and are stored in the Siebel Tools repository. Before you can run a workflow process as a server task or from the Siebel client, you must first publish the workflow process from Siebel Tools, then activate the workflow process from the Siebel client.

NOTE:  If you use the Publish/Activate button rather than the Publish button to publish the workflow process in Siebel Tools, it is not necessary to separately activate the workflow in the Siebel client.

Siebel Business Process Framework: Workflow Guide Copyright © 2008, Oracle. All rights reserved.