Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

OOTB Search does not work for descendant class work objects



When a Search string belongs to descendent class work objects stored in a separate table (as per design requirements), the out-of-the-box pxRetrieveSearchData Search activity does not display results.
However, the report passed as a parameter to this activity works correctly when the 'Include all descendant classes' checkbox is enabled. Hence, results display when a Search string is entered for the descendant class work objects.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a child work type class which is defined as a class group in the main work type 
  2. Use the out-of-the-box pxRetrieveSearchData Search activity and pass the parameters as below:

    ReportName - pyWorkSearch 
    CaseTypeList - All 
    TypeOfWork - All work 
    IncludeAttachments - Work items only 
    UpdatedOn - Anytime 
    ReportClass - <The Parentclass>  
    pyMaxResults - 20 
    SearchString - <Child work object id> 

  3. Include both the Implementation classes (that is, the child work type and the main work type) in the Application Rule Definition for each client.
  4. Launch the portal.
  5. Enter a Search string. 
  6. Click the magnifying glass or press the Enter key.

Root Cause

According to the pxRetrieveSearchData activity design, when the Search query is executed, a condition is created automatically as the below criteria:
  • If the class specified by pyReportClassName is Concrete and not a Workpool, use the class as is (which occurs in the current scenario). If the class is Concrete and a Workpool, all classes that start with the class name are searched.
  • If the class specified by pyReportClassName is 'Rule-' or 'Data-Rule-Summary', all the Rule types are searched.
  • If the class specified by pyReportClassName is 'Data-', all the Data types are searched.
  • If the class specified by pyReportClassName is 'Work-', all the Work types are searched.
  • If the class is Abstract and is not one of the above cases, an error message is displayed to the Code-Pega-List page. Search reports can only be defined on a Concrete class, or on one of the following abstract classes: Work-, Rule-, Data-, and Data-Rule-Summary.


Perform the following local-change:
  1. Move the report definition to a parent class which is a Work Group (not belonging to a work group).
  2. Add an entry in the Keys section of the child class definition (pyID as Name and ID as Caption).

Published March 27, 2020 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us