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.
Client-side global JavaScript objects in scoped applications - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Client-side global JavaScript objects in scoped applications
KB0551586

Client-side global JavaScript objects in scoped applications


7700 Views Last updated : Sep 28, 2022 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

A key feature of scoped applications is their isolation from one-another. The platform enforces this isolation to ensure each applications independence. Along with many other parts of the platform, this enforcement occurs in client-side scripting.

Access to client-side global JavaScript objects in scoped applications is blocked by default. This occurs because with this access, an application would be able to break out of it's own scope and access the global scope, and through that the scope of other applications. An example of a global JavaScript object is the window object.

Sometimes, it may be necessary to access global JavaScript objects. An example scenario is if you wanted to create a UI Action which opened a new window. The only way to do this would be to use the open() method on the window object. You would be blocked from being able to do this by default. There is a system property which lets you override this default behaviour, glide.script.block.client.globals.

To define the glide.script.block.client.globals system property, follow the steps below.

  1. Press the settings cog in the top right corner of the screen
  2. Select the application you want to enable access for from the Application drop-down.
  3. In the Application Navigator, open System Properties > All Properties
  4. Click New
  5. Use the values below:
    Suffixglide.script.block.client.globals 
    ApplicationThe application you want to enable access for(This will be automatically filled in)
    Nameappname.glide.script.block.client.globals(This will be automatically filled in. appname will be the scope of your application.) 
    Typetrue | false 
    Valuefalse 
  6. Click Submit

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.