Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Business Process Designer Administration Guide > For Administrators: Administering Workflow Processes > About Deploying Workflow Processes > Deploying Workflow ProcessesThere 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.
Now you can invoke the workflow process from any of the invocation modes: the Process Simulator, a script, or Workflow Policies. |
![]() |
![]() ![]() |
Siebel Business Process Designer Administration Guide |