Question
1
Replies
211
Views
Posted: August 2, 2019
Last activity: August 5, 2019
Closed
Pega 7.4 Access Deny for Rules of a class is not effective
We have a requirement to deny access to harness, sections and other rules of a particular class to a particular Access role. We tried to implement this by defining Access Deny rule to deny all rules of this class. The rules are denied if the user with this access role try to open the rules directly in Designer studio. However, the harness and sections are loaded and rendered in Casemanager portal from CasemanagerLinks Menu.
The requirement is to show the menu but throw error if the user cannot access the Menu. Hence hiding the menu based on privilege from CasemanagerLinks navigation rule is not of much help here.
It would be of great help if anybody who have handled similar requirement share their knowledge.
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Hi @SudhaS14
You can achieve this feature by implementing Access of Role to Object(ARO). And by defining a role for the user to to restrict.
For that Need to create following rule :-
Step 1 : New Access Group: To be reference to an operator ID whom u need to restrict
Step 2: New Role : to be referenced in the Access Group for Step 1
Step 3 : New ARO instance :- it will ask for the Role and Class to restrict (By providing valid input 0 is for no Access 5 is for full access)
Step 4 : Reference the Access group to an operator whom you want to restrict.
Note: If the Operator is having any Role which provide the Access to the Class than your ARO will be overruled and it will not work.
Hope this will work for you.