Configuring Siebel eBusiness Applications > Configuring Picklists and Pick Applets >

About Static Picklists


A static picklist is a list of predefined values that the user invokes from a field in an applet. When the user clicks the drop-down arrow to the right of the field, a single-column picklist appears. The user selects a value from the list, and then clicks Save to enter the value for the field. The values in the picklist are predefined by an administrator or developer and stored in the list of values table.

A picklist can be bounded or unbounded. A bounded picklist allows the user to select values from the list only. An unbounded picklist allows users to select values from the list or type values directly into the field.

A static picklist is a selection list that is invoked from a particular text box or list column in an applet. A static picklist in a Siebel application is shown in Figure 73.

Figure 73.  Static Picklist
Click for full size image

When the user clicks the drop-down button to the right of the text box, a single-column picklist appears. The user selects a value from the list by clicking the desired value. The selected value replaces the previous value in the text box.

NOTE:  You cannot delete the lookup value. You can set the picked field (for example, Lead Quality) back to NULL, unless it is required.

Static picklists differ from dynamic picklists in the following ways:

  • They are different in that a static picklist does not draw values dynamically from a pick business component. A static picklist is a static list of available selection values. Configuration of these values is an administration activity that is performed in the List of Values Administration view in a Siebel application.
  • They are different in that a static picklist generally does not invoke a dialog box with multiple list columns and buttons. All that appears is a simple one-column pop-up list, without buttons.

    NOTE:  It is possible to use a pick applet rather than a simple drop-down list to display a static list of values, but this is not common practice.

  • They are different in that a static picklist does not populate multiple controls in the originating applet. It populates a single control in the applet, and the corresponding field in the underlying business component.

For more information about dynamic picklists, see About Dynamic Picklists.

Static picklists are implemented using object types illustrated in Figure 74.

Figure 74.  Static Picklist Architecture
Click for full size image

Figure 75 shows the object types used in the implementation of a static picklist in greater detail, and identifies their interrelationships.

Figure 75.  Static Picklist Details

The roles of the object definitions in Figure 75 are summarized in the following list, and discussed in greater detail in the subsequent sections. The static picklist example refers to the Quality picklist illustrated in Figure 73.

  • Originating applet. Contains the control or list column that invokes the picklist. After the selection of a value from the picklist, the originating control displays a revised value. In the example, the originating applet is the Opportunity form applet.
  • Originating business component. Business component of the originating applet. This business component (in the example, the Opportunity business component) supplies the data presented in the originating applet (Opportunity form applet). The selection process in the picklist results in the update of one field in the current record in this business component.
  • Originating control or originating list column. Appears in the originating applet. It initiates the picklist when clicked. In the example, this is the Quality control.
  • Originating field. Field in the originating business component that the originating control represents. Generally, it has one pick map child object definition that defines the mapping of a field from the PickList Generic business component into the originating business component. In the example, the originating field is Quality.

    NOTE:  If the originating field is a custom field, make sure that it can accommodate the LOV table values. A field shorter than the LOV table values will cause truncation when it is displayed or stored in the database.

  • PickList Generic business component. Special-purpose business component for the list-of-value lists that are used in static picklists. It is administered through the List of Values view in the System Administration screen in Siebel applications. To access the List of Values view choose Site Map > Application Administration >List of Values from the menu bar.
  • Pick List object. The field of the originating control references the Pick List object definition. The Pick List object definition identifies the pick applet's business component, which is always PickList Generic. In the example, the Pick List is called Picklist Quality.
  • Pick Map object. Child of the originating field. The pick map defines a correspondence between the Value field in the PickList Generic business component and the originating field. This correspondence provides the information required to update the current originating business component record with information from the PickList Generic business component record when a selection is made.
  • Sequence Property. Defines the sequence for updating fields in the current originating business component record with information from pick business component record when picking this record. If you do not define sequence numbers on pick maps, they will be executed in the order in which they were created.
Configuring Siebel eBusiness Applications