Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Inbound email action not processed due to cross scope previliges issues - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Inbound email action not processed due to cross scope previliges issues
KB0825330

Inbound email action not processed due to cross scope previliges issues


1566 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Inbound actions defined in the scoped application will not be able to access the objects defined in the global scope API. 

 

Objects such as current, email are defined in the global scope and trying to access them from a different scope will throw errors.

 

 

 

Cause

Inbound actions defined in the scoped application will not be able to access the objects defined in the global scope API. 

 

Objects such as current, email are defined in the global scope and trying to access them from a different scope will throw errors.

Resolution

To resolve this issue you need to check the conditions and the action script of the inbound actions to see which objects of the global API are being accessed. 

 

Consider a sample inbound action which is accessing current, email objects.

 

To resolve the cross scope privilege issue with the above said sample inbound action we need to define below cross scope privileges from source scope(scope where we have inbound action created) to target scope(global).

 

** Please test in your sub-production instance first .

 

Below is how you can create:

 

Go to cog wheel settings at the top >> Go to Developer >> switch to the scoped application >> Go to Application Cross-Scope Access >> Click on New>>

 

Add the below cross scope privileges:

 

Select Target Scope as Global >> Target Name  as ScopedGlideElement >> Target Type as Scriptable >> Operation as Execute API >> Status as Allowed >> Click on Update

 

Select Target Scope as Global >> Target Name as ScopedEmailWrapper >> Target Type as Scriptable >> Operation as Execute API >> Status as Allowed >> Click on Update

 

Select Target Scope as Global >> Target Name as ScopedEmailLogger >> Target Type as Scriptable >> Operation as Execute API >> Status as Allowed >> Click on Update

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.