Configuring Siebel eBusiness Applications > Creating and Administering Lists of Values >
Configuring Siebel Business Process Designer to Use MLOV-Enabled Fields
Additional configuration is required to enable the Siebel Business Process Designer to use MLOV-enabled fields. Siebel Business Process Designer compares values in target tables with values in the Business Process administration tables to determine whether a particular condition is true. For columns enabled for MLOVs, the value stored in the target table is the Language-Independent Code rather than the Display Value. However, the value in the Business Process Administration table is the Display Value. Siebel Business Process Designer cannot evaluate a condition by comparing the Language-Independent Code to the Display Value. To enable Siebel Business Process Designer to work with MLOV-enabled columns, you must configure Workflow entities so that they compare the language-independent code in the target table with the language-independent code in the Business Process Designer administration table. You must do this for the following entities:
Policy Conditions
Before you enable Policy Conditions, you must:
- Determine all the business component fields that are enabled for MLOVs.
- Of the fields that are MLOV-enabled, identify which ones are referenced by Policy conditions.
For each of the fields that reference a Workflow Policy condition, you must complete the following tasks:
- Create a new picklist to display LIC values.
- Create a new applet to display LIC values.
- Configure the Workflow Policy Column to use the new picklist and applet.
- Repick the values for existing workflow policies.
To create a LIC picklist for a Workflow Policy Column
- In Siebel Tools, navigate to the Workflow Policy Column object type that you want to enable to use with MLOVs.
- Find the Workflow Policy Column that references the MLOV enabled field.
- In the PickList property field, click the picklist name.
The Pick Lists window appears in the Object List Editor.
- Create a new picklist by copying the existing one and append LIC to the name.
For example, Picklist Account Status LIC.
- Verify that the Sort Specification property of the picklist is set to "Name."
To create a new LIC applet for a Workflow Policy Column
- Navigate back to the Workflow Policy Column selected in the previous procedure.
- In the Applet property field, double-click the name of the associated applet.
The Applet window appears in the Object List Editor.
- Create a new applet by copying the existing one and append LIC to the name.
- Add a new list column to the applet for the language-independent Code.
- In the Object List Editor, select List object type and then select the List Column object type.
- In the List Column window, create a new record by copying an existing one, and then set the Field property to "Name."
To configure the Workflow Policy Column
- Navigate back to the Workflow Policy Column selected in the previous section.
- In the PickList property field, select the new picklist created in Step 4 of the procedure To create a LIC picklist for a Workflow Policy Column.
- In the Source Field property, change the value from Value to Name.
- Compile changes.
To repick the values
- Log on using a client connected to the modified repository file.
- From the application level menu, choose View > Site Map > Business Process Administration > Workflow Policies.
- Repick the Values by selecting the conditions and reselecting the appropriate display values.
This will store the language-independent code.
Action Arguments
Before you enable Action Arguments, you must:
- Determine all the business component fields that are enabled for MLOVs.
- Of the fields that are MLOV enabled, identify which ones are referenced by Policy conditions.
For each of the fields that reference an Action Argument, you must complete the following tasks:
- Create a new picklist to display LIC values.
- Create a new applet to display LIC values.
- Configure the Action Arguments to use the new picklist and applet.
- Repick the values for the existing workflow policies.
To create a LIC picklist for a Workflow Policy Program Argument
- In Siebel Tools, navigate to the Workflow Policy Program object type and the Workflow Policy Program that contains the argument that you want to enable for use with MLOVs.
- Select the Workflow Policy Program Argument object type (child of Workflow Policy Program) and then select the Argument you want to enable for use with MLOVs.
- In the PickList property field, click the picklist name.
The PickLists window appears in the Object List Editor.
- Create a new picklist by copying the existing one and append LIC to the name.
To create a new LIC applet for a Workflow Policy Program Argument
- Navigate back to the Workflow Policy Program Argument selected in the previous procedure.
- In the Applet property field, double-click the name of the associated applet.
If no applet exists, you must create one.
The Applet window appears in the Object List Editor.
- Create a new applet by copying the existing one and append LIC to the name.
- Add a new list column to the applet for the language-independent code.
- In the Object List Editor, select List object type and then select the List Column object type.
- In the List Column window, create a new record by copying an existing one and set the Field property to Name.
To configure the Workflow Policy Program Argument
- Navigate back to the Workflow Policy Program Argument selected in the previous section.
- In the PickList property field, select the new picklist created in Step 4 of the procedure To create a LIC picklist for a Workflow Policy Program Argument.
- In the Source Field property, change the value from Value to Name.
- Compile changes.
To repick the values
- Log on using a client connected to the modified repository file.
- From the application level menu, choose View > Site Map > Business Process Administration > Workflow Policies.
- Repick the Values of arguments for existing workflow policies.
For more information about Siebel Business Process Designer, see Siebel Business Process Designer Administration Guide.
|