Best approach to set visibility (or access rights) to Report Definition
Hi,
I have a very simple requirement to implement.
I want to create a report definition which may show some sensitive information.
The business unit would like to use this report by their own only. Nobody, except from them, shouldn’t run or even see the report.
I have worked with category and placed this Report Definition in a private (and also shared) category. I have setup the when rule and the visibility of the category works ok but the report can be seen when the users (some of them has this capability) clicks on the show all categories. Even If the category is invisible, the report def can be reachable by doing that.
What is the best way to implement such requirement ? I really dont want to dig that List View (the one lists all the reports to the portal) ...
Probably I am missing a point ...
What do you think ?
Thank you
Pegasystems Inc.
IN
You may try specifying the privilege on the ReportDefinition's DataAccess Tab.
Of course we can't restrict the report name from displaying in report browser but no content will be displayed unless the users have this privilege.
Pegasystems Inc.
NL
Hi Shashidhar
Thanks for reply
I have seen that privilege settings but I am not on expert on this.
I guess I need to create a privilege and associate this with access role. To do that I need to create an access role and select that privilege. In the access role I can define a class and set the operation & levels on that. Then .. I think I need to associate my report definition with a when rule on operation zones
That may sound confusing or even wrong for you as I am only guessing :)
What should I do actually do you have document, link or anything to clarify what and how to do ?
Thank you
.
,
Pegasystems Inc.
IN
The first part you mentioned is same as what I did. There is no need of any when rule.
1) Create a Privilege rule first.
2) In the intended access role add a new access class. If the class is already existing open it and add the newly created privilege. If it's new class, define the access controls as needed.
3) Add the privilege.
4) Save the report definition with the privilege selected.
5) Logoff and Login for the changes to take effect.
I checked these at my end and when I login as a user with no mapping to the ARO, I can see the report name but when run below error message is observed.
I've attached the steps I followed.
Pegasystems Inc.
NL
Hi Shashidhar,
Thanks for the detailed steps and explanations.
I have two problems for this approach ... one them is pretty weird though....
The first screen shot you put in the documents shows the initial privilege creation page. You have three tabs as Roles, Specifications and History ...
When I try to create a role, I only have two tabs. Specification tab is missing. Possible root cause of this should be a missing role on my operator. I am searching for it but couldnt find it yet.
The second problem is the class of my report definition. When you create a privilage you then access to a class. The report definition belongs to Work class in my case. I am not sure but ı guess there is chance of restricting the access of the others If I define an ARO as you did in your screen shot. Am I correct ?