Example of Using a Single Criterion for Two Assignment Objects

This topic gives one example of configuring Siebel Assignment Manager to assign candidates to two objects (Account and Opportunity) using criteria from only one of the objects. You might use this feature differently, depending on your business model.

See also "Using a Single Criterion for Multiple Assignment Objects".

The example is divided into the following procedures; perform each procedure in the order provided.

1. "Creating a Workflow Policy Component Using the Account and Opportunity Assignment Objects".

2. "Mapping the Opportunity Workflow Policy Component to the Opportunity Lead Contact Assignment Criteria".

3. "Mapping the Account or Opportunity Workflow Policy Component to the Lead Quality Code Assignment Attribute".

Creating a Workflow Policy Component Using the Account and Opportunity Assignment Objects

This topic is part of "Example of Using a Single Criterion for Two Assignment Objects".

Use the following procedure to create a workflow policy component for two assignment objects.

To create a workflow policy component using the Account and Opportunity objects

1. Start Siebel Tools.

2. Select the workflow policy object for which you want to create a workflow policy component.

   1. In the Object Explorer, select Workflow Policy Object.

   2. In the Workflow Policy Objects window, select the object.

      For this example, select Account.

3. With the Account assignment object selected, choose Tools, then Lock Project (or Alt+L), to lock the project.

4. Add a new workflow policy component record.

   1. In the Object Explorer, expand Workflow Policy Component.

   2. In the Workflow Policy Component window, choose Edit, then New Record.

5. Enter information in the fields for the new record using the following steps:

   1. In the Name field, type the name of the workflow policy component.

      For this example, type Account/Opportunity.

   2. In the Source Table Name field, select the source table for the workflow policy component.

      For this example, select S_OPTY.

   3. In the Source Column Name field, select the source column for the workflow policy component.

      For this example, select PR_DEPT_OU_ID.

   4. In the Target Component Name field, select the target component for the workflow policy component.

      For this example, select Account.

   5. In the Target Column Name field, select the target column for the workflow policy component.

      For this example, select ROW_ID.

Mapping the Opportunity Workflow Policy Component to the Opportunity Lead Contact Assignment Criteria

This topic is part of "Example of Using a Single Criterion for Two Assignment Objects".

After you create the workflow policy components for both objects, you map the workflow policy component to the assignment criteria. You do this by mapping a column to one of the workflow policy components. In this example, you map the Opportunity workflow policy component to the Opportunity Lead Contact assignment criteria.

To map a column to the workflow policy component

1. With the Account or Opportunity record still selected, expand the Workflow Policy Component object in the Object Explorer, and then select the Workflow Policy Component Col object.

2. In the Workflow Policy Component Columns window, choose Edit, then New Record.

3. In the Workflow Column Name field, select the workflow column for the workflow policy component.

   For this example, select Opportunity Lead Quality.

Mapping the Account or Opportunity Workflow Policy Component to the Lead Quality Code Assignment Attribute

This topic is part of "Example of Using a Single Criterion for Two Assignment Objects".

After you map a column to the workflow policy component, you map the workflow policy component to the assignment attribute. In this example, you map the Account or Opportunity workflow policy component to the Lead Quality Code assignment attribute.

To map an assignment attribute to the workflow policy component

1. In the Object Explorer, select the Assignment Attribute object.

2. In the Assignment Attributes window, select Lead Quality Code.

3. In the Object Explorer, expand the Assignment Attribute object and select the Assignment Attribute Column object.

4. In the Assignment Attribute Columns window, choose Edit, then New Record.

5. Enter information in the fields for the new record as described in the following substeps:

   1. In the Name field, type the name of the assignment attribute column.

      For this example, type Account: Lead Quality.

   2. In the Assignment Object field, select the assignment object to which candidates are assigned for the assignment rule.

      For this example, select Account.

   3. In the Workflow Policy Component field, select the workflow policy component to map to this assignment attribute.

      For this example, select Account/Opportunity.

   4. In the Workflow Policy Component Column field, select the workflow policy component column to map to this assignment attribute.

      For this example, select Opportunity Lead Quality.

   5. In the Sequence field, specify the sequence of this assignment attribute.

      For this example, type 2.

6. Update the Siebel runtime repository and run various server administration tasks.

   For instructions on updating your deployment with the new configurations, see "Updating Your Siebel Assignment Manager Deployment with New Configurations".

Note: You must redeploy the changes to the Siebel runtime repository whenever you add, inactivate, or delete any assignment object types, assignment criteria, and assignment attributes. Make sure that all projects are redeployed (not only the locked projects) if you inactivate or delete a high-level object type or assignment criteria. For more information about when to redeploy the changes to the Siebel runtime repository, see "Updating Your Siebel Assignment Manager Deployment with New Configurations".

Figure 6-8 shows an example of defining an assignment rule for the Account and Opportunity objects using only the Lead Quality Code assignment criteria. The figure shows:

• An Account Opportunity assignment rule using the Opportunity and Accounts objects and One, Best Fit assignee filter.

  
  

  Note: Only the Opportunity object appears in the Objects to Be Assigned field, even though the Accounts object is also assigned.

  
  

• The Account Opportunity assignment rule has the Lead Quality Code rule criterion applied and uses the Compare to Person comparison method and the Include inclusion method. This assignment rule is always required.

Figure 6-8 Example of Defining an Assignment Rule for Two Objects Using One Assignment Criteria