Question

4
Replies
288
Views
Shankar Krishnamurthy (ShankarK5519)
American Express

American Express
US
ShankarK5519 Member since 2015 1 post
American Express
Posted: December 6, 2016
Last activity: December 9, 2016
Posted: 6 Dec 2016 9:29 EST
Last activity: 9 Dec 2016 1:57 EST
Closed
Solved

Search not returning Impl layer columns

We have a requirement to customize the results of the OOTB Search results. We are using Pega 7.1.7. We have referred the following PDN article: 
https://pdn.pega.com/community/pega-product-support/question/full-text-search-work-objects-how-add-columns-data-search 
Specifically the post by Rajiv: 
In that case, I suggest you modify to gadget to call your own report definition instead of the one that is called by the gadget out of the box. Note that, if you are searching across different work classes and want to return different properties for different classes, then that is not feasible unless you run different search queries and show the results using your own custom UI. 

We have overridden the pyWorkSearch Report Definition, Section and Data page to try and achieve this. The Search functionality is still only executing the Work- version of the report definition and not fetching the columns in the implementation layer. The specific issue is in the pzSearch activity. In our case it is executing the distributed Search step (Step 1):


-----------------------------------------------------


try {


    pega.getSearcherAPI().search(myStepPage, tools.getParameterPage(), tools.getThread());


}


catch(com.pega.pegarules.priv.search.nextgen.FTSException fe) {


    oLog.error(fe.getMessage());


}

We have a requirement to customize the results of the OOTB Search results. We are using Pega 7.1.7. We have referred the following PDN article: 
https://pdn.pega.com/community/pega-product-support/question/full-text-search-work-objects-how-add-columns-data-search 
Specifically the post by Rajiv: 
In that case, I suggest you modify to gadget to call your own report definition instead of the one that is called by the gadget out of the box. Note that, if you are searching across different work classes and want to return different properties for different classes, then that is not feasible unless you run different search queries and show the results using your own custom UI. 

We have overridden the pyWorkSearch Report Definition, Section and Data page to try and achieve this. The Search functionality is still only executing the Work- version of the report definition and not fetching the columns in the implementation layer. The specific issue is in the pzSearch activity. In our case it is executing the distributed Search step (Step 1):

-----------------------------------------------------

try {

    pega.getSearcherAPI().search(myStepPage, tools.getParameterPage(), tools.getThread());

}

catch(com.pega.pegarules.priv.search.nextgen.FTSException fe) {

    oLog.error(fe.getMessage());

}

This populated the Search results page which only has the handful of Work- Columns in the OOTB pyWorkSearch RD. I have detailed all the steps followed in the attached document. Please review and let us know how we can achieve custom implementation columns in the full text search results.

Low-Code App Development Data Integration Java and Activities Support Case Exists
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.