Process of Defining Dynamic Candidates

If you plan to create new dynamic candidate teams, then you must first modify the Dynamic Candidate objects before the candidates are available for adding to your assignment rules. The process is similar to Workflow Policy Component and Workflow Policy Component Column configuration. Using Siebel Tools, you modify the following object types:

Dynamic Candidate
Dynamic Candidate Component
Dynamic Candidate Component Col

Dynamic candidate configuration is a logical definition of the underlying team table, candidate column, and related joins to the assignment object. The Dynamic Candidate properties define the dynamic candidate name, team type, and so on. The Dynamic Candidate Component properties define the table and column names used in the join, and the Dynamic Candidate Component Col properties define columns used in the team-based criteria.

Note:

If you plan to use only the predefined dynamic candidate teams (Activity Account Team or Activity Asset Team) for your assignment rules, or if you have already created other dynamic candidate teams, then you can skip most of the steps and proceed directly to Step 5.

The process for defining dynamic candidate is a multi-step process and requires the following tasks. These tasks might vary according to your organization's business practices.

"Configuring Assignment Objects for Dynamic Candidates"
"Configuring Join Specifications for Dynamic Candidate Object Definitions"
"Mapping Columns From Source Tables to Team-Based Criteria"
(Optional) "Copying Dynamic Candidate Attribute Columns to the Team Table"
"Adding Dynamic Candidate Teams to Assignment Rules"

Configuring Assignment Objects for Dynamic Candidates

Dynamic candidates are the potential assignable candidates obtained from related business entities when assigning an object. The Dynamic Candidate Component object properties define the dynamic candidate name, team type, and so on.

Using Siebel Tools, you must first modify the properties of the Dynamic Candidate object type.

This task is a step in "Process of Defining Dynamic Candidates".

Use the following procedure to configure the Dynamic Candidate object type for dynamic candidates.

To configure an assignment object for dynamic candidates

Start Siebel Tools.
In the Object Explorer, expand Workflow Policy Object, and in the Workflow Policy Objects window, select the object that you want to configure.

Tip:
If Workflow Policy Object is not visible in the Object Explorer, then you can enable it in the Development Tools Options dialog box (View, then Options, and then Object Explorer).
Lock the project for the object by choosing Tools, then Lock Project (or Alt+L).

The pencil icon appears in the W field to indicate that the project for the object is locked.
In the Object Explorer, expand Assignment Object, and then select Dynamic Candidate.
In the Dynamic Candidates window, choose Edit, then New Record.
In the new record, enter values for the relevant information.

Table 7-3 provides descriptions of some of the Dynamic Candidate object properties.

Table 7-3 Dynamic Candidate Object Properties

Property	Description
Name	The name of the dynamic candidate team. For example, Activity: Asset Team.
Display Name	An alternative name to display to the Siebel Client. This property is optional. If no display name is provided, then the value in the Name field is used. By default, this is set to NULL.
Display Name - String Reference	The display name for this team appearing in the Person Candidates Source or the Organization Candidates Source list of value (LOV) fields on the assignment rule applet. Note: You must first create a string reference in the Symbolic String object, and then set the Display Name - String Reference to the symbolic string that you created.
Display Name - String Override	This property allows users to enter a display name without entering a symbolic string. The value in this property is what is displayed in the GUI, and it overrides any other display name entries. However, because this value has no symbolic string, it is not translatable. For this reason, use caution when assigning an override.
Inactive	Indicates whether the object is active or inactive. By default, this value is set to FALSE.
Team Table Attribute Id Column	The name of the column in the team table that contains the attribute ID, that joins to the Attribute Id column.
Team Table Candidate Id Column	The name of the column in the team table that contains the candidate ID, the foreign key to the candidate base table.
Team Type	Indicates whether or not the candidate team is employee-, organization-, or position-based. Note: If the Team Type property is not set, then the dynamic candidate will not be displayed in the Person Candidates Source drop-down list for the assignment rule.

Configuring Join Specifications for Dynamic Candidate Object Definitions

Siebel Assignment Manager supports complex joins to relate base table with other related entities. The Dynamic Candidate Component object properties define the table and column names used when performing a join from the assignment object primary table to the candidate table to retrieve the dynamic candidates.

