Notifications

Cancel changes

Description

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.

Press the settings cog in the top right corner of the screen

Select the application you want to enable access for from the Application drop-down.

In the Application Navigator, open System Properties > All Properties

Click New

Use the values below:

Suffix

glide.script.block.client.globals

Application

The application you want to enable access for

(This will be automatically filled in)

Name

appname.glide.script.block.client.globals

(This will be automatically filled in. appname will be the scope of your application.)