Siebel Order Management Guide Addendum for Communications > Employee Asset-Based Ordering > Roadmap for Configuring Bulk Requests >

Configuring Bulk Request Validation to Improve Performance

By default, when Bulk Requests validates records, information from those records is stored in a cache in case the information is needed later. If the number of records to validate is very large, then searching through the cache can degrade performance. In this case, you can improve performance by configuring Bulk Requests to get the validation information by querying the table every time instead of searching the cache.

To store bulk request information in a cache, the following arguments are defined in the Validate method of ABO Bulk Request Validation Service business service:

• Cache Instance. Stores bulk request instances in the cache.
• Cache Action Set. Stores bulk request action sets in the cache.
• Cache Action. Stores bulk request actions in the cache.

To configure Bulk Requests to query the table every time instead of searching the cache, you can reset the values of one or more of these arguments in workflow steps.

This task is a step in Roadmap for Configuring Bulk Requests.

To configure bulk request validation to improve performance

1. Log in to Siebel Tools as an administrator.
2. In the Object Explorer, click Revise Workflow.
3. In the Workflow Processes list, select ABO Bulk Request - Validate Process, and click the Validate Bulk Request step.

   The ABO Bulk Request - Validate Process workflow is called when a user clicks the Validate button to validate the bulk request information before submission. In this case, the Validate Bulk Request workflow step validates the bulk request explicitly.

4. In the Validate Bulk Request step, modify or accept the values of the parameters that are listed in the following table.

   Parameter	Values
   Cache Instance	Accept the default Y to store bulk request instances in the cache. Change the value to N to not store bulk request instances in the cache.
   Cache Action Set	Accept the default Y to store bulk request action sets in the cache. Change the value to N to not store bulk request action sets in the cache.
   Cache Action	Accept the default Y to store bulk request actions in the cache. Change the value to N to not store bulk request actions in the cache.

   You can use any combination of Y and N values for these parameters, and then check the performance results. If the instances, action sets, or actions are unique across the bulk request, then setting these parameters to N can be advantageous. Otherwise, you can use your judgment to store, or not store, each of these types of items in the cache.

5. In the Workflow Processes list, select ABO Bulk Request - Submit Process Workflow, and click the Validate Bulk Request step.

   The ABO Bulk Request - Submit Process Workflow is called when a user clicks the Submit button to submit the bulk request for processing. In this case, the Validate Bulk Request workflow step validates the bulk request implicitly during submission.

6. Repeat Step 4 for the ABO Bulk Request - Submit Process Workflow.

   NOTE:  You can set the parameters to different values in each workflow. For maximum performance advantage, however, it is recommended that you set these parameters to the same values in both workflows.

   Suppose, for example, you leave Cache Instance set to Y in the ABO Bulk Request - Validate Process workflow, but reset Cache Instance to N in the ABO Bulk Request - Submit Process Workflow. In this case, some instances are stored in the cache and some are not, depending on which bulk requests are validated explicitly and which ones are not.

7. Save and reactivate the workflows.

For more information about the workflows in this procedure, see ABO Bulk Request - Validate Process Workflow and ABO Bulk Request - Submit Process Workflow.