Bookshelf Home | Contents | Index | PDF |
Configuring Siebel Business Applications > About Applets, Controls and List Columns > Options to Create an Applet > Options to Filter Data That Siebel CRM Displays 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. This topic describes a search specification for an applet, but this information typically 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 identifies the records that Siebel CRM displays in the applet:
The following search specification describes 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 include more examples of how you can filter CRM data: [Competitor] IS NOT NULL and [Competitor] <> "N" [Type] = LookupValue ("TODO_TYPE", "In Store Visit") Parts of a Search SpecificationTable 20 describes some of the parts of a search specification. How Siebel CRM Handles a Hierarchy of Search SpecificationsIf multiple search specifications exist on an applet, business component, link, or list, then Siebel CRM uses the object hierarchy to determine how to run these search specifications. 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 Runs 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 Runs 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 creates one query against the Siebel database to update these applets. A database SELECT statement only supports one WHERE clause, so 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, it displays the record that the user chooses 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. Siebel CRM enters data into these applets from the same query, so the applets display the same record set. You must not define the same search specification on the business component and on the applet. If you do this, 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 applets reference the same business component, then Siebel CRM might synchronize them in the Siebel client because of links that it defines 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 this 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, then you must test it thoroughly. Defining the Search Specification Property or the Sort Specification PropertyYou define the Search Specification property or the Sort Specification property of an object the same way define the expression for a predefined query except that you do not identify the business component and you do not include the following reserved words: Example Expressions That the Search Specification Property Can ContainThe following are example expressions that the Search Specification property can contain:
The entire search specification must reside on one line. If you use more than one line, then Siebel CRM displays a message that is similar to the following at run time: "Invalid search specification..."
Example That Includes a Sort in the Sort Specification PropertyThe following examples include a sort in the Sort Specification property:
Sorting With a Predefined QueryTo modify the expression that a saved query uses, you can use the PreDefined Query view to add a sort expression. You can specify one or more fields that refine an ascending or descending search. You can use the following format for a predefined query: 'Business Component Name'.Sort = "[Field] [[(DESC[ENDING])], [Field] [(DESC[ENDING]],...]"
Sorting in the ClientTo do a sort in the client, the user can sort items in a list column, use a predefined query, or you can configure the Search Specification property. To specify an ascending or descending sort after Siebel CRM gets data, the user can click a list column header in a list applet, and then click a sort button. For more information, see Siebel Fundamentals. Sorting Versus Searching
Siebel CRM does not support the GROUP BY clause for a business component. |
Configuring Siebel Business Applications | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |