ACL rule for Approvers to see RITM variables on the Portal or Instance

Peter Williams
Kilo Sage

Good day,

i am looking for an ACL rule on the sc_req_item - READ so that approvers of the RITM is able to see the variables from the RITM request they are approving.

This can be from the portal, mobile or in the fullfiller view.

 

so far i have created a ACL Rule for SC_REQ_ITEM Read on Requested_For is Dynamic (to Me) to see the users request.

Looking for something similar to Approvers of the request

1 ACCEPTED SOLUTION

DrewW
Mega Sage
Mega Sage

Last I checked, there was an OOB ACL that used a script
answer = new ApproverUtils().canApproversRead();

which allows the user to read the row when they have an approval for it which should give them all the access they need to view the variables.

 

View solution in original post

4 REPLIES 4

DrewW
Mega Sage
Mega Sage

Last I checked, there was an OOB ACL that used a script
answer = new ApproverUtils().canApproversRead();

which allows the user to read the row when they have an approval for it which should give them all the access they need to view the variables.

 

Amit Gujarathi
Giga Sage
Giga Sage

HI @Peter Williams ,
I trust you are doing great.

To create an ACL (Access Control List) rule for sc_req_item in ServiceNow, allowing approvers of the RITM (Request Item) to see the variables from the RITM request they are approving, you can indeed use a scripted solution similar to what you mentioned.

The approach DrewW suggested is on the right track. Using ApproverUtils().canApproversRead() is a common and efficient method. This function checks if the current user is an approver for the item and grants read access if they are.


Was this answer helpful?


Please consider marking it correct or helpful.


Your feedback helps us improve!


Thank you!


Regards,


Amit Gujrathi



Peter Williams
Kilo Sage

so i saw that OOB rule already but what happen by default its sc_req_item.None
i had to modify it to how sc_req_item.* for the read.

Then it finally worked

 

 

You should leave the default rule as sc_req_item.None and add a second ACL for the sc_req_item.*.  It may save you grief down the road.