Bookshelf Home | Contents | Index | PDF |
Configuring Siebel Business Applications > About Applets, Controls and List Columns > Options to Create an Applet > Options to Filter Data Displayed in an AppletA search specification is an expression you can define in the Search Specification property that filters the set of CRM data that Siebel CRM displays in an applet. Although this topic describes a search specification for an applet, in general this information also applies to the search specification for a business component, link, or list. For more information, see the following topics:
The search specification contains the names of one or more fields in the business component and various operators. These items constitute a logical condition that determines which Siebel CRM records Siebel CRM displays in the applet:
The following search specification illustrates how you can filter CRM data so that Siebel CRM only displays records that contain a revenue that is greater than 5000: The following search specifications provide more examples of how you can filter CRM data: [Competitor] IS NOT NULL and [Competitor] <> "N" [Type] = LookupValue ("TODO_TYPE", "In Store Visit") Major Elements of a Search SpecificationTable 19 describes the major elements of a search specification. How Siebel CRM Handles a Hierarchy of Search SpecificationsBecause you can define a separate search specification on an applet, business component, link, or list, Siebel CRM uses specific logic to handle a situation where a hierarchy of search specifications exists. For example, if a search specification is defined on the applet and on the business component, then Siebel CRM does the following:
How Siebel CRM Executes a Search Specification That Is Defined on a Child AppletIf a search specification is defined on a child applet, then Siebel CRM does the following:
How Siebel CRM Executes a Search Specification That Is Defined on a Link or ListIf a search specification is defined on a link, then Siebel CRM does the following:
How Siebel CRM Handles a Search Specification if Multiple Applets Are InvolvedIf two applets reference the same business component, and if these two applets are included in the same view, then Siebel CRM generates one query against the Siebel database to update these applets. Because a database SELECT statement only supports one WHERE clause, the following conditions apply:
For example, Siebel CRM displays the Account List Applet and the Account Entry Applet in the Account List View. In the Account Entry Applet, Siebel CRM also displays the record that is chosen in the Account List Applet. If the user chooses a different row in the list or scrolls through the list, then Siebel CRM updates the Account Entry Applet to make sure the same record is chosen in the Account List Applet. Because Siebel CRM enters data into these applets from the same query, the applets display the same record set. Do not define the same search specification on the business component and on the applet. If you define the same search specification on the business component and on the applet, then duplicate joins might result. If a view must include two applets that must not display master detail relationships, then make sure each applet references a different business component. If these applet reference the same business component, then Siebel CRM might automatically synchronize them in the Siebel client because of links defined in the business objects. How the Applet Visibility Type Property Affects a Search SpecificationIf the Applet Visibility Type property of the view web template item includes a value that is not null, then Siebel CRM might ignore a search specification that is defined for the applets in that view. It is recommended that you use this property for applets in a view that reference a different business component. If you use this property, test it thoroughly for functionality. |
Configuring Siebel Business Applications | Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |