Restricted Caller Access message after attachment uploaded to Attachment type variable on portal

Derek C
Tera Guru

‎04-25-2024 11:16 AM

Hi all, I am having an issue with a popup on the portal when adding an attachment to an attachment type variable, specifically after adding a record to an MRVS. It doesn't seem to pop up the error if there is no record in the MRVS which makes this even more odd.

 

The message states: "Unable to identify source of the Read operation on table 'sn_hr_core_job' from scope 'Service Catalog REST API'. No Restricted Caller Access privilege records were created. The operation was allowed because target resource RCA policy is set to 'Tracking', but will be blocked with the 'Restricted' policy. Please contact the application admin."

 

2024-04-25_10-54-21.png

 

Steps to reproduce:

 

1. Navigate to the record producer in the catalog on the ESC portal (no widget customizations)

2. Add a record that references the sn_hr_core_job table

3. Add any attachment an "Attachment" type variable

 

DerekC_1-1714068005458.png

 

 

I have added a handful of different Restricted Caller Access records, but can't seem to find the right combination. Has anyone come across this issue? Any suggestions on how to fix this?

 

A couple other notes: 

1. I am using the g_service_catalog.parent.getValue() api on the MRVS to populate the "Employee" field. Because the message references the "'Service Catalog REST API'" I thought it may have to do with that.

 

DerekC_2-1714068213743.png

2. I am also using the new "Auto-populate" ability on variables in the MRVS. Again because the message references the "'Service Catalog REST API'" I thought it may have to do with this new functionality (hooray for no more GlideAjax!)

 

DerekC_3-1714068375780.png

 

0 Helpfuls
  • 1,618 Views
2 REPLIES 2

Tim Deniston
Mega Sage
Mega Sage

‎05-02-2024 08:35 AM

I had a similar error with the Security Incident Request table. The solution was...

  1. Go to the sys_db_object table
  2. Open the record for the table where the error occurs (for me: sn_si_request; for you: maybe 'sn_hr_core_job' or whatever the HR Case table is that the record producer is using)
  3. Update the 'Caller Access' field to "-- None --". 

I then flushed the cache and it immediately solved the issue for me. 

Here's where I found the fix: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0851910 

Derek C
Tera Guru
In response to Tim Deniston

‎05-02-2024 08:43 AM

Thanks for the info! 

This appears to be an issue with the new "Auto-populate" feature on variables. As soon as I turned all of that off and went back to a GlideAjax (I'd also imagine g_form.getReference() with a call back would work) the issue was resolved. This seems to be a brand new functionality, probably just needs some bugs ironed out.

Thanks!

- Derek

0 Helpfuls