ServiceNow CAD key terms

A custom application built inside its own private namespace, so its tables, scripts, and logic stay isolated from other applications and from the global scope unless access is explicitly granted.

The unique namespace identifier assigned to a scoped application, for example x_acme_orders, which prefixes its tables and determines which artifacts the application owns and may call.

The default scope whose artifacts any application may call or extend; changes made there are shared across the whole instance rather than isolated to one application.

The top-level navigation menu that groups an application's modules so users can reach its lists, forms, and dashboards from the instance banner.

A navigable link inside an application menu that opens a specific page, list, or record, sometimes filtered by a predefined query.

A setting that lets a non-administrator user create and edit artifacts within one specific scoped application without being given full administrative rights on the instance.

A named collection of records that share the same set of fields, stored as rows in the database; a table may extend another table or stand alone.

The record in the system dictionary that defines a table column, including its type, maximum length, default value, reference target, and other attributes.

A 32-character globally unique identifier automatically assigned to every record and used as the key for lookups, reference values, and record URLs.

A field type that stores the sys_id of a record on another table, creating a link that renders as a clickable value and supports dot-walking to the related record.

A field whose permitted values come from a defined set of options stored in the choice table and presented to users as a dropdown, radio buttons, or similar control.

A relationship in which a child table extends a parent table and automatically gains all of the parent's fields and behavior, as the incident table does from task.

A data design where two tables are joined through a third mapping table holding a reference field to each side, so many records can relate to many records.

The drag-and-drop interface used to arrange fields, sections, and related lists on a form for a chosen table and view, without editing layout records by hand.

Configuration that determines which columns appear on a table's list, the order of those columns, and whether users may personalize the list themselves.

A list embedded on a form that shows records from another table connected to the current record, typically through a reference field pointing back to it.

A condition-based rule evaluated in the browser that makes fields visible, mandatory, or read-only, letting developers change form behavior without writing client scripts.

A single field-level instruction attached to a UI policy, such as setting a field mandatory, hiding it, making it read-only, or clearing its value.

A record that lets a child table change a field's label, mandatory state, read-only state, or default value without altering the parent table's dictionary entry.

JavaScript that runs in the user's browser on form or list events such as load, field change, submit, or cell edit, providing immediate interactive behavior.

Server-side script that runs when records are queried, inserted, updated, or deleted, executing before, after, or asynchronously from the database operation.

A reusable server-side JavaScript class that other server scripts can call and that, when marked client callable, the browser can invoke through GlideAjax.

A client-side class that sends an asynchronous request to a server-side Script Include and returns the result to the browser without reloading the form.

The primary server-side API class for querying, inserting, updating, and deleting records; it runs queries, iterates result sets, and reads or writes field values.

A server-side utility object that provides session and instance information, logging, date and number helpers, property lookups, and user role checks.

A button, link, or context menu item on a form or list that runs client-side script, server-side script, or both when the user activates it.

A low-code tool for building automations as flows composed of triggers, actions, and approvals, often replacing traditional workflow and simple business rule use cases.

A record that runs a server-side script automatically at defined times or intervals, commonly used for recurring cleanup, maintenance, or data updates.

An access control rule that grants or denies read, write, create, or delete access to a table, record, or field, evaluated by a condition or a script.

A named set of permissions assigned to users or groups; roles gate menu items, ACL evaluation, and script-level checks such as checking whether a user has the role.

A record that permits one scoped application to read or use a specific artifact, such as a table or script include, that belongs to a different scope.

A related list on an application record that lists the roles whose users are allowed to open the application's menu and its modules.

A container that records configuration changes made in an instance so the changes can be exported and replayed on another instance.

The two-step deployment process in which preview compares the update set's records with the target instance and reports conflicts, and commit then applies the changes.

A central store of published applications and plugins from which instances install or upgrade apps, including custom scoped applications shared between instances.

A staging area that receives raw imported data plus the mapping that converts each staged row into a record on a target table, optionally coalescing onto existing records.

An agent installed inside a customer network that lets the instance communicate with internal systems for integrations, discovery, and orchestration tasks.

A record defining an outbound REST integration, including the endpoint URL, HTTP method, headers, query parameters, and any response processing.

A platform tool for building and running automated tests of forms, UI actions, and server-side logic to confirm that changes did not break existing behavior.