Question
ANZ
AU
Last activity: 8 Mar 2017 10:58 EST
CPM Case search fetching only 20 results
Hi All,
try {
pega.getSearcherAPI().search(myStepPage, tools.getParameterPage(), tools.getThread());
}
catch(com.pega.pegarules.priv.search.nextgen.FTSSearchQueryParseException pe) {
//BUG-182975 - Ignore the exception
}
catch(com.pega.pegarules.priv.search.nextgen.FTSException fe) {
oLog.error(fe.getMessage());
}
is fetching only 20 results. I have tried increasing pyMaxWork count to 100. Also, re-indexing is done. But if I search with case ID its fetching all the cases separately.
Accepted Solution
Pegasystems Inc.
US
Hi Mathiyazhagan,
Support Article SA-25776 (https://pdn.pega.com/node/1176446) mentions HFix-28218 as the resolution. The product version for the corresponding SR is CPM 7.1 Release 2. Is that version applicable to you?
Do you have a working scenario you could use as a reference and add some debug statements (oLog.infoForced) to determine what the descrepance between the working and non-working scenario is?
Thanks,
Tigran
Pegasystems Inc.
IN
Hi Mathiyazhagan,
I found a similar issue in the SA article : https://community.pega.com/support/support-articles/cpm-search-results-find-work-gadget-displays-only-20-records
Regards,
Evita.
Updated: 26 Feb 2017 23:24 EST
instellars
IN
Based on our observation, CS has no control in limiting the search results.
The max limit of 20 is coming from PRPC by default.
Modifying pyMaxWork does not help.
Accepted Solution
Pegasystems Inc.
US
Hi Mathiyazhagan,
Support Article SA-25776 (https://pdn.pega.com/node/1176446) mentions HFix-28218 as the resolution. The product version for the corresponding SR is CPM 7.1 Release 2. Is that version applicable to you?
Do you have a working scenario you could use as a reference and add some debug statements (oLog.infoForced) to determine what the descrepance between the working and non-working scenario is?
Thanks,
Tigran