Support Article
pxRetrieveReportData not behaving the same after upgrade to 717
SA-8032
Summary
When calling report definitions from a customized pyPopulateCaseContent activity (pyWorklistAssignmentDefinition and pyWorkBasketAssignmentDefinition), there is an "Invalid report content page specified" error written to the logs and the activity fails.
Tracing the activity shows an error "Report Content Page does not exist or refers to an invalid class" in Pega 7. However, the same activity has no error in 6.2 SP2.
Error Messages
"Invalid report content page specified"
Steps to Reproduce
Create a new work object.
Root Cause
The root cause of this problem is a defect in customer application code/rules.
Resolution
This issue is resolved through the following local change: recreating the customizations of the activity in Pega 7 (as opposed to using the 6.2 SP2 version) resolved this issue.
Published June 12, 2015 - 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.