SN System Properties Reference
Property reference

glide.script.block.client.globals

The glide.script.block.client.globals property determines whether client-side global variables are blocked in scripts. Admins should consider enabling this property to enhance security by preventing unauthorized access to sensitive global variables.

Default: false Type: boolean Application:

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do? This boolean property, when set to true, blocks the use of client-side global variables in scripts, thereby improving security.
What area does it affect? Script Security Settings
What does the default mean? The default value is "false", which means this behavior is disabled by default.
When should you review it? Review this property when assessing script security or during security audits.

Out of the box property record

Raw metadata from the property record.

Property name glide.script.block.client.globals
Sys ID
Type boolean
Application
Default value false
Description
Updated 2024-08-01 23:59:19

Sources

Official references and nearby text excerpts where this property appears.

Documentation excerpt View supporting context
Context preview Snippet 1
... disable this on a per-script basis, configure this form and select the Isolate script check box. To disable this feature for all new globally-scoped client-side scripts set the system property glide.script.block.client.globals to false. UI scripts UI scripts provide a way to package client-side JavaScript into a reusable form, similar to how script includes store server-side JavaScript. Administrators can create UI scripts ...
Documentation excerpt View supporting context
Context preview Snippet 2
... are associated. 813 Problem Short description Description Steps to reproduce the code coverage from the frontend hasn't been fully processed and persisted. Automated Test Framework (ATF) PRB1997825 KB2806020 When the 'glide.script.block.client.globals' property is set to false, running an ATF test throws a client error with code coverage enabled Refer to the listed KB article for details. Benchmarks PRB2000082 Success dashboard and ...
Additional source link Another external reference for this property
Open reference