Using the dynamic candidate feature, you can configure Assignment Manager to identify related business entities and retrieve potential candidates from these entities.

For example, you use the dynamic candidate feature when:

Assigning a position, such as Executive Sponsor, from the account team to a related child account
Assigning account sales representative positions to a child account's opportunity
Assigning an activity and you want to evaluate only employees who belong to that activity's service region, and if necessary, then add more criteria for product skills, and so on.

Because potential assignees for dynamic candidates can be derived from various related business entities, you must configure the relationship between these entities.

This task is a step in "Process of Defining Dynamic Candidates".

Use the following procedure to configure join specifications for dynamic candidates.

Note:

Before you can successfully use join specifications for creating dynamic candidate definitions, you must have a thorough understanding of database administration and how to use Siebel Tools. Also familiarize yourself with the basics of the underlying Siebel Business Applications architecture. For more information, see Using Siebel Tools and Siebel Deployment Planning Guide.

To configure join specifications for dynamic candidates

Start Siebel Tools.
In the Object Explorer, expand Workflow Policy Object, and in the Workflow Policy Objects window, select the object that you want to configure.

Tip:
If Workflow Policy Object is not visible in the Object Explorer, then you can enable it in the Development Tools Options dialog box (View, then Options, and then Object Explorer).
Lock the project for the object by choosing Tools, then Lock Project (or Alt+L).

The pencil icon appears in the W field to indicate that the project for the object is locked.
In the Object Explorer, expand Assignment Object, and then expand Dynamic Candidate.
Expand the Dynamic Candidate object further, and then select Dynamic Candidate Component.
In the Dynamic Candidate Component window, choose Edit, then New Record.
In the new record, enter values for the relevant information.

Table 7-4 provides descriptions of some of the Dynamic Candidate Component properties.

Table 7-4 Dynamic Candidate Component Object Properties

Property	Description
Additional Join Spec	Use this property to specify an additional join.
Candidate Id Column	The column in the Team table containing the ID of the candidate (employee, position, or organization).
Candidate Table	The name of the source table at the last level of a join.
Inactive	Indicates whether the component is active or inactive.
Name	The name of the dynamic candidate component.
Primary	When checked, indicates whether the dynamic candidate component is the primary for the dynamic candidate selected for the assignment object.
Score Column	The column in the Team table containing scores of the candidates.
Source Column Name	The column in the source table that relates to another dynamic candidate component.
Source Table Name	The table that the dynamic candidate component is based on.
Target Column Name	The column in the source table that relates to another dynamic candidate component.
Target Component Name	The target dynamic candidate component that is related to this dynamic candidate component.

Note:

Each dynamic candidate specified can have only one primary dynamic candidate component.

Mapping Columns From Source Tables to Team-Based Criteria

Using Siebel Tools, you create records in the Dynamic Candidate Component Col object to map columns in a source table, at a particular level in the join, to a team-based assignment criterion. You do so by specifying the attribute column name and the correct assignment criteria attribute name.

This task is a step in "Process of Defining Dynamic Candidates".

Use the following procedure to map columns from source tables to team-based criteria.

To map columns from a source table to team-based criterion

Start Siebel Tools.
In the Object Explorer, expand Workflow Policy Object, and in the Workflow Policy Objects window, select the object that you want to configure.

Tip:
If Workflow Policy Object is not visible in the Object Explorer, then you can enable it in the Development Tools Options dialog box (View, then Options, and then Object Explorer).
Lock the project for the object by choosing Tools, then Lock Project (or Alt+L).

The pencil icon appears in the W field to indicate that the project for the object is locked.
In the Object Explorer, expand Assignment Object, and then expand Dynamic Candidate.
Expand the Dynamic Candidate object further, and navigate to Dynamic Candidate Component Col.
In the Dynamic Candidates Component Columns window, choose Edit, then New Record.
In the new record, enter values for the relevant information.

Table 7-5 provides descriptions of some of the Dynamic Candidate Component Col object properties.

Table 7-5 Dynamic Candidate Component Col Object Properties

