
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
10-16-2022 09:17 PM - edited 08-03-2024 05:11 AM
Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
Hi there,
Did you notice with Employee Center, when you update the Employee Center Header, suddenly several errors appear when loading Employee Center? And even when you revert the changes made, the errors won't disappear? Let's have a look at how can we fix these errors.
Cross scope access privilege
After updating the Employee Center Header with anything, errors like these will appear when loading Employee Center:
The exact reason why this occurs every time you update the Employee Center Header, I haven't found out yet. Though how can we fix these errors? Basically, there are two situations:
1. The Restricted Caller Access Privilege record does not exist
2. The Restricted Caller Access Privilege record is in a Status other than Allowed
Update Status Restricted Caller Access Privilege record
First have a look if the Restricted Caller Access Privilege record already exists. Navigate to:
System Applications > Application Restricted Caller Access
Then search for:
- Operation = Execute API (the first error mentions "Execute operation")
- Target = Script Include: todoPageUtils (the first error mentions "on script include 'todoPageUtils'")
- Source = Widget: Employee Center Header (the last error mentions "Employee Center Header", which of course is the Widget you updated)
If you find a match, have a look at the Status of the Restricted Caller Access Privilege record. Most likely the Status is "Invalidated" or "Requested". Make sure you are in the correct Application Scope (Employee Center Core), and update the Status to "Allowed".
After solving this error, it can happen that you run into a new error. For example:
Just repeat the previous steps followed. Search for Restricted Caller Access Privilege:
- Operation = Read (the first error mentions "Execute operation")
- Target = Table: sn_hr_integrations (the first error mentions "on table 'sn_hr_integrations_todo_inbound'")
- Source = Widget: Employee Center Header (the last error mentions "Employee Center Header", which of course is the Widget you updated)
If you find a match, have a look at the Status of the Restricted Caller Access Privilege record. Most likely the Status is "Invalidated" or "Requested". Make sure you are in the correct Application Scope (Employee Center Core), and update the Status to "Allowed".
Adding Restricted Caller Access Privilege
If searching the Restricted Caller Privilege record does not give any results, you would need to add the record yourself. This can be a bit of a struggle. So let's try to break down the error messages because these do actually contain all information needed to create a Restricted Caller Privilege record.
I will start with the fields on the right-side column, based on the error messages from the first image:
- Application = This is automatically filled, based on the active Application Scope. This should be the same Application Scope as the Target record is in.
- Target Scope = This should be the same Application Scope as the Target record is in.
- Target Type = The first error message mentions "Execute operation on script include 'todoPageUtils'". The Target type therefore should be Script Include.
- Target = The first error message mentions "Execute operation on script include 'todoPageUtils'". The Target therefore should be Script Include: todoPageUtils.
- Operation = The first error message mentions "Execute operation on script include 'todoPageUtils'". The Operation therefore should be Execute API.
- Source Scope = This should be the same Application Scope as the Source record is in.
- Source Type = The last error message mentions "Failing widget: 'Employee Center Header'". The Source type therefore should be Service Portal Widget
- Source Table = This is automatically filled, based on the Source Type.
- Source = The last error message mentions "Failing widget: 'Employee Center Header'". The Source therefore should be Widget: Employee Center Header (which of course is the Widget you updated)
- Status = Allowed
Result
After following the steps above, the error messages while loading Employee Center should not appear anymore and the Employee Center Header should be visible again.
---
Hope you like it. If any questions or remarks, let me know!
C |
If this content helped you, I would appreciate it if you hit bookmark or mark it as helpful.
Interested in more Articles, Blogs, Videos, Podcasts, Share projects I shared/participated in? |
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
3x ServiceNow Developer MVP
3x ServiceNow Community MVP
---
- 16,198 Views

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi @Mark Roethof , I recently ran into these errors and able to resolve those. Did you get an opportunity to find why these errors occur every time we update Employee Center Header widget (or why the restricted caller access privilege records status move back to Invalidated) ?
Thanks!

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
I had a recent Support Case on this. Works as designed 😞
Kind regards,
Mark

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Oh no, that is strange. Thanks for your response.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Thanks Mark for writing this post. I logged in to community just so I can give you thumbs up!
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Had this issue after upgrading from Tokyo to Utah Patch 4 Hot Fix 2.
Your workaround worked!
Any idea when ServiceNow will release the fix in an official patch??
Thanks!

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Nice post @Mark Roethof . Definitely a consideration folks need to take into account when looking to customize the Header.
@JSchmauch This isn't an issue or bug that needs to be addressed. The idea of Employee Center is bring departments and business units together into one experience. These errors happen, typically, because of application access restrictions to the HR module and application.
@Vamsi Sreenivas HR has a number of restricted caller setups and app calls that require approval, as HR can contain sensitive data. As Employee Center ships with our assets already structured and approved for this, when you make changes to the Header, it requires you action these restricted caller requests fresh.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Thank you so much. I almost had heart failure this morning when this happened to me.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Great post! I had to log in, too so I could like and comment. All I did was change a color in the CSS and this happened. I think this works as designed because I jump back and forth between scopes all the time when working in the Employee Center (from Employee Center to Employee Center Core). But the scoping in the Employee Center does not work as designed, and thats where everything got messed up. ServiceNow should clean the scoping up in one of the next patches.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Thank you very much...GREAT POST!!
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
This worked for me. Thank you for sharing the information.
Although the error re-occurred after 2 days I am not sure why. The restricted access went to invalidated automatically. I have cloned the header and did the updates in dev instance and then Allowed the restricted caller access privilege.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Thank you very much, it was very helpful, although it is pending for Service Now to solve this small problem 🙂