1. Configuring Siebel Business Applications
  2. Using Calculated Fields with Bounded Lists

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.