Skip to main content

ServiceNow Error: Create operation from scope 'rhino.global' has been refused due to the table's cross-scope access policy

ServiceNow Error: Create operation from scope 'rhino.global' has been refused due to the table's cross-scope access policy


Sometimes if encountering an issue in background script or fix script, move the code into a script include defined within the application but accessible from all application scopes, and call the script include from there

example - background script:

var firstname='testfirst';
var lastname='testlast';
var title='Mr';

var si=new x_cls_clear_skye_i.serviceCatalog_libraries();
var res=si.createTestStagingEntry(firstname, lastname, title);

gs.print('RECORD SYSID='+res);


script include:

createTestStagingEntry: function(firstname, lastname, title) {

var startdate = new GlideDate().getDisplayValue();

var gr = new GlideRecord('x_cls_clear_skye_i_poc_account_import_staging');
gr.newRecord();
gr.setValue('u_first_name', firstname);
gr.setValue('u_last_name', lastname);
gr.setValue('title', title);
gr.setValue('scheduled_start', startdate);
var sReturn=gr.insert();

gs.info('createTestStagingEntry::STAGING TABLE SYSID=' + gr.sys_id);
return sReturn;
},




Resolution:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0727180 


Resolution

Enable the 'Can Create' option for the 'x_<custom_table>'

  1. Navigate to System Definition > Tables
  2. Open the record for the custom table. 
  3. In the Application Access section, check the box for 'Can create' 

Additional Information

 Please review the documentation below as well: 

In the Application Access section, define the scope protection for the table. For more information, see Application access settings.

Can create 

Select the check box to allow script objects from other application scopes to create records in this table. This option offers runtime protection. For example, a script in another application can insert a new record in this table. This option is available only when the Can read check box is selected. lear the check box to prevent script objects from other application scopes from creating records in this table. 

Comments

Popular posts from this blog

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){

Get URL Parameter - server side script (portal or classic UI)

Classic UI : var sURL_editparam = gs . action . getGlideURI (). getMap (). get ( ' sysparm_aparameter ' ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); } Portal : var sURL_editparam = $sp . getParameter ( " sysparm_aparameter " ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); }