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

About Static Lists

A static list is a type of list that displays a list of predefined values. If the user clicks the arrow that Siebel CRM displays to the right of a field in an applet, then it displays a list that contains a single column. The user chooses a value from the list, and then clicks Save to enter the value for the field. You can define the values in the list to store them in the list of values table.

A list can be bounded or unbounded:

• A bounded list is a type of list that allows the user to choose a value only from the list.
• An unbounded list is a type of list that allows the user to choose a value from the list or to type a value directly into the field.

You cannot delete the lookup value. You can set the field that the user chooses back to empty, unless it is required. Lead Quality is an example of a chosen field.

For more information, see Using the Pick List Wizard to Create a Static List and Creating a List of Values.

Viewing an Example of a Static List

You can view an example of a static list.

To view an example of a static list

1. In the Siebel client, choose the Contacts screen.
2. Choose the Contacts List link.
3. Choose an existing record in the Contacts list.
4. Choose the Mr/Ms field.
5. Click the down arrow.

   The list that Siebel CRM displays is an example of a static list. It includes static values, such as Miss, Mr., Ms., Mrs. and Dr.

How Siebel CRM Creates a Static List

Figure 64 describes the relationships and objects that Siebel CRM uses to create a static list.

Figure 64. Relationships and Objects That Siebel CRM Uses to Create a Static List

Figure 65 includes an example of how Siebel CRM creates a static list. This example implements the Quality list that is described in Figure 64.

Figure 65. How Siebel CRM Creates a Static List

Explanation of Callouts

Siebel CRM uses the following objects to create a static list:

1. Originating control or list column. The control or list column that the user clicks to call the list. In this example, Quality is the originating control.
2. Originating applet. The applet that contains the originating control or list column. After the user chooses a value from the list, the originating control displays a revised value. In this example, the Opportunity form applet is the originating control. The Business Component property of the originating applet identifies the originating business component.
3. Originating business component. Business component that the originating applet references. This business component supplies the data that Siebel CRM displays in the originating applet. It updates one field in the current record in this business component after the user chooses a value in the list. In this example, the Opportunity business component is the originating business component.
4. Originating field. Field in the originating business component that the originating control represents. This field typically contains one pick map child that defines how the field from the PickList Generic business component maps to the originating business component. In this example, Quality is the originating field.
5. PickList Generic business component. Business component that provides the lists in a static list. You use the List of Values view in the Administration - Data screen in the Siebel client to administer the PickList Generic business component. For more information, see About the Picklist Generic Business Component.
6. Pick list. Identifies the business component that the pick applet references and the field that provides data for the pick applet. This business component is always PickList Generic. In this example, the Pick List is named Picklist Quality. The field of the originating control references the list.
7. Pick map. Defines a relationship between the Value field in the PickList Generic business component and the originating field. If the user chooses a value from the list, then this relationship provides the information that Siebel CRM requires to update the record in the current originating business component with information from the PickList Generic business component. The pick map is a child of the originating field.
8. Sequence property. Defines the sequence that Siebel CRM uses to update fields in the current record of the originating business component. It updates these fields with information from the pick business component. If you do not define sequence numbers on the pick map, then it updates fields in the order that it uses to create these fields.

About the Picklist Generic Business Component

The PickList Generic business component is a specialized business component that Siebel CRM reserves for lists of values for static lists. The following fields in the Picklist Generic business component define and group the lists of values:

• Type. Groups together all records that Siebel CRM includes in one list of values. For example, the LEAD_QUALITY type identifies a record as a member of the Lead Quality list of values. Each list of values includes a type. For more information, see Creating a List of Values.
• Value. The value that Siebel CRM displays in the static list. For example, values for Lead Quality include Excellent, Very Good, High, Fair, and Poor.

For more information, see Caution About Using Specialized Classes.

Table 56 lists example data in the Picklist Generic business component.

Comparison of a Static List to a Dynamic List

A static list differs from a dynamic list in the following ways:

• A static list is a static list of values. It does not get values dynamically from a pick business component. An administrator defines these values in the List of Values view in the Administration - Data screen.
• A static list typically does not call a dialog box with multiple list columns and buttons. Instead, it uses a simple pop-up list that contains one column and no buttons. It is possible to use a pick applet rather than a simple list to display a static list of values, but Siebel CRM does not frequently use this configuration.
• A static list does not provide data for multiple controls in the originating applet. It provides data for a single control in the applet and the corresponding field in the business component that the applet references.

For more information, see About Dynamic Lists, and Creating a List of Values.