Support Article
Data page reference interpreted as string literal
SA-25705
Summary
Report Definition rules do not require a developer to specify the class of a data page used for filtering on the Pages & Classes tab. However, if a data page is referenced but not added to the Pages & Classes tab then the data page reference is interpreted as a string literal by the engine.
Error Messages
Not Applicable.
Steps to Reproduce
- On any Pega 7.2 system create a report definition in the PegaSample class.
- Add .pyID as a column.
- Add a filter with a data page reference like: .pxObjClass Contains Declare_AppExplorerData.pyAppExplorerWorkPool.
- Run the report and review results.
Root Cause
The engine interprets the filter expression as a string literal if the data page is not included on the pages and classes tab of the rule form.Resolution
In this example, adding "Declare_AppExplorerData" / "Code-Pega-List" to the Pages & Classes tab resolves the issue.
A product enhancement to provide a guardrail warning for this issue is being considered by product management.
Published July 28, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.