Siebel Assignment Manager Administration Guide > Running Assignment Manager >

About Running Batch Assignment

Use batch assignment to assign multiple records of an object in a single batch. Typically, you want to run batch jobs periodically when you anticipate the least amount of database activity (such as daily or weekly after-hours).

Batch assignment runs only in rule group mode. At the time of the assignment request, you specify one of the rule groups as the Assignment Key parameter for the AsgnBatch server component job along with the request. You identify the records for batch assignment using an SQL WHERE clause. This WHERE clause is usually based on columns in the base table of the assignment object. For example, an example of a WHERE clause is:


You can use this clause to identify all service requests that are not as yet assigned to a owner.

You can have a batch assignment task load only a particular group of rules into memory by specifying the row ID of the rule group in the Assignment Key parameter when you start the task. If no rule group is specified for this parameter, the batch task loads all rules in the Default Rule Group into memory. If no rule groups have been defined in the application, then all active rules in the database load.

Reason to Not to Run Batch Assignment with Dynamic Assignment

For performance reasons, do not run dynamic assignment when running batch assignment. If you run both batch assignment and dynamic assignment in your environment, the batch assignment can activate dynamic assignment due to triggers created in the database required to run dynamic assignment. Before running batch assignment, you should deactivate all assignment policies and drop related triggers to prevent dynamic assignment from processing modified rules, objects, and candidates. After completing batch assignment, you can reactivate the assignment policies and reenable batch assignment.

Related Topic

Running Batch Assignment

Siebel Assignment Manager Administration Guide