Predefined Queries (PDQs) is one of Siebel's most intuitive features. The user typically navigates to a view and queries data to get related records. In his daily work, the user will perform this same query several times. What if the user could see the already filtered data as soon as they enter the view? This is the concept of Predefined Queries (PDQs).
The user can define and save different queries for each view, which will show the data queried once navigating to the view. The stored PDQs can be found in the drop-down menu located at the top right of the application.
There are two types of PDQs: Private and Non Private.
- Private: Only the user who creates the PDQ has access to it.
- Non Private: All users have access to the PDQ.
To manage the PDQs, it is necessary to enter the Webclient> Site Map>Administration Application>Predefined Queries
PDQs can reduce application performance depending on the number of queries performed by each and/or related tables. In this case it would be advisable to disable the PDQs for a particular view. This way the user could always select a PDQ from the drop-down menu.
In versions prior to 8.0 the only way to disable PDQs in a view was to modify the .cfg file. Oracle has developed a new functionality to disable them from Tools, through an Application User Property.
Application>User Property>New Record
Name = PDQDisabledViewn Value = "Nombre de la Vista"
n is a number, used to assign the same property to different views to disable. For example:
PDQDisabledView1 = Opportunity History View
PDQDisabledView2 = Activities View
etc... etc...