Property	Description
Assignment Criteria Attribute Name	The name of the assignment criteria attribute.
Assignment Criteria Name	The name of the assignment criteria. Note: This property is automatically populated when you select the assignment criteria attribute name.
Inactive	Indicates whether the component is active or inactive.
Name	The name of the dynamic candidate component column.
Parent Name	The name of the object definition's parent. This value is supplied by the system.

Copying Dynamic Candidate Attribute Columns to the Team Table

Siebel Assignment Manager supports copying of dynamic candidate attribute columns and stamping of attributes on each candidate obtained through a join on the team table by copying dynamic candidate attribute values at any level in an n-level join to the results team table.

You can create multiple entries to create joins. One of those entries you flag as the candidate table. The source table for that record is the team table for that dynamic candidate.

This task is an optional step in "Process of Defining Dynamic Candidates".

Use the following procedure to specify the column name in the results table where you want the attribute values stamped.

Note:

You can write results to both reporting or operational tables.

To copy dynamic candidate attribute columns to the team table

Start Siebel Tools.
In the Object Explorer, expand Workflow Policy Object, and in the Workflow Policy Objects window, select the object that you want to configure.

Tip:
If Workflow Policy Object is not visible in the Object Explorer, then you can enable it in the Development Tools Options dialog box (View, then Options, and then Object Explorer).
Lock the project for the object by choosing Tools, then Lock Project (or Alt+L).

The pencil icon appears in the W field to indicate that the project for the object is locked.
In the Object Explorer, expand Assignment Object, and then expand Dynamic Candidate.
Expand the Dynamic Candidate object further, and navigate to Dynamic Candidate Component Col.
In the Dynamic Candidates Component Columns window, choose Edit, then New Record.
In the new record, enter values for the relevant information.

Table 7-6 provides descriptions of some of the Dynamic Candidate Component Col object properties.

Table 7-6 Dynamic Candidate Component Col Object Properties Used for Stamping Attributes

Property	Description
Attribute Column Name	The name of the column in the source table.
Copy Column Name	The name of the column stamped on the team table when working in operational mode.
Reporting Copy Column Name	The name of the column stamped on the Name reporting table when working in reporting mode.

Adding Dynamic Candidate Teams to Assignment Rules

You can add dynamic candidates teams (position or employee) or organization dynamic candidate teams to assignment rules. You can use either the predefined dynamic candidate teams provided in the application or create your own teams using Siebel Tools.

This task is a step in "Process of Defining Assignment Rules" as well as "Process of Defining Dynamic Candidates".

Use one of the following procedures to add predefined dynamic candidate teams to your assignment rules.

Note:

If you plan to create you own dynamic candidate teams, then you must use Siebel Tools to configure the teams before implementing the following procedure. For more information about configuring dynamic candidate teams, see "Configuring Assignment Objects for Dynamic Candidates".

Adding a Person Dynamic Candidate Team to an Assignment Rule

Use the following procedure to add a person dynamic candidate team to an assignment rule.

To add a person dynamic candidate team to an assignment rule

Navigate to the Administration - Assignment screen, and then the Assignment Rules List view.
In the Assignment Rules list, drill down on the assignment rule for which you want to add a dynamic team.
Click the Person Candidates Source drop-down list and choose one of the following:
- Activity Account Team
- Activity Asset Team
- All People
- From Rule
- Any team that you predefined using Siebel Tools
  
  Note:
  For territory management, you can choose from several other predefined values. For more information about these values, see Siebel Territory Management Guide.

You use a similar procedure for adding organization dynamic candidate teams to assignment rules. However, there are no predefined organization dynamic teams from which to choose in the seed data; you must create your own organization teams.

Adding an Organization Dynamic Candidate Team to an Assignment Rule

Use the following procedure to add an organization dynamic candidate team to an assignment rule.

To add an organization dynamic candidate team to an assignment rule

Navigate to the Administration - Assignment screen, and then the Assignment Rules List view.
In the Assignment Rules list, drill down on the assignment rule for which you want to add a dynamic team.
Click the Organization Candidates Source drop-down list and choose one of the following:
- All Organizations
- From Rule
- Any team that you predefined using Siebel Tools