About Dynamic Candidate Types

Depending on how an assignment object is configured, the object can be assigned as either the single-owner or multiple-owner type. Dynamic candidates are also assigned as single-owner or multiple-owner type, as shown in the following image.

The following figure shows the following relationships:

• Candidates are of the single-owner type when you can associate only one candidate (employee, position, or organization) with an assignment object.

  In the first part of the following figure titled Single Owner, one employee is associated with a service request.

• Candidates are of the multiple-owner type when you can associate many candidates (employees, positions, or organizations) with an assignment object.

  In this example, multiple employees are associated with an activity, as shown in the upper part of the following figure, and multiple positions are associated with an opportunity, as shown in the lower half of the following figure.

  In the second part of the following figure titled Multiple Owner, multiple employees are associated with an activity: Emp1, Emp2, and Emp3 are associated with Activity.

  In the third part of the following figure also titled Multiple Owner, multiple positions are associated with an opportunity: Pos1, Pos2, and Pos3 are associated with Opportunity_Account 1. Pos4, Pos5, and Pos6 are associated with Opportunity_Account 2.

The main difference between single- versus multiple-owner is that in single-owner situations, Assignment Manager can assign only one candidate, whereas in multiple-owner situations, Assignment Manager can assign many candidates. For information about which assignment objects are restricted to a single assignee and which objects are capable of incorporating a team of assignees, see Teams Versus Individual Candidates.

Using Siebel Tools, you configure dynamic candidates by modifying dynamic candidate object properties. For more information about configuring dynamic candidates, see Process of Defining Dynamic Candidates.

In the GUI, you define team-based criteria for assignment rules that have dynamic candidates as you would any other criteria, that is, you apply a comparison method and define the criteria values. Only the Compare to Person or the Compare to Organization comparison methods are supported for team-based criteria.

However, an assignment rule defined for dynamic candidates does not necessarily need team-based criteria. An assignment rule can have any of the following:

• Static candidates and regular criteria

• Dynamic candidates and regular criteria

• Dynamic candidates and team-based criteria

• Dynamic candidates and a combination of regular and team-based criteria