- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-27-2020 11:58 AM
I'm trying to figure this out but I can't seem to find answers in the usual places.
I'm looking to customize the header menu in the Employee Service Center page. I'm looking to remove and add as needed but I can't seem to find the right method to do so.
- I'm looking to remove the To-dos and the Cart (if needed) and modify the Requests to point to custom page instead of the OOB page.
- I've tried cloning this header but I get cross scope errors and a whole set of other errors with it. Are headers not meant to be cloned?
- Additionally, how would I get the portal to use custom pages? Would that be defined in the header code?
Solved! Go to Solution.
- Labels:
-
Service Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-15-2020 04:00 PM
ServiceNow got back to me to indicate that there's value that must be changed in the Restricted Caller Access Privilege table.
After the widget is cloned, it creates a record on this table under the widget's name as Source
You must set the Status option from "Requested" to "Allowed". This seems to resolve the cross scope error messages.
The below is the OOB record for the ESC Header prior to cloning (for reference). Find the record with your cloned widget and change the value in the correct scope. This corrected the issue for my situation and may save you some time if you're cloning widgets and run into this error.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-27-2020 12:15 PM
Hi,
Kindly find my comments below.
- I'm looking to remove the To-dos and the Cart (if needed) and modify the Requests to point to custom page instead of the OOB page.
- [Jaspal]: You need to clone the header & comment the To-do part from the code.
- I've tried cloning this header but I get cross scope errors and a whole set of other errors with it. Are headers not meant to be cloned?
- [Jaspal]: That is not the case. You can modify it just make sure you are cloning the widget in the same scope that it is actually created in. Instead of cloning header did you check for HR Theme. If not, you can look for Service Portal >> Portals >> Employee Service Center & then look for Theme from which you can look for HR Header & then clone & modify/comment required set of options that you want not to be shown.
- Additionally, how would I get the portal to use custom pages? Would that be defined in the header code?
- [Jaspal]: Not required to be defined anywhere. You can use it like you use normal pages in Global scope.
Thanks,
Jaspal Singh
Hit Helpful or Correct on the impact of response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-27-2020 12:46 PM
- [Jaspal]: That is not the case. You can modify it just make sure you are cloning the widget in the same scope that it is actually created in. Instead of cloning header did you check for HR Theme. If not, you can look for Service Portal >> Portals >> Employee Service Center & then look for Theme from which you can look for HR Header & then clone & modify/comment required set of options that you want not to be shown.
I've created a custom portal and copied the ESC Theme as is (no modifications other than the name). The header I chose to clone was ESC Header which is used on the OOB ESC page. The cloned header is in the correct HR service portal scope. The errors are related to cross scope and widget failuresIs there another place I need to be aware of to clone for me to be getting these errors?
- [Jaspal]: Not required to be defined anywhere. You can use it like you use normal pages in Global scope.
Just for clarification, if the Requests link in the header points to a page called "my_requests" and I want to point it to a custom page "custom_my_requests", would I have to change it in the header to replace "my_request" to "custom_my_requests" in the code?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-15-2020 04:00 PM
ServiceNow got back to me to indicate that there's value that must be changed in the Restricted Caller Access Privilege table.
After the widget is cloned, it creates a record on this table under the widget's name as Source
You must set the Status option from "Requested" to "Allowed". This seems to resolve the cross scope error messages.
The below is the OOB record for the ESC Header prior to cloning (for reference). Find the record with your cloned widget and change the value in the correct scope. This corrected the issue for my situation and may save you some time if you're cloning widgets and run into this error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2020 06:18 PM
Hi,
I was stuck with the same error but this is helpful. I still have a issue as i see the same errors again after I make changes in the ESC header page and the status goes back to invalidated which i set to allowed on the Restricted Caller Access Privilege table.
Did you face such issue ? any idea on it ?
Since you have worked on it, can you help me on how i can remove the menu from the portal ? Chat, catalog, org, knowledge - i want to remove this menu options.