Pick Lists ensure that end users can only select valid values for a field. This is a major boost for data quality and usability. It is important for developers to understand how pick lists work in Siebel CRM and how they can be configured.
In this chapter, we will learn the following:
Understanding pick lists
Creating a new static pick list for an existing field
Administering the List of Values table
Creating dynamic pick lists
Creating pick applets
Constrained and hierarchical pick lists
Siebel CRM supports two types of pick lists—static and dynamic. The preconfigured applications are replete with examples for both types. In the following, we will use the Opportunity entity as an example to examine static and dynamic pick lists.
A static pick list is rendered in the user interface (UI) as a simple one column drop-down box. The following screenshot shows the Lead Quality pick list in the More Info form applet for opportunities:
Static pick lists like the previous one are typically bounded, that means that end users are only allowed to enter values provided by the drop-down list. An unbounded pick list allows the end user to enter values which are not displayed in the pick list. The Probability field of an opportunity is an example for an unbounded pick list in preconfigured Siebel CRM applications.
On the business component level, we find that each field that exposes the behavior described previously has the following characteristics...
Developers are supported in the task of creating pick lists by the Pick List Wizard in Siebel Tools. In the following case study example, we will use this wizard to create a new static pick list for a field.
In Chapter 9, Business Objects and Links, we created a new child business component named AHA Customer Offer. As indicated in the field level requirements, a new static pick list should be created for the Response Type field with the following values:
Purchase
Tentative
Positive
Negative
The following procedure describes how to create a new static pick list for a business component field using the Pick List Wizard:
1. Navigate to the AHA Customer Offer business component.
2. Check out or lock the business component if necessary.
3. In the Object Explorer, expand the Business Component type and select the Field type.
4. In the Fields list, query for the Response Type field.
5. Right-click the Response Type field and select...
The data for static pick lists is stored in the S_LST_OF_VAL table as we have learned previously. The data set for a single pick list is defined by the Type value. Administrators and developers have two options to administer data in the S_LST_OF_VAL table:
Use the List of Values list in Siebel Tools
Use the List of Values view in the Siebel Web Client
Both applications allow us to add, modify, or deactivate entries in the List of Values data pool. In the following example procedure we describe how to undertake these tasks in the Siebel Web Client. For example purposes we will deactivate the Purchase entry in the AHA_CUST_RESPONSE type and create a new entry with a value of Decided to buy:
1. Log in to the Siebel Developer Web Client to the same database that you used to create the AHA Customer Response Pick List in the previous section.
2. Navigate to the site map.
Hint: Click the globe icon on the toolbar or press Ctrl+Shift+A
3. Navigate to the Administration...
The process of creating dynamic pick lists is similar to that of creating static pick lists. The major exceptions are that dynamic pick lists reference commonly used business components such as Account or Internal Product and that a pick applet must be specified in the applet control or list column.
As indicated in the previous chapter, the solution architect team of AHA has defined the following requirements for the Product Name field of the AHA Customer Offer business component:
Create a new pick list that only displays products marked as orderable
Create a new read-only pick applet
We will describe example procedures for these tasks in this and the following section.
The following procedure describes how to create a new dynamic pick list for the Product Name field of the AHA Customer Offer business component:
1. Navigate to the AHA Customer Offer business component.
2. In the Object Explorer, expand the Business Component type and select the Field...
To finalize the work started in Chapter 9 and subsequently fulfill AHA's requirements, we can use the following procedure to reuse an existing pick list for the Responsible User Login Name field in the AHA Customer Documents business component. The AHA technical architect team has identified PickList Login Name as the pick list definition to reuse:
1. Navigate to the AHA Customer Documents business component.
2. Check out or lock the business component if necessary.
3. Navigate to the Responsible User Login Name field.
4. Right-click the field and select Add Pick List...
5. In the Pick List Type page of the Pick List Wizard select Dynamic.
6. Click Next.
7. In the Pick List Definition page, select Use existing Pick List.
8. In the Existing Pick Lists list, select the PickList Login Name pick list.
For easier navigation in the list, you can type the name on the keyboard (case not required) after clicking inside the list.
9. Click Next.
10. In the Pick...
The second requirement stated in the previous case study example is to create a new pick applet that displays the product data to end users so they can select one product.
Developers have the following options for pick applets (sorted from least to most effort):
Reuse existing pick applets based on the same pick business component
Copy an existing pick applet and modify the copy
Create a new pick applet using the Pick Applet wizard
Did you know?
Because the Pick Applet wizard does not place all typical pick applet controls such as the Find combo boxes on the web layout, these must be copied from an existing pick applet using the Compare Objects window in order to avoid placing them on the wrong placeholders.
The following procedure describes how to copy an existing pick applet and modify the copy. Copying an existing pick applet ensures that all typical pick applet controls such as the Find functionality are present in the custom pick applet on the...
In order to test the business layer and applet modifications, we must be able to view the applets in the Siebel Web Client. In early phases of the project (such as in this chapter), it may be necessary to create a simple test view that exposes the modified applets.
The procedure to create and register new views has already been laid out in Chapter 5, so only brief instructions are given here for creating a test view for the AHA Customer Offer List Applet and the AHA Customer Documents List Applet:
1. Use the New View wizard to create a view with the following characteristics:
Project: AHA User Interface
Name: AHA UI Test View
Title: Test View
Business Object: Account
Upgrade Behavior: Preserve
Web Template: View Detail
Applets: AHA Customer Profile Form Applet, AHA Customer Offer List Applet, AHA Customer Documents List Applet
Applet Mode for all list applets: Edit List
2. Arrange the list applets side by side by positioning them on the 50 percent...
Because of the fact that pick lists are based on the feature set of business components, developers can limit the record set visible to the end user in the pick list. This technique is called constrained pick lists and applies to static and dynamic pick lists alike.
Hierarchical pick lists are a special type of static pick lists where the end user has to follow a defined sequence of selection. For example, the area field of a service request has to be filled before the subarea field. The subarea dropdown will only display values suitable for the selected area.
Filtering the record set for a pick list can be required for various reasons. Usability and data quality are among the typical reasons. Another reason can be data security.
We have the following options to filter the record set for a pick list:
Constrained pick maps (discussed in this section)
Specify a search specification on the pick business component, the pick list, or the pick applet (discussed...
Static and dynamic pick lists ensure that high levels of usability and data quality can be easily achieved in Siebel CRM applications.
Simple drop-down boxes are implemented as static pick lists. The values for these pick lists are administered in a central List of Values table.
Relationships between entities, such as the account for an agreement, are supported by dynamic pick lists and pick applets, which allow the user to search and modify the data set.
Pick maps define the values to copy between the pick and the originating business components as well as the rules to constrain the entries in the pick list.
Finally, pick lists can be organized hierarchically to support multi-level selections.
In the next chapter, we will learn how to configure multi value fields.
© 2011 Packt Publishing Limited All Rights Reserved
