Applications Administration Guide > Ongoing Application Administration Tasks >
Setting Up Predefined Queries
This section discusses how to set up predefined queries. It includes the following topics:
About 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). 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.
Things to Remember
When setting up queries, remember:
Procedures
The following procedures describe how to create a predefined query by saving a query and how to set up a query in the Predefined Query view. To create a predefined query by saving a query
- Navigate to the screen where you want to run the query.
- Create and execute a query.
- From the application-level menu, choose Query > Save Query As.
- In the Save Query As dialog box, enter a name for the query.
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:
- Navigate to the Administration - Application screen > Predefined Queries view.
- 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
- Navigate to the Administration - Application screen > Predefined Queries view.
- In the Predefined Queries list, create a new record and complete the necessary fields.
Some fields are described in the following table.
|
|
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. For more information about the syntax, see about operators, expressions, and conditions in Siebel Developer's Reference. |
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 System Administration Guide. NOTE: Setting DSMaxFetchArraySize to -1 and Cache Result to Y may cause memory problems for queries returning many rows.
|
|