Question
Cognizant Technology Solutions
US
Last activity: 9 Aug 2016 3:11 EDT
How to show selected properties in Data explorer for developer operator?
Only users with check-out privilege can create reports in public categories. As part of our current release, we have a requirement that says "Site admins (A set of users) should be able to create reports in public category so that the other users should be able to use them." So, we gave enabled check-out option on all the Site admin's operator IDs.
We have another requirement which says that all the users, including Site Admins, should be able to see only a set of properties in the data explorer. We implemented the functionality using the data transform pyReportEditorProperties as suggested in the post https://docs.pega.com/customize-lists-properties-and-calculations-available-report-editor . Now, as the Site admins have check-out privileges, they are not able to see just the set of properties configured using pyReportEditorProperties. These users see all the properties including the Pega properties and they found is confusing. So now we need a solution to one of the below two questions in order to achieve both the requirements.
1. Is there a way users can create reports in public categories without requiring the check-out privilege?
2. Or is there a way we can enforce the list of properties that appear in the data explorer even for users with check-out privilege?
Only users with check-out privilege can create reports in public categories. As part of our current release, we have a requirement that says "Site admins (A set of users) should be able to create reports in public category so that the other users should be able to use them." So, we gave enabled check-out option on all the Site admin's operator IDs.
We have another requirement which says that all the users, including Site Admins, should be able to see only a set of properties in the data explorer. We implemented the functionality using the data transform pyReportEditorProperties as suggested in the post https://docs.pega.com/customize-lists-properties-and-calculations-available-report-editor . Now, as the Site admins have check-out privileges, they are not able to see just the set of properties configured using pyReportEditorProperties. These users see all the properties including the Pega properties and they found is confusing. So now we need a solution to one of the below two questions in order to achieve both the requirements.
1. Is there a way users can create reports in public categories without requiring the check-out privilege?
2. Or is there a way we can enforce the list of properties that appear in the data explorer even for users with check-out privilege?
We found that we can modify some rules to achieve this, but the rules are final. Example: pzPrepareReportExplorerFieldNames
***Updated by moderator: Brendan. Removed user added Group Tags. Apologies for confusion, shouldn't have been an end-user option.
Accepted Solution
Pegasystems Inc.
US
Sorry Ravikanth, currently there isn't a way to change the sharing criteria. I'll raise this as an issue and see if we can add the ability to customize how reports/categories are shared in a future release.
Telstra
AU
1. I think asnwer is "No"
2. Yes
Trace when all the properties get loaded, see any activity/data transform which isn't Final so that you can use that activity/data transform to filter out what you don't need.
Pegasystems Inc.
US
1. You can but they will only be shared among those users in the same access group. Do the users need to share reports accross access groups?
2. There currently isn't. If the user has checkout priviledges, then the full list will be shown
Cognizant Technology Solutions
US
@ Abhijith
Thanks Abhijith! We will have to override many final rules, if we want to achieve it. It may not be a good idea, as our application goes through upgrades frequently.
@ Mike
Thanks for the response. We checked the "Shared categories" option (it is difficult to notice on Pega 7). But, it has a limitation that the categories can be shared among users of the same access group. But our requirement is that the category should be shared across access groups based on the pyOrgDivision. i.e. all the operators with the same pyOrgDivision should be able to access the reports in the category. Is there a way we can change the sharig criteria from access group to division?
Accepted Solution
Pegasystems Inc.
US
Sorry Ravikanth, currently there isn't a way to change the sharing criteria. I'll raise this as an issue and see if we can add the ability to customize how reports/categories are shared in a future release.