Bookshelf v7.5: Setting Up Predefined Queries

Applications Administration Guide > Ongoing Application Administration Tasks >

Setting Up Predefined Queries

Predefined queries (PDQ) automate queries that a user can perform online. Rather than creating a query, entering criteria, and running the query, the user selects a PDQ from the Queries drop-down list.

Predefined queries can be private (available only to the person who created them) or they can be public (available to all the users of the application).

Both public and private predefined and user-defined queries are stored in the database table S_APP_QUERY.

There are two ways to set up predefined queries:

Create and execute a query in the usual way, and then save the query.
Create or modify a predefined query in the Predefined Query screen.

For more information about the syntax of Siebel queries, see Fundamentals and Siebel Tools Reference.

When setting up queries, remember:

The Administrator can define a PDQ using both displayed and nondisplayed fields.
You can reference only fields from the current applet's business component in your query.
On occasion, using the wildcard * to find all entries in a field may cause a performance problem. If it does, use IS NOT NULL instead. For more information about query operators, see Siebel Online Help.
Predefined queries are defined on a business object. All screens based on the same business object will display all the predefined queries created for that business object.
Do not query on fields of Siebel field data type DTYPE_NOTE.

NOTE: In the preconfigured application, the records shown on the application home page are determined by the predefined query Default, which is performed on the object WebCallCenter Home.

To create a predefined query by saving a query

Navigate to the screen where you will run the query.
Click the Query button in the applet title bar or select New Query from the applet drop-down menu.
In the applet that is displayed, enter the criteria for the new query.
Click the Go button and then click Run Query.
The query's results appear.

From the application-level menu, choose Edit > Query > Save As.
In the Save Query As dialog box, enter a name for the query, and click OK.
The query is added to your list of predefined queries. This query is private, and only you can view it.

If you want to make the query public:

From the application-level menu, choose View > Site Map > Application Administration > Predefined Queries.
In the Predefined Queries list, deselect the Private field in the record for the query you just created.

To set up a predefined query in the Predefined Query view

From the application-level menu, choose View > Site Map > Application Administration > Predefined Queries.
In the Predefined Queries list, add a new record and complete the necessary fields.
Some fields are described in the following table.

Field

Comments

Name

This is the name that appears in the predefined query drop-down list.

Object

The object upon which the query is performed.

Private

Marked if the query is available only to the person who created it.
When you unmark a query to make it public, the other users must first exit the application and reenter before they can see the newly public query.

Query

The SQL code for the query.
When you create a query for a field that is a multi-value group, you can use the EXISTS operator to query nonprimary child records.

Cache Result

If this is Y, the query returns all rows up to the value of the DSMaxFetchArraySize parameter set for the data source.
For information about setting DSMaxFetchArraySize, see about modifying Named Subsystems in the Siebel Server Administration Guide.
Note: Setting DSMaxFetchArraySize to -1 and Cache Result to Y may cause memory problems for queries returning many rows.

About Multi-Value Group Queries in Siebel Industry Applications

In Siebel Industry Applications, the default behavior of queries in Multi-Value Group (MVG) fields is set to automatically add an EXISTS statement to every MVG query. This allows detailed cross-business object queries, such as the following example from Siebel Pharma:

Find all the Contacts
Who are ranked High in a specific therapeutic class
Who have not been visited for over a month by any sales representative
With a best time to call on Monday afternoon

This MVG behavior, however, also prevents the following query in an MVG field:

EXISTS (A) AND EXISTS (B).

To disable the EXISTS statement

Set the Default MVG Exists Query system preference to FALSE.
For more information about changing system preferences, see Setting System Preferences.

Field	Comments
Name	This is the name that appears in the predefined query drop-down list.
Object	The object upon which the query is performed.
Private	Marked if the query is available only to the person who created it. When you unmark a query to make it public, the other users must first exit the application and reenter before they can see the newly public query.
Query	The SQL code for the query. When you create a query for a field that is a multi-value group, you can use the EXISTS operator to query nonprimary child records.
Cache Result	If this is Y, the query returns all rows up to the value of the DSMaxFetchArraySize parameter set for the data source. For information about setting DSMaxFetchArraySize, see about modifying Named Subsystems in the Siebel Server Administration Guide. Note: Setting DSMaxFetchArraySize to -1 and Cache Result to Y may cause memory problems for queries returning many rows.

Applications Administration Guide
Published: 09 September 2004