Support Article
Report Definition in Framework Class behaves incorrectly
SA-11300
Summary
The scenario involves class structure hierarchy as follows:
MyCo-FW-CaseFW-Work ( this is a Framework)
- MyCo-FW-CaseFW-Work-Cover-
- MyCo-FW-CaseFW-Work-Object-
Created two classes in the implementation layer
- MyCo-GCS-Work-Profile inherits MyCo-FW-CaseFW-Work-Cover-
- MyCo-GCS-Work-Account inherits MyCo-FW-CaseFW-Work-Object-
And then created a ReportDefinition in the MyCo-FW-CaseFW-Work-Object-, this ReportDefinition has "Report on descendant class instances" checked.
If we select the WorkPool representing MyCo-GCS-Work-Profile . The Report Definition generates the below queries and provide the WorkItem of Profile class. The SQL is getting generated from the current work pool.
SELECT "PC0".PYID AS "pyID" , "PC0".PZINSKEY AS "pzInsKey" FROM PRPC716.pc_MyCo_GCS_Work "PC0" WHERE "PC0".pxObjClass LIKE ? Query Parameter: MyCo-GCS-Work-Profile
To get the WorkItem from MyCo-GCS-Work-Account, we need to change the WorkPool to MyCo-GCS-Work-Account.
This seems to be an incorrect behavior.
Error Messages
No error, incorrect results.
Steps to Reproduce
1. Create a Report Definition under an abstract class in Framework layer.
2. Have Report on descendant class instances" checked.
3. Run the Report Definition, it reports on the workpool and not on the inheritance class.
Root Cause
This is an expected behavior:
· If a report is defined on abstract class (inherited from Work-), it reports on the workpool by default. Even if the Report on descendant class instances" is checked.
· If a report is define on the Framework class and has “report on descendant classes” checked, it reports on the Implementation class in the current application for that Framework class.
Resolution
A documentation bug has been raised to include the the below point:
· If a report is defined on abstract class (inherited from Work-), it reports on the workpool by default. Even if the Report on descendant class instances" is checked.
- FDBK-11728 has been created as an Enhancement Request for Product Owner to evaluate.
When we have a RD in Abstract class with " report on descendant classes” checked. The RD should not report on the class which is not in the descendant path even if the reports are pulled according to the Workpool, this is a wrong behavior.
Published July 17, 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.