Assignment Manager Siebel Bookshelf

Siebel Assignment Manager Administration Guide > Advanced Siebel Assignment Manager Configuration >

Configuring Siebel Assignment Manager to Use Reporting Tables and Columns


Siebel Assignment Manager provides a special set of tables to which you can write assignment results for what-if analysis. These tables are known as reporting tables, and the environment in which you work with these tables is known as the reporting environment. When you work in the reporting environment, you work in reporting mode.

By default, reporting mode is turned off; Assignment Manager does not write to the reporting tables. Using Siebel Tools, you can configure Assignment Manager to use reporting tables and columns (in lieu of actual assignment tables) by defining Assignment Object and Assignment Object Extension object properties.

NOTE:  You can retrieve reporting mode table data by using native database utilities, such as SQL*Plus, Query Analyzer, and so on. Do not modify or delete this data. Rather, assignment administrators should use the reporting tables to preview the temporary reporting results before executing Assignment Manager in actual production tables.

About Reporting Tables

You can think of the reporting tables as temporary draft tables that allow you to preview the results of Assignment Manager processing to see the changes that are going to be made before committing those changes to the actual database. Reporting allows you to run Assignment Manager multiple times without impacting current assignments. Assignment Manager can write to the reporting tables independently of whether results are written to actual assignment tables or not.

The reporting tables are especially useful when you want to filter and operate on a subset of candidates.

About Reporting Mode

When merging records in reporting mode, Assignment Manager runs in one of the following modes:

  • Snapshot mode. Assignment Manager reads from and writes to the reporting team tables only.

    Running in snapshot mode is similar to running in production mode, except that the result tables are different. Assignment Manager stores the results tables in the Assignment Object Extension object in Siebel Tools. In snapshot mode, the reporting team tables store a snapshot of the results.

  • Delta mode. Assignment Manager reads from the current actual assignments but writes to the reporting team tables.

    In delta mode, Assignment Manager stores the delta as compared with current actual assignments to the reporting tables. Assignment Manager also stores the delta information about whether a particular candidate was added or dropped, as compared with the same account or contact in actual assignments. You can later use this information to run reports.

    NOTE:  The values in the Assignment Object Extension object properties determine what columns are used to determine which candidates were added or dropped, which tables to use for reporting, which column to use as the key column, and which columns to use as the position, employee, or organization column.

Reporting mode is supported in default mode, that is, when Assignment Manager operates on one rule group at a time.

To configure an assignment object to use reporting tables and columns

  1. Start Siebel Tools.
  2. In the Object Explorer, expand Workflow Policy Object, and in the Workflow Policy Objects list, query for the object for which you want to enable reporting tables and columns.

TIP:  If Workflow Policy Object is not visible in the Object Explorer, you can enable it by selecting View, then Options, then Object Explorer in the Development Tools Options dialog box.

  1. 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 the project for the object is locked.

  2. In the Object Explorer, select Assignment Object Extension.
  3. In the Assignment Object Extensions list, choose Edit, then New Record, and then click in the available fields to enter relevant information.

Table 54 shows some of the properties of the Assignment Object Extension object type.

NOTE:  There are no predefined Siebel tables for the Position Reporting, Org Reporting, and Employee Reporting properties listed in Table 54. Customers must decide which tables to use, and create them manually.

Property

Description

Name

The name of the assignment object extension. This name should always match the assignment object name.

Inactive

Indicates if the object extension is active or inactive.

By default, this is set to FALSE.

Position Reporting Table

The name of the position reporting intersection table. If the assignment object can be assigned to multiple positions, this intersection table stores the set of position IDs that are assigned to the assignment object IDs.

Position Reporting Column

The name of the column in the position reporting intersection table that points to rows in the S_POSTN position table.

Required if Position Table property is non-NULL.

Position Reporting Insertion Column

This column marks the positions that are added to the team. Applicable in both snapshot and delta reporting modes.

Position Reporting Deletion Column

This column marks the positions that are removed from the team. Applicable in both snapshot and delta reporting modes.

Position Reporting Key Column

Stores the key values of the positions assigned to the team at run time.

NOTE:  The UseKeyVal parameter must also be set to TRUE.

Employee Reporting Table

The name of the employee reporting intersection table. If the assignment object can be assigned to multiple employees, this intersection table stores the set of employee IDs that are assigned to the assignment object IDs.

Employee Reporting Column

The name of the employee reporting intersection table that points to rows in the S_POSTN position table.

Required if the Employee Table property is non-NULL.

Employee Reporting Insertion Column

This column marks the employees that are added to the team. Applicable in both snapshot and delta reporting modes.

Employee Reporting Deletion Column

This column marks the employees that are removed from the team. Applicable in both snapshot and delta reporting modes.

Employee Reporting Key Column

Stores the key values of the employees assigned to the team at run time.

NOTE:  The UseKeyVal parameter must also be set to TRUE.

Org Reporting Table

The name of the organization reporting intersection table. If the assignment object can be assigned to multiple organizations, this intersection table stores the set of organization IDs that are assigned to the assignment object IDs.

Org Reporting Column

The name of the organization reporting intersection table that points to rows in the S_POSTN position table.

Required if Organization Table property is non-NULL.

Org Reporting Insertion Column

This column marks the organizations that are added to the team. Applicable in both snapshot and delta reporting modes.

