Siebel Business Process Framework: Workflow Guide > About Workflow Process Design Options >

About Batch Processing

A workflow process can be run in batch by running the Workflow Process Batch Manager server component (WfProcBatchMgr). Executing a process in batch allows you to execute the actions in a workflow process for multiple records. When using the Workflow Process Batch Manager, be sure to specify the business object with which the workflow process is associated. You must also use a search specification to locate the business component records that are referenced or manipulated. NOTE: It is recommended that only a service workflow process or a 7.0 workflow process be run in batch. Table 31 describes parameters for the Workflow Process Batch Manager. Table 31. Description of Parameters of the Workflow Process Batch Manager Display Name Workflow Process Name Description Required. Name of the workflow process definition to execute.

Search Specification

Search specification that identifies the work items to process. The Search Specification parameter is a generic parameter shared by Workflow Management server components. However, this parameter is only used by the WfProcBatchMgr component. A Search Specification parameter specified for a component other than WfProcBatchMgr is not used.

Scheduling a Batch Workflow

You can set up a batch workflow to run a workflow process at specified intervals. For example, 7 A.M. every Monday. You do this by setting up a component request to schedule a batch workflow.

To set up a component request to schedule a batch workflow 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Navigate to Administration-Server Configuration > Enterprises > Component Definitions. In the Component Request form, click New. In the Component/Job field, click the selection button. The Component/Jobs dialog box appears. Choose Workflow Process Batch Manager. In the Component Request Parameters form applet, click New. In the Name field, click the selection button, then choose Workflow Process Name from the dialog box. In the Value field, type in the name of the workflow process to execute. Click New to add another parameter. In the Name field, click the selection button. Choose Search Specification.

In the Value field, provide a search specification. For more information on running a workflow process in batch, see Siebel System Administration Guide.

About the Repeating Component Request

You can use the Repeating Component Request feature in conjunction with the workflow process to schedule the workflow task to be executed at a predetermined time. To view an example workflow process that benefits from a repeating component request, see Example Workflow Process That Traverses a Record Set to Close Obsolete Service Requests. For more information, see Siebel Server Administration Guide.

Using the Search Specification Parameter

When running a workflow process in batch, you can specify a search specification to limit the number of records evaluated. If you do not specify a search specification, Workflow Process Batch Manager executes the workflow process for each record of a particular type in the Siebel application. For example, if there are 100 SRs, the Workflow Process Batch Manager executes the workflow process 100 times, once against each SR. The Search Specification parameter on the Workflow Process Batch Manager is used to execute the search specification on the primary business component of the business object specified in the Business Object property of the workflow process. For each fetched record, the Workflow Process Batch Manager invokes the workflow process and sets the Object Id process property as the current active row.

Using Workflow Process Batch Manager When Primary and Non-Primary Business Components are Present
When running Workflow Process Batch Manager, if the Link Specification property is set to TRUE on a field on the primary business component, the number of records returned can be more than expected. This condition can affect performance. This is due to the fact that the field's value is passed as a default value to a field in the nonprimary business component through a link. This condition occurs when the primary business component has a link relationship with one or more nonprimary business components, as established through a Link object definition on the current business object. Therefore, it is important to be careful when the business component is accessed by querying records in a custom Business Service or when running Workflow Process Batch Manager.

Comparing Workflow Process Batch Manager Against Workflow Process Manager

Use the Workflow Process Batch Manager server component when you need to run the workflow process for all records of a particular business component. WfProcBatchMgr considers the primary business component associated with the business object property on the workflow process. WfProcBatchMgr then runs the workflow process on all records within that primary business component.

Considerations When Using a Custom Business Service

A situation can change when the workflow process involves a custom business service. For example, assume the custom business service contains a loop that processes all records and executes the business service code on each record returned from the code itself. Table 32 compares how the two process managers compare in this situation. Table 32. Comparison of Using WfProcMgr Against WfProcBatchMgr When Using A Custom Business Service That Contains a Loop If WfProcMgr Is Used The business service, and the loop, handles all the records at one time. This is the recommended way to execute this business service and workflow process. If WfProcBatchMgr Is Used Since the workflow process' business service already contains a loop, then using WfProcBatchMgr causes the business service loop to execute for every record in the primary business component. This leads to undesirable duplicate and repeated execution.