sys_properties Table — ServiceNow Reference

Table Reference/sys_properties

The sys_properties table stores platform configuration as key-value pairs accessed via gs.getProperty() and gs.setProperty(). Owned by the Platform module, this table controls everything from timeouts to feature flags across your instance.

What This Table Is

The sys_properties table stores platform configuration as key-value pairs that control ServiceNow behavior at the system level. Every timeout, feature flag, URL endpoint, and configurable constant lives here. Unlike user preferences or module-specific settings, these properties affect the entire platform and all users unless specifically scoped.

Owned by the Platform module, this table supports every ServiceNow process by providing runtime configuration. Properties range from database connection timeouts (glide.db.query.timeout) to UI behavior toggles (glide.ui.security.ignore_csrf) to integration endpoints. The platform reads these constantly—every API call, UI render, and background job checks relevant properties.

This table extends sys_metadata, making properties part of the update set framework. Properties can be scoped to applications and moved between instances. No tables extend sys_properties—it's a leaf table focused purely on storing configuration data.

Enterprise instances typically contain 2,000-5,000 properties, with out-of-box properties making up the majority. Performance is excellent—properties are heavily cached in memory and rarely cause query bottlenecks. The platform preloads critical properties at startup, making gs.getProperty() calls extremely fast.

When You'll Script Against This Table

You'll read properties constantly via gs.getProperty() in Business Rules, Script Includes, UI Scripts, and Background Scripts. Writing properties requires either the System Properties module (Sanity) or gs.setProperty() calls. Direct GlideRecord manipulation works but bypasses caching and should be avoided.

Property access requires admin role to modify, but reading via gs.getProperty() works for all users. Some security-sensitive properties are hidden from non-admin users even in scripts. Scoped applications can only modify their own scoped properties unless elevated.

Common scripting patterns:

Feature flagging: if (gs.getProperty('custom.feature.enabled') == 'true')
Environment detection: gs.getProperty('glide.servlet.uri') to check instance URL
Timeout configuration: Reading database or API timeout values before long operations
Integration endpoints: gs.getProperty('custom.api.endpoint') for external system URLs
Deployment automation: Setting properties during clone scripts or deployment
Debug switches: gs.getProperty('custom.debug.logging') to control verbose logging
Application configuration: Storing app-specific settings that admins can modify without code changes

Table Gotchas

⚠️

Properties are cached aggressively. Changes via direct GlideRecord won't be visible until cache refresh or instance restart. Always use gs.setProperty() or the UI.

⚠️

All property values are strings. gs.getProperty('my.number.prop') returns '123', not 123. Convert explicitly: parseInt(gs.getProperty('my.number.prop')).

The value field is limited to 4,000 characters. Longer values get truncated silently.
Property names starting with glide. are reserved for ServiceNow. Use your company prefix: acme.integration.timeout

⚠️

Security-sensitive properties (passwords, tokens) in name or value are partially masked in the UI but fully readable via gs.getProperty() if you have the role.

Boolean properties should use 'true'/'false' strings, not 'yes'/'no'. Check with: gs.getProperty('prop') == 'true'
Default values in gs.getProperty('name', 'default') only apply when the property doesn't exist, not when it's empty string.

Free Newsletter

Enjoying this? Get one deep-dive per week.

Join 1,000+ ServiceNow pros — scripts, GlideRecord patterns, Flow Designer techniques, and career moves. Free.

The sys_properties table extends sys_metadata, inheriting update set tracking and application scoping behavior. This relationship makes properties manageable through the development lifecycle—you can capture property changes in update sets and promote them between instances.

The sys_user_preference table serves a similar key-value role but for user-specific settings rather than system-wide configuration. The sys_app_application table connects to scoped properties through the sys_scope field. Security configurations in sys_security_acl and audit logging in sys_audit frequently reference properties that control their behavior.

Chrome Extension

Sourdough: ServiceNow Monitoring and Analytics

A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.

Instance HealthGraphs & ChartsAPI HealthDeveloper ToolsQuick SearchInstance Switcher

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview

Tasks

CMDB

API

Metrics

Monitor