Org Reporting Deletion Column

This column marks the organizations that are removed from the team. Applicable in both snapshot and delta reporting modes.

Org Reporting Key Column

Stores the key values of the organizations assigned to the team at run time.

NOTE:  The UseKeyVal parameter must also be set to TRUE.

Siebel Assignment Manager Administration Guide > Advanced Siebel Assignment Manager Configuration >

Configuring Siebel Assignment Manager to Add Scores Across Rules


You can configure Siebel Assignment Manager so that the same candidate (employee, position, or organization) can qualify from different assignment rules with different scores. By default, Assignment Manager treats passing candidates from different rules as if they were different candidates. However, it is possible for Assignment Manager to merge (add) the scores for the same candidate across rules and take the total score in the calculation of the primaries.

How you configure Assignment Manager to add scores across rules differs for each operating mode. You specify the Add scores across Rules (AddScores) parameter to determine Assignment Manager scoring behavior by way of the:

  • Assignment Manager (AsgnSrvr) component for interactive assignment
  • Batch Assignment (AsgnBatch) component for batch assignment
  • Assignment Request (In Process) workflow policy program for dynamic assignment

The following subtopics describe configuration for each mode in detail.

NOTE:  The AddScores parameter is applicable to static and dynamic candidates, but only if no rules are marked as exclusive. That is because you explicitly define the rule from which you want the primaries to come for exclusive rules.

Adding Scores Across Rules for Interactive Assignment

If you set the AddScores component parameter to TRUE, all requests sent to AsgnSrvr add scores for the candidates. However, when interactive assignment is used, the <Assign> menu method by default sets AddScores to FALSE, and subsequently passes AddScores = FALSE to the AsgnSrvr task. To override this behavior so that interactive assignment passes AddScores = TRUE for the assignment, you need to add a user property to the respective business component on which interactive assignment is running.

Alternatively, for requests sent to AsgnSrvr using a script or the Server Request business service, you can pass AddScores = TRUE as an input parameter to the AsgnSrvr task.

To configure Assignment Manager to add scores across rules for interactive assignment

  1. Start Siebel Tools.
  2. Configure the Action business component to add scores across rules.
    1. In the Object Explorer, expand Business Component.
    2. In the Business Components list, select Action.
    3. Choose Tools, then Lock Project (or Alt+L), to lock the project.
    4. In the Object Explorer, click Business Component User Prop, and add a new record with the following information:
      • Name = AddScores
      • Value = TRUE
  3. Check in the changes to the server.

    For more information about checking in changes, see Using Siebel Tools.

  4. Compile the siebel.srf file.

    For more information about recompiling the siebel.srf file, see Updating Your Siebel Assignment Manager Deployment with New Configurations.

  5. Make sure that all Siebel clients that create activity records have the new siebel.srf file by copying the newly compiled siebel.srf file to:
    • For the Siebel Server (for Siebel Web Clients), the objects\language directory, where language is the appropriate language code, such as ENU for U.S. English.
    • For Siebel Developer Web Clients, the objects\language directory, where language is the appropriate language code, such as ENU for U.S. English.

      NOTE:  This step applies only to the Siebel Web Client or Developer Web Client.

This procedure allows control of AddScores = TRUE for interactive assignment based on the object being assigned.

Adding Scores Across Rules for Batch Assignment

If you set the AddScores component parameter to TRUE, all tasks for batch assignment add the scores across rules for the candidates. Alternatively, you can also set Add Scores across Rules = TRUE at the task-level when starting a batch assignment task. For more information about running batch assignment, see Running Batch Assignment.

Adding Scores Across Rules for Dynamic Assignment

To add scores across rules for dynamic assignment, you must set the Add Scores program argument to TRUE for the Assignment Request (In Process) workflow policy program.

To configure Assignment Manager to add scores across rules for dynamic assignment

  1. Start Siebel Tools.
  2. Configure the Assignment Request (In Process) workflow policy program to add scores across rules.
    1. In the Object Explorer, expand Workflow Policy Program.
    2. In the Workflow Policy Programs list, select Assignment Request (In Process).
    3. Choose Tools, then Lock Project (or Alt+L), to lock the project.
    4. In the Object Explorer, click Workflow Policy Program Arg, select AddScores, and change the Default Value to TRUE.
  3. Check in the changes to the server.

How the AddScores Parameter Affects Primaries

By default, if an assignment rule has a primary employee, primary position, or primary organization set, and one of these passes, it is assigned as the primary if that rule passes and is the highest scoring rule for that object. However, if the AddScores parameter is set to TRUE, the primaries are ignored because the AddScores parameter overrides the primaries on the rule. The AddScores parameter assigns the highest-scoring employee, position, or organization across all the rules that pass for that object, and has more weight than the primaries.

For example, assume you have two rules (Rule 1 and Rule 2) that pass for a specific Account Z. Each rule has two positions that qualify, with scores as shown in Table 60.

Rule

Position A Score

Position B Score

Rule 1

100

120

Rule 2

50

20

Both rules combined

150

140

If the AddScores parameter is not applied (set to FALSE), Position B is the highest-scoring position, with a score of 120, and becomes the primary. However, if AddScores is set to TRUE, then Position A, with a score of 150, is the highest-scoring position and becomes the primary.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *