Configuring Siebel Business Applications > Configuring Lists and Pick Applets > Configuring Lists and Pick Applets >

Creating a Static List Manually

It is highly recommended that you use the Pick List Wizard to create a static list, but you can create a static list manually. For more information, see Using the Pick List Wizard to Create a Static List and How Siebel CRM Creates a Static List.

To create a static list manually

1. In Siebel Tools, click Applet in the Object Explorer.
2. In the Applets list, locate the originating applet.
3. In the Object Explorer, expand the Applet tree, and then click Control.
4. In the Controls list, add an originating control using values from the following table.

   Property	Description
   Field	Specify the originating field that resides in the originating business component.
   Pick Applet	Leave empty.
   Runtime	Set to TRUE. This setting indicates that Siebel CRM attaches and activates a static list if the user clicks the control or list column.

5. Click Business Component in the Object Explorer, and then locate the originating business component in the Business Components list.
6. In the Object Explorer, expand the Business Component tree, click Field, locate the originating field in the Fields list, and then modify the field using values from the following table.

   Property	Description
   PickList	Specify the pick list.

   If the originating field is a custom field, then make sure that it can accommodate the LOV table values. If the originating field is shorter than the values that exist in the LOV table, then Siebel CRM truncates the values from the LOV table when it displays these values in the Siebel client or when it stores them in the Siebel database.

7. In the Object Explorer, expand the Field tree, click Pick Map, and then add a pick map in the Pick Maps list using values from the following table.

   Property	Description
   Field	Choose the originating field.
   Pick List Field	Enter Value. This value references the Value field in the PickList Generic business component.

8. If you use a multiple column selection list, then configure more pick maps, as required.
9. In the Object Explorer, click Pick List, and then create a new pick list in the Pick Lists list using values from the following table.

   Property	Description
   Business Component	Choose PickList Generic. This value indicates that Siebel CRM gets the list of values from a system table. For more information, see About the Picklist Generic Business Component.
   Type Field	Choose Type. This value configures Siebel CRM to search the Type field in the PickList Generic business component for types. Each list of values includes a type that uniquely identifies the list and each value in the list.
   Type Value	Enter the relevant type for the list of values. For example, the values that display in the Lead Quality list in Table 56 include a Type Value property whose value is LEAD_QUALITY.
   Search Specification	In most situations, you can leave the Search Specification property empty. For more information, see How Siebel CRM Handles a Hierarchy of Search Specifications.
   Sort Specification	Do one of the following: To use the sort specification that is defined for the business component, leave the Sort Specification property empty. To override the sort specification that is defined for the business component, define a value in the Sort Specification property. For more information, see Creating a Sort Specification for a Static List.
   No Insert	Make sure the No Insert property contains a check mark. If the No Insert property does not contain a check mark, then Siebel CRM creates an error that is similar to the following: Unable to create list popup applet

Creating a Sort Specification for a Static List

You can define a Sort Specification on a list to override the sort specification that is defined on the business component. The default value for the Sort Specification property in a list is empty, so Siebel CRM uses the sort that is defined on the business component. It uses the Order By field in a Type to sort the list of values in ascending order, by default. If the Order By values are empty, then it sorts the entries for the Type alphabetically in ascending order according to the Value field.

You can specify a sort specification on a static list to modify this behavior. This modification applies only to the static list. A sort specification on a list object sorts values in the static list that references the list of values in the PickList Generic business component. For more information, see How a Business Component Sorts Records.

Using Calculated Fields with Bounded Lists

It is recommended that you do not configure a list of values that references a calculated field if this field references another field that the user can update. For example, Siebel CRM comes predefined with a list named PickList Activity Priority that resides on the Priority field in the Action business component. The following properties of this list include a check mark:

• No Insert
• Static
• Bounded

This list references the ACTIVITY_PRIORITY list of values that includes the following values:

• 1-ASAP
• 2-High
• 3-Medium
• 4-Low

This configuration requires the user to choose a value from the list of values. The user cannot manually add a value. However, if you configure the ACTIVITY_PRIORITY list of values to reference a calculated field, and if this field references another field that the user can update, and if the Predefault property of the business component contains a check mark, then Siebel CRM might allow the user to choose any value that the user enters in this updatable field. In this example, the user could add to the Priority field any value that the updatable field contains.