1. Configuring Siebel Business Applications
  2. How Siebel CRM Creates a Static List

How Siebel CRM Creates a Static List

The following figure shows the relationships and objects that Siebel CRM uses to create a static list, which are as follows:

  • User Interface Objects Layer. Contains the following objects: Control, Applet, Applet Web Template, Applet Web Template Items, List and List Columns. There is a 1:M relationship between Applet and Control, Applet and Applet Web Template, Applet Web Template and Applet Web Template Items (through properties), List and List Column. There is a 1:1 relationship between Applet and List.

  • Business Objects Layer. Contains the following objects: Business Component, Field, Pick Map, Pick List. There is a 1:M relationship between Business Component and Field, Field and Pick Map. There is a 1:1 relationship between Field and Pick List (through properties).

Relationships and Objects That Siebel CRM Uses to Create a Static List: This image is described in the surrounding text.

The following figure shows an example of how Siebel CRM creates a static list. This example implements the Quality list that is described in the preceding figure.

How Siebel CRM Creates a Static List: This image is described in the surrounding text.

As shown in this figure, 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.