Hello Paul, There are ways around the "unqualified search" issues as you hit upon. Personally, in our org we found unqualified searches caused degradation in our performance and at times locking up the mid-tier.
To solve our problem our admin has put in a get list limit. But we also have disallowed unqualified searches. On Aug 8, 2012 1:54 PM, "Hodgdon, Paul" <[email protected]> wrote: > ** > > Is there any harm in allowing unqualified searches in a production > environment. We had been told that we should disallow this for production, > but we are finding that in order to leverage some of the reporting > capabilities (dynamically choosing parameters such as groups) this option > is prohibiting this. In essence this really isn’t doing much as a user can > do a search where incident number is not null.**** > > -Paul**** > > ** ** > > ** ** > > IT Accounts & Remedy Administration Manager**** > > University of New Hampshire**** > > Client Services**** > > Primary: (603) 862-2377**** > > Alternate: (603) 862-4242**** > > [email protected]**** > > http://accounts.unh.edu**** > > ** ** > > *The information transmitted in this e-mail, including attachments, is > intended only for the person(s) or entity to which it is addressed and may > contain confidential/privileged material. Any review, retransmission, > dissemination, taking any action or other use thereof, by anyone other than > the intended recipient, is prohibited. Responses to this e-mail must not > include any restricted or sensitive information. If you received this in > error, please contact the sender and destroy any copies of this message, > including any attachments.*** > > ** ** > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
