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

Report search condition default value even after customization

SA-12411

Summary



The scenario involves customization of section as report condition. When same section is used in different reports, condition value is not cleared when report is closed.
On opening another report configured with same custom section, same filter value was displayed, the requirement was not to hold the value.


Steps to Reproduce



1. Create multiple reports.
2. In the report viewer tab of report definition rule, check the "Display filters using custom section".
3. Configure the custom section with property mapped to filter criteria.
4. Execute the first report and input any filter data.
5. Close the report window.
6. Again, run another report. Observed that the value 
entered in the filter criteria of first report is retained.

Root Cause



The use case has the same custom filter section in multiple reports opened under the session. Also, the same page name is defined on all the reports under ‘Page and Classes’ for the class the custom section applies to. With these settings, open reports refer the same clipboard page (created under standard thread) to access the criteria/filter data. Hence the fields in custom criteria section are populated (referring the existing clipboard page) as soon as the report is open.

Resolution



This issue is resolved through the following local-change:
 
Define different page names for different reports (Under "Pages & Classes" tab of report definition rule) for the classes the custom criteria section applies to.

Published July 24, 2015 - 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