Employee Center (ESC) read access errors after Vancouver Patch 7 Hot Fix 2b upgrade

Takefumi Muto
Giga Guru

Hi everyone in the community!


For the first time since implementing HRSD, I've conducted a patch update in Vancouver. However, I encountered five errors and I can't figure out the cause.

JackBook_0-1718015041919.png

 


・Error Read operation on table 'sn_ja_task' from scope 'Employee Center Core' was denied. The application 'Employee Center Core' must declare a cross scope access privilege. Please contact the application admin to update their access requests.
・Error com.glide.script.fencing.access.ScopeAccessNotGrantedException: read access to sn_ja_task not granted
・Error Script source code logged to console
・Error Failing widget: 'Employee Center Header' (d0009941eb103010ed7966d6475228c1)
・Error Read operation on table 'sn_ja_task' from scope 'Employee Center Core' was denied. The application 'Employee Center Core' must declare a cross scope access privilege. Please contact the application admin to update their access requests.

I'm aware that similar issues occurred in the past with the Rome version, but I'm not sure if this is the same problem. Employee Center (ESC) read access errors after Rome upgrade

If anyone has experienced the same issue in Vancouver as in the Rome version or can offer assistance, I'd greatly appreciate it! Thanks to everyone in the community!

1 ACCEPTED SOLUTION

Takefumi Muto
Giga Guru

I have solved the problem and will write it down!

<Cause>
Disabling Restricted Caller Access Privileges
The update to the script include "todoPageUtils" caused the Restricted Caller Access Privileges of source "todoPageUtils" to be disabled.

<Fix>
Corrected the Restricted Caller Access Privileges for the affected source to allow.

View solution in original post

4 REPLIES 4

Kieran Anson
Kilo Patron

Hi Jack,

you need to create a cross scope access record. You can go to the module 'Application Restricted Caller Access' and there may be a record in there with a status of 'requested'. Otherwise you can create the access policy manually

https://docs.servicenow.com/bundle/washingtondc-application-development/page/build/applications/task... 

This method solved my issues. Thanks.

 

Glad it helped!

Takefumi Muto
Giga Guru

I have solved the problem and will write it down!

<Cause>
Disabling Restricted Caller Access Privileges
The update to the script include "todoPageUtils" caused the Restricted Caller Access Privileges of source "todoPageUtils" to be disabled.

<Fix>
Corrected the Restricted Caller Access Privileges for the affected source to allow.