Support Article
Associations not working with Include Implementation class only
SA-37355
Summary
Associations not working with Include Implementation class only option.
A Report Definition is configured to report on descendant classes, and also uses an association to join to another (work) class.
When the report is run at the implementation layer, the association does not dynamically change to use the implementation class, but continues to use the framework class defined in the association.
For example a report configured in the Framework to report on descendant classes that uses an association:
Framework class is used by association when running in the context of an implementation.
Main report class correctly changed to implemenation dynamiclly.
Error Messages
No error messages. Framework class is used for the association when running the report in the context of an implementation.
Steps to Reproduce
- Create report definition using Associations using Report on descendant class instances.
- Include Implementation class only option.
Root Cause
Association rules are not curently supported for use with reporting on descendant classes.
This issue was determined to be a product enhancement request.
Resolution
An enhancement request, FDBK-19302, has been created for consideration by Pega Product Management.
Local-change solutions
- If an association rule is required then save the association rule into the implementation class.
- Otherwise a class join can be used instead of an association.
Published May 15, 2017 - 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.