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

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

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