Predefined Query, also called as PDQs in Siebel are very handy for end users. The end users often execute the same query multiple times or also the requirement could be such that as soon as the person navigates a particular view a default set of records should be displayed. Instead of redoing the query again and again we setup PDQs for this.
With PDQs in Siebel, the queries are stored and can be seen in the drop down list on the upper right hand side of the Siebel screen. When a particular query needs to executed, just select that particular query from the drop down.
There are two types of PDQs. Private and Non-Private. Private means that the query is only available for those people who created the query or for those who saved the query. This is normally done by end users and is available only to them. The second method below describes how to create this type of PDQ.
Non-Private PDQ means that the PDQ is available to all the users using the Siebel Application. This is normally created by either Developers or by Siebel Administrators using the first method described below.
There are two ways you can create a PDQ.
- Method 1: Go to SiteMap-> Administration-Application->Predefined Queries. (This view is normally accessible only to those having Siebel Administrator responsibilities.) Here you will see several Predefined Queries that already exist. You should also observe that PDQs are Business Object Specific. Meaning if you specify the query with Business Object Account, then this PDQ will be displayed under all views where the Business Object is Account.To define a new PDQ click New and start entering the required information. First the Business Object, then whether this query is Private or non-Private, Name and then Actual Query to be executed. The Name you give takes an important role. It decides which query to execute by default when the user navigates to a particular view. The Name is sorted and the first one on the top is the query that will be executed by default. So give the name appropriately. Sometimes developers start the name with asterisk or with a number so that it arrives on the top when sorted and is executed by default.
- Method 2: The second way of creating a PDQ is by saving the query that is executed using the Application Menu. To create this, first execute the query on the application you would like to save and then from the application menu on upper left hand side choose Query -> Save Query As. Give an appropriate name to the query. Once this is done you should be able to see the saved queries from the Saved Queries dropdown. Again the Name takes precedence on which query to execute by default. Also this query will be saved as private and available only to the person who saved it.
Hope this helps. Leave a comment.
Related posts(Auto Generated):





January 15th, 2009 at 11:16 pm
Very well explained!!
January 27th, 2009 at 3:09 am
Any idea how to style these ActiveX dropdowns in Siebel? The CSS file: jctrls.css does exhibit some declared values that match the visual appearance of these elements, but despite clearing cache, cookies, and history — then re-starting Client, I’m still not seeing changes made to what I THINK are the attributes that define the visual appearance of these elements. Help?!?
March 31st, 2009 at 4:03 pm
It would be good if you can explain the syntax of the PDQ like explaining more about Search and Sort option in the PDQ as well as the functions that can be used in the PDQ would be more perfect. Thanks.
March 31st, 2009 at 5:48 pm
Hi Kumar,
The best way to search about PDQ syntax is by looking at the existing ones. It is not complex.
I will see if I can post a blog on that. Thanks.
July 3rd, 2009 at 10:03 am
Greate man greate….Very help ful
February 12th, 2010 at 3:23 pm
Thanks man!! Well said…
February 20th, 2010 at 10:27 am
The examples for a search in a query field are:
”.Search = “[Id] IS NOT NULL” .Sort=”"
”.Search = “[Status] = “”Open”"” .Sort=”Name”
”.Search = “[Type] = LookupValue(”"EVENT_STATUS”",”"Done”")” .Sort=”Name, Description”
March 30th, 2010 at 11:23 am
Hi ,
Here is my problem . Can you please respond for it.
A custom button is there on one applet, when we enter into application home page and select PDQ’s the button is going to disable and it has to enable there..
How can i achieve this
March 30th, 2010 at 8:24 pm
Hi Guruprasad,
please use forums to discuss your problem. your requirement is not clear. please be more descriptive and clear.
–Sridhar
April 29th, 2010 at 2:29 pm
Hi,
Could you please advise on how to do Run- time queries in SIebel with an exanple?
August 3rd, 2010 at 5:47 am
Hi sridhar,
i would like to know the limitations and Disadvantages of PDQ’s can you please please help me in this.
thanks
September 17th, 2010 at 11:49 am
Hi,
Thank u verymuch….Very useful information for all of us….
June 9th, 2011 at 8:23 pm
Informative Post,I want to know how to create PreDefined Query on a field having MVL(where the value of the field is coming from another Business Component)?
January 12th, 2012 at 11:36 am
I just like the helpful info you provide for your articles. I’ll bookmark your weblog and check once more here regularly. I am fairly sure I will be told many new stuff right here! Good luck for the next!