Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Extending complaint search parameters

Updated on January 18, 2021

You can extend the search for submitted complaints by adding more search parameters. For example, add the submitter's phone number as another search filter.

  1. In the Dev Studio Explorer panel, click Data.

  2. Click the Option Map data type.

  3. On the Records tab, at the bottom of the list of records, click Add record.

  4. Add a record with SearchCriteria in the Field name / Group field.

    For example, add Phone number as a new search parameter.

  5. Search for and open the SearchCriteria section of the PegaPS-Data-Complaint class.

  6. Add the new search parameter to the section.

    For more information about modifying sections, see Sections.

  7. Create a when rule in the PegaPS-Work-Complaint class that verifies whether the new parameter is equal to the Param.SearchType value.

    For example, Param.SearchType EQUALS "New search parameter".

    For more information about creating when rules, see When condition rule - Completing the New or Save As form.

  8. Create a report definition rule in the PegaPS-Work-Complaint class for the new parameter.

    Use a report definition rule for an existing search parameter in that class as a model, for example, ComplaintsFilingPerson.

    For more information about creating report definition rules, see Creating a report definition.

  9. Search for and open the D_ComplaintDetails data page.

  10. On the Definition tab, update the Data sources section with the new when rule and the new report definition rule.

    For more information about modifying data pages, see Data page rules - Using the Definition tab.

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us