Caller Restriction to none

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2019 10:09 PM
For the Survey notification we got the scope error form global to HE case table.
We change “Caller Access” field on sn_hr_core_case table to “None” from “Caller Restriction”. After that, “Cross scope errors we were getting before is not coming.
Does it impact or it is doable?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2019 05:22 AM
Hi SMORA,
Setting the Caller Access to 'None' is not the recommended approach. This allows every read or execution on the target of HR Case. Understanding the Application Restricted Caller Access is key. You can find a recorded Ask the Expert session on this topic by following this link.
https://community.servicenow.com/community?id=community_question&sys_id=cbd8b9badbb9570058dcf4621f961982
Regards,
Mike

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2019 09:05 AM
Thank you Mike.
But how to fix the scope error. Even after allowing the Read Access the error occurs.
This is for the HR survey we created. When we click on outbox (preview html) read operation error displays.
Does we need to approach HI or any suggestions to fix the issue please.
Thanks
SMORA

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2019 09:11 AM
Hi SMORA,
Do you have any RCA records with a status other than "Allowed"? If so, I would evaluate those to see if they are the root cause for your issue.
Regards,
Mike

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2019 09:18 AM