Property reference

glide.record.legacy_cross_scope_access_policy_in_script

The glide.record.legacy_cross_scope_access_policy_in_script property determines whether legacy cross-scope access policies are applied in scripts. Admins should review this setting when managing script behaviors that interact with different application scopes.

Default: false Type: boolean Application: Global

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 enables or disables the use of legacy cross-scope access policies in ServiceNow scripts, affecting how scripts can access records across different application scopes.
What area does it affect? Script execution and access
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 configuring script access across application scopes or troubleshooting related issues.

Out of the box property record

Raw metadata from the property record.

Property name glide.record.legacy_cross_scope_access_policy_in_script
Sys ID 9e52826587120300cf2d5fb736cb0b7f
Type boolean
Application Global
Default value false
Description
Updated 2024-05-25 04:03:51

Sources

Official references and nearby text excerpts where this property appears.

Documentation excerpt View supporting context
Context preview Snippet 1
... access to tables that were not configured with that level of access. In order to prevent customers from having applications broken when this scoped access behavior was patched, the property glide.record.legacy_cross_scope_access_policy_in_script was created. When 'true', cross scope access falls back onto legacy behavior (insecure‎. This property disables scope fencing, allowing scoped apps to access global script interfaces. • Security Risk ◦(Old‎ ...