Error when loading new Employee Center Portal: Execute operation on script include 'todoPageUtils' from scope 'Employee Center Core' was denied. The application 'Employee Center Core' must declare a cross scope access privilege. Please contact the ap

[tj26]

Hi ServiceNow Community,

I'm hoping someone can help me. I am testing the Employee Center portal in a developer instance, I have created a new portal and cloned the following pages:

• HomePage: ec_dashboard > custom_ec_dashboard
• KB home page: esc_knowledge_home > custom_esc_knowledge_home
• Catalog Home Page: esc_sc_category > custom_esc_sc_category

When I load the new portal I have created, I get the following error across the top of the page:

"Execute operation on script include 'todoPageUtils' 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."

Has anyone else experienced this issue? If so, can you please provide detailed information on how you resolved it?

Thanks

[Mark Roethof]

Hi there,

Any follow-up needed? Or was my answer sufficient?
Let me know.

If your question is solved, please close the topic by marking my answer as correct. This will help others searching for a similar question and will remove the topic from the unsolved list.

Kind regards,
Mark
2020-2022 ServiceNow Community MVP
2020-2022 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list

[Palash_Sarkar]

Hi all
I'm facing the same issue with the "Utah" release, but thanks to Mark Roethof for providing the solution, the issue has been resolved. I have configured the following: I hope someone who faces the same problem can help them.

1. Go to All >> Navigation>> and search for "Application Restricted Caller Access" menu to open the list.
2. Filter out the status field with "Allowed" and you will see the list of Invalidated records.

3. Change those records' status to Allowed.

4. Reopen your Employee Center portal for confirmation.

[Vinicius Olivei]

Updating the corresponding entry in the sys_restricted_caller_access table solves this issue.