Siebel Business Process Framework: Workflow Guide > Options for Configuring a Workflow Process >

Configuring Batch Processing

If Siebel CRM must run a workflow process for every record of a business component, then you can configure the Workflow Process Batch Manager (WfProcBatchMgr) server component. It can run a workflow process one time for each record that the primary business component contains. For more information, see Defining the Primary Business Component.

It is recommended that Siebel CRM only run a service workflow process or a 7.0 flow workflow process in batch mode.

For more information about running a workflow process in batch, see Siebel System Administration Guide.

To configure batch processing

1. In the Siebel client, navigate to the Administration-Server Configuration screen, Enterprises, and then the Component Definitions view.
2. In the Component Request form, click New.
3. In the Component/Job field, click the selection button.

   The Component/Jobs dialog box displays.

4. Choose Workflow Process Batch Manager.
5. In the Component Request Parameters form, click New.
6. In the Name field, click the selection button, and then choose Workflow Process Name from the dialog box.

   For more information, see Parameters of the Workflow Process Batch Manager.

7. In the Value field, type in the name of the workflow process to run.
8. Click New to add another parameter.
9. In the Name field, click the selection button.
10. Choose Search Specification.
11. In the Value field, provide a search specification.

Parameters of the Workflow Process Batch Manager

Table 41 describes parameters of the Workflow Process Batch Manager server component.

Configuring Batch Processing with a Search Specification

To limit the number of records that Siebel CRM evaluates when it runs a workflow process in batch, you can define a search specification. Siebel CRM uses the Search Specification parameter on the Workflow Process Batch Manager to run the search specification on the primary business component. For each record it finds, the Workflow Process Batch Manager starts the workflow process and sets the Object Id process property to the current active row. For more information, see Defining the Primary Business Component.

If you do not define a search specification, then the Workflow Process Batch Manager runs the workflow process for each record of a particular type. For example, if 100 service requests exist, then it runs the workflow process 100 times, one time for each service request.

Configuring Batch Processing to Run Repeatedly at a Specific Interval

To configure Siebel CRM to run a batch at a specific interval, you can use the Repeating Component Request feature. For example, you can configure a workflow process to run at 7 A.M. every Monday. For an example workflow process that uses a repeating component request, see Defining a Workflow Process That Traverses a Record Set to Close Service Requests. For more information, see Siebel Server Administration Guide.

Configuring Batch Processing with Linked Fields

If Siebel CRM runs the Workflow Process Batch Manager, and if the Link Specification property is TRUE on a field of the primary business component, then Siebel CRM might return more records than expected. This situation can affect performance.

If the primary business component contains a link relationship with one or more nonprimary business components, as created through a Link on the current business object, then Siebel CRM passes the value that the field contains to a field in the nonprimary business component through this link. If Siebel CRM runs Workflow Process Batch Manager in batch mode, or if a custom business service queries business component records, then it is important to monitor performance and modify the configuration, if necessary. For more information, see Defining the Primary Business Component.

Configuring Batch Processing with a Custom Business Service

If a custom business service that you define includes a loop that processes every business component record, and if it runs business service code on each of these records, then you must consider how this configuration uses the server component. Table 42 compares how the two server components work in this situation.