Internals

Instance:sourdoughdev·Version:Yokohama

Instance StateONLINE

System StatusFully Operational

Session Timeout90 minutes

Logged-In Sessions2 (20 active)

Build Nameyokohama-12-18-2024_p1

IP Address10.159.128.43

Instance HealthHealth Score: 90%

🔥 5dSourdough (Chrome Plugin)Dark Mode

Key Fields

Column	Type	Label	Notes
name	string	Name	The property key used in gs.getProperty(). Must be unique and should follow naming conventions like 'company.module.setting'.
value	string	Value	The property value as a string. Limited to 4,000 characters and always returned as string from gs.getProperty() regardless of content.
description	string	Description	Human-readable description of what this property controls. Critical for maintenance since property purposes aren't obvious from names alone.
type	choice	Type	Data type hint (string, boolean, integer, etc.). Purely documentational—all values are stored and returned as strings.
choices	string	Choices	Comma-separated list of valid values when type is 'choice'. Used by the UI for dropdown validation but not enforced programmatically.
suffix	string	Suffix	Optional suffix appended to the name for display purposes. Helps organize related properties in the System Properties list.
read_roles	string	Read roles	Comma-separated list of roles required to read this property. Empty means all users can read via gs.getProperty().
write_roles	string	Write roles	Comma-separated list of roles required to modify this property. Defaults to 'admin' if empty when security is enforced.
ignore_cache	boolean	Ignore cache	Forces fresh database read on every gs.getProperty() call instead of using cached value. Rarely needed and impacts performance.
is_private	boolean	Private	Hides property from System Properties list for non-admin users. The value is still readable via gs.getProperty() if role permits.
status	choice	Status	Lifecycle status of the property. 'Available' properties are active, others are filtered from normal operation.

Common Queries

Get all active system properties

// Basic query to see all available properties
var gr = new GlideRecord('sys_properties');
gr.addQuery('status', 'Available');
gr.orderBy('name');
gr.query();

while (gr.next()) {
    gs.info('Property: ' + gr.name + ' = ' + gr.value);
}

Find properties by name pattern and scope

// Find custom integration properties in global scope
var gr = new GlideRecord('sys_properties');
gr.addQuery('name', 'CONTAINS', 'acme.integration');
gr.addQuery('sys_scope.scope', 'global'); // Reference to sys_scope
gr.addQuery('status', 'Available');
gr.query();

while (gr.next()) {
    gs.info('Integration prop: ' + gr.name + ' = ' + gr.value);
}

Find environment-specific configuration properties

// Get all properties containing environment indicators
var gr = new GlideRecord('sys_properties');
var qc = gr.addQuery('name', 'CONTAINS', 'url');
qc.addOrCondition('name', 'CONTAINS', 'endpoint');
qc.addOrCondition('name', 'CONTAINS', 'uri');
gr.addQuery('status', 'Available');
gr.orderBy('name');
gr.query();

// Useful for deployment validation
while (gr.next()) {
    gs.info(gr.name + ': ' + gr.value);
}

Count properties by application scope

// Aggregate count of properties per application
var ga = new GlideAggregate('sys_properties');
ga.addQuery('status', 'Available');
ga.addAggregate('COUNT');
ga.groupBy('sys_scope.name'); // Group by scope name
ga.query();

while (ga.next()) {
    var scopeName = ga.getValue('sys_scope.name');
    var count = ga.getAggregate('COUNT');
    gs.info('Scope: ' + scopeName + ' has ' + count + ' properties');
}

Wrong way vs right way to check boolean properties

// WRONG - this fails when property value is 'false'
if (gs.getProperty('custom.feature.enabled')) {
    // This runs even when value is 'false' string!
}

// RIGHT - explicit string comparison
if (gs.getProperty('custom.feature.enabled') == 'true') {
    // Only runs when explicitly set to 'true'
}

// BETTER - with default handling
var enabled = gs.getProperty('custom.feature.enabled', 'false') == 'true';
if (enabled) {
    // Clean boolean logic with sensible default
}

Test Your Knowledge

Quick 3-question quiz — see how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue

sys_properties