Configuring Siebel Business Applications > Localizing Siebel Business Applications > Configuring Certain Siebel Modules to Use MLOV Fields >

Configuring Siebel Assignment Manager to Use MLOV Fields

To determine if a condition is true, Siebel Assignment Manager compares values in target tables against values in the Assignment Manager administration tables. However, Assignment Manager cannot compare the language-independent code to the display value because of the following differences:

• Siebel CRM stores the language-independent code in the MLOV column of the database table.
• Siebel CRM stores the display value in the Assignment Manager administration table.

To allow Assignment Manager to work with an MLOV column, you must configure the criteria values and criteria skills so that they compare the language-independent code in the target table with the language-independent code in the Assignment Manager administration table. This situation is similar to configuring Siebel Workflow. For more information, see Configuring Siebel Workflow to Use MLOV Fields.

For more information, see Siebel Assignment Manager and Siebel Assignment Manager Administration Guide.

Preparing Criteria Values and Criteria Skills for an MLOV

In this topic, you prepare criteria values and criteria skills for an MLOV.

To prepare policy conditions and action arguments for an MLOV

1. Complete Preparing Policy Conditions and Action Arguments for an MLOV with the following modifications:
   1. In Step 1, display the workflow policy column and assignment attribute object types.
   2. In Step 6, identify the fields that reference the following object types:
      • Criteria values
      • Criteria skills
      • Workload rules
2. Set the criteria for each field that references criteria values and criteria skills:
   1. In the Object Explorer, click Assignment Attribute.
   2. In the Assignment Attributes list, locate the assignment attribute that must work with an MLOV field.
   3. Set properties of the assignment attribute using values from the following table.

      Property	Value
      Translate	Contains a check mark.
      Translate Pick Field	Choose the field that stores the language-independent code. The Name field usually stores the language-independent code.

   4. Repeat Step 2 for each field until you configured all criteria.
3. Set the workload rules for each field you identified in Step b:
   1. Create a new list to display language-independent code values.
   2. Create a new applet to display language-independent code values.
   3. Configure the workflow policy column to use the new list and applet.
   4. Choose the values for predefined records.

      Work you perform in this step is similar to work you perform to configure a workflow policy. For more information, Preparing Policy Conditions and Action Arguments for an MLOV.

4. Compile and test your changes.

   For more information, see Using Siebel Tools.