Restricted Caller Access Errors – Status Showing as Requested

[manthenamah]

Hi everyone,

We are getting these three errors, and they appear to be related to Restricted Caller Access.

Can we change the Restricted Caller Access status from Requested to Allowed to resolve these errors? If so, is this the recommended approach, or is there a better solution?

Any guidance would be appreciated. Thank you!

[Shruti]

I would recommend changing the Restricted Caller Access status from Requested to Allowed. Once the status is updated to Allowed, please retest the affected functionality and verify whether the errors are resolved.

[Tanushree Maiti · Accepted solution]

Hi @manthenamah 

1)

• Naviagete to your ServiceNow navigation filter and type sys_restricted_caller_access.list
• Filter the list using these conditions:
• Source Scope: Global
• Target Scope: Human Resources: Core (sn_hr_core)
• Target Name: sn_hr_core_case
• Operation: read
• Open the matching record that is currently in a Requested or Denied state.
• Change the Status field to Allowed.
• Click Save or Update.
• If no record exists, click New, fill in the exact field values listed above, set the status to Allowed, and save.

2) Refer: Execute operation on script include 'hr_caseOpenRequestFilterUtil' from scope 'Global' was denied.