- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2024 01:18 AM
Hi,
I am trying to transfer a HR case (HR core case) to Employee RElations (ER). I get the below error message even though the case gets transferred. I created restricted caller access to allow read/write /create acceess on ER. It did not work
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2024 01:51 AM
@Radhika1 Please look for the script include/business rule which is using setWorkflow. It looks like setWorkflow is being called from HR Core scope for the table which belongs in Employee relations scope.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2024 01:51 AM
@Radhika1 Please look for the script include/business rule which is using setWorkflow. It looks like setWorkflow is being called from HR Core scope for the table which belongs in Employee relations scope.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2024 02:26 AM
@Sandeep Rajput setWorkFlow is being used in OOTB 'ReclassifyCaseTransfer' script include. As not recommended, I do not want to modify that. Do you see any other possibility?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2024 02:52 AM
@Radhika1 Please check if there are any existing invalidated Restricted Caller Access records originating from the ER scope. Please set them to allowed and check if this action fixes the issue. If not then raise a case with ServiceNow support as this API call was made from their OOTB script include and they should have a workaround to address it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2024 03:15 AM
Yes , I have already validated all restricted caller access privileges. The issue is resolved when I removed setWorkflow(false) from a custom BR used for achieving another functionality. Thank you.