How to Customize the Search Filters in Case Manager Portal?

Hi we have a requirement to customize the search filters and the display grid.

The source of the grid is a data page D_pyWorkSearch which is populated by an activity pySearchWrapper . On tracing the activity I was struck at a point where an activity named "CL:Embed-ReportContent ID:pzSearch RS:Pega-SearchEngine" makes an API call pega.getSearcherAPI().

I am not sure how or what this API call does. I found a RD : pyWorkSearch in Work-. But modifying that doesn't seem to reflect on the resulting DataPage at the end. But running the RD standalone does retrieves my added column.

Also the other thing is we need to customize the search filter based on a work property. Eg: MemberID. So we need this in the Filter condition and we need the result table to show this column(This property is exposed).

Have any one made any such changes to the portal search screen?

Any insight on how to approach this would be very helpful. Thank in advance :)


Keep up to date on this post and subscribe to comments

February 8, 2018 - 4:21pm

What might be safer than modifying the default search would be to add a new button that you associate with your own report definition rule.  That way, you can customize the search within the report definition rule.


May 21, 2018 - 6:34am
Response to ericosman_GCS

Hi It seems the report pyWorkSearch is not retrieving any additionally added select columns. The getSearcherAPI() API call populates it. And I read that its best practice to use this search rather than customizing the actual search itself.

As the "DATA-CUSTOMPROPERTIES-SEARCH" instances works only when called from pxRetrieveSearchData, which will be called only from the actual search itself.

Thanks for the reply anyways :)

Any insight on the API call would be very helpful.

May 21, 2018 - 8:16am

I have following questions on the requirement.

1. is it quick search or advanced search? where you want to give this option of search.

if it is quick search, it is already free text search.

if it is advanced search - then  you have to build the query and set the following values , before the RD is called.



eg: param.pySearchMethod - EXACT / contains

param.pySearchString - "ColumnName:*"+.value +"*"


Gouri Shankar K


December 24, 2018 - 12:55pm

Hello, has anyone attempted to build query params (using pySearchWorkParams) in such a way, to use OR clause for search params?

Refer to the main post here.

December 24, 2018 - 12:59pm
Response to BalajiS6010

This is an older post and hasn't had any activity for a few months. Thank you for posting your question as a separate post. Please continue the discussion there.

Thank you!

Marissa | Community Moderator | Pegasystems Inc.