How to expose WorkParty property for reports
Hi,
We have a requirement to show some properties which are in Data-Party class on reports.For example WorkParty(Assignee).pyFullName and WorkParty(Approver).pyFullName
Since those properties are not exposed as DB table columns , so the reports get poor performance of course.
I tried to use optimization tool but it doesn't work, because the Data-Party class is an abstract class.
Could anyone tell me how to expose those properties or is there any other approach to improve report performance with unexposed properties?
Thanks
***Moderator Edit: Vidyaranjan | Updated Categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Coforge DPA
GB
Hi
There is already Declare Index for the .pyWorkParty() page and "Index class to write" is index-WorkPartyUri. So that you can get the work party details in report by joining with index-WorkPartyUri class, Joining condition could be the pxInsIndexedKey of index-WorkPartyUri class and pzInsKey of Your Work Class.
Thanks,
Nagesha DV.
Accenture
JP
Hi,
I tried to join Index-WorkPartyUri class in our reports and it works very well.Thank you very much for the suggestion.
But there is an another issue is that, actually, in order to show the WorkParty Operator's Department information on reports, we added a Single Page property called "OperatorID" in Data-Party class, which Page definition is Data-Admin-Operator-ID. And get the data through .pyWorkParty().OperatorID.pyDepartment. I think it is also needed to add this property in Index-WorkPartyUri class and expose it to column perhaps. But PRPC is not allowing to expose property in Index-WorkPartyUri class by Property Optimization For Report.
Is it possible to expose this department property maually, or has any other way to solve this inssue?
Accenture
JP
I resolved this issue by exposing Data-Admin-Operator-ID.pyDepartment property to DB (Since this class is a Pega shipped class and Pega also not allowing to expose property, I alter PR_OPERATORS table manually by adding column with same name "PYDEPARTMENT" and resaved DB-Table instance , as a result it works well ).And then joined Data-Admin-Operator-ID class to our RD. Now reports get Department data from PR_OPERATORS table PYDEPARTMENT column instand of BLOB, and report performance is been improved
Pegasystems Inc.
IN