Error message from modifying cloned widget
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2025 08:40 PM
I'm having weird issue with cloned widget on EC Pro Yokohama.
I'm using the Dev instance I got from developers.servicenow.com.
Here are the steps I went through:
- Cloned OOB Header widget from Service Portal > Headers & Footers, under same application scope as the original widget
- Use the cloned widget in the Portal
- Modify HTML or CSS of the cloned widget, save
- Go to the Portal, refresh the page, error messages show up
The first error message says "Execute operation on script include 'cd_CompanyEventCacheManager' from scope 'Employee Center' was denied. The application 'Employee Center' must declare a cross scope access privilege. Please contact the application admin to update their access requests."
I've been fixing this by
- Go to Restricted Caller Access Privileges
- Find the ones that have Invalidated status
- Manually change the status of all Invalidated to Allowed
This resolves the issue, but it comes back the next time I make another change to the cloned widget.
Is there a way to fix this permanently?
And why is this happening? Did I do something wrong during cloning?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
I have the exact same issue, and not a single response from the community or a ServiceNow employee after 7 months. Oh well, support ticket it is.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
I know it's bit late to this, but I did find out why this was happening.
The OOB Header widget has several ACL that works with it, and when I cloned it the cloned version is disconnected from those ACL.
The solution is to read the error message and create ACL for each error seen.
Our team decided this solution is not practical as we don't know how many ACL will need to be created, so we decided to use the OOB Header widget as is.