Siebel Business Process Framework: Workflow Guide > Architecture That Siebel Workflow Uses > About the Architecture of a Workflow Process >

Architecture You Use to Deploy a Workflow Process

It is not necessary to deploy changes to the Siebel runtime repository or to do a merge to deploy a workflow process. You define workflow objects in Siebel Tools and store them in the repository that Siebel Tools uses. You must publish the workflow process in Siebel Tools, and then activate it in the Siebel client before you can run it as a server task or from the Siebel client. If you use Publish/Activate in Siebel Tools rather than Publish, then it is not necessary to separately activate the workflow in the Siebel client.

To deploy a workflow process, you do the following work:

1. Publish. Siebel CRM reads the object definitions that exist for this workflow process in the Siebel repository tables, and then writes them, along with deployment parameters, into the run-time tables. For more information, see Publishing a Workflow Process.
2. Activate. Siebel CRM makes the workflow process available for use in the Siebel client. For more information, see Activating a Workflow Process.

Figure 5 describes how you use Siebel Tools and the Siebel client to deploy a workflow process.

Figure 5. Architecture You Use to Deploy a Workflow Process

Explanation of Callouts

Siebel CRM does the following to deploy a workflow process:

1. Marks the workflow process Completed for deployment.
2. Reads the workflow process from the repository.
3. When activated, writes the workflow process to the run-time tables.
4. You can modify some parameters of the deployed workflow process in the Siebel client.