CSA: Certified System AdministratorDemo

ServiceNow Access Control List (ACL) rules secure record objects identified as tables, fields, or particular records. Since a record is a table row and a field is a table column, ACLs can protect a specific row, column, or table. ServiceNow ACL types

ServiceNow events can be generated from a Business Rule or from a Workflow. These mechanisms can queue an event for subsequent processing by notifications, script actions, or other event handlers.

ServiceNow administrators create custom tables through the table-administration interface. The Tables module supports creating custom table records, and Tables & Columns is the table-administration module label that provides access to those table records. A Schema Map is for viewing relationships, and the Dictionary is primarily for managing dictionary entries rather than creating tables.

Import sets stage source records in an import table. A transform map defines the mapping from that staging table to a target table, the transform moves the records to the target, and the import-set records can then be cleaned up.

The Help Panel (question-mark icon) in Flow Designer provides in-product guided tours, information about actions, and instructions for working with flow inputs and outputs.

ServiceNow assigns each record a unique 32-character GUID in the sys_id field, which serves as the record’s system identifier.

The Data section is where a report’s name and its source are set. It lets the author choose the source type and select the underlying table or data source used by the report.

The CI Relationship Editor creates and manages relationships between configuration items, including dependency relationships in the CMDB.

The baseline Service Catalog homepage provides access to catalog items, record producers, and order guides. Record producers and order guides are Service Catalog item types, while item variables are configured within catalog items and flows automate fulfillment rather than acting as catalog-homepage components. ServiceNow documents standard catalog items, record producers, and order guides as basic Service Catalog item types.

A data source must be defined first because it specifies the type and location of the external spreadsheet data. ServiceNow then loads that data into an import-set staging table before mapping or transforming it into target tables.

A ServiceNow variable set is a reusable collection of catalog variables that can be associated with multiple catalog items. Defining the four shared mandatory variables in one variable set and adding it to each item keeps their configuration consistent and lets changes propagate to every associated catalog item.

The personalize_form role grants access to Table Builder’s Forms tab and permits form-field customization. The admin role has administrative access to Table Builder and platform configuration, so it can also configure form layouts.

ServiceNow Core provides reusable actions available to all flows, including actions to create a record, look up a record, request approval, and pause execution until a record condition is met. These functions correspond to Create Record, Look Up Record, Ask for Approval, and Wait for Condition.

In ServiceNow, the Activity formatter is added to a form to show the record’s activity history, including tracked updates and journal entries such as comments and work notes.

A Service Catalog order is represented by a requested-item record in the sc_req_item table, and the fulfillment work for that requested item is tracked through catalog-task records in the sc_task table. Incident, change, and problem records are separate ITSM processes rather than the standard records used for catalog-item fulfillment.

ServiceNow Client Scripts run JavaScript in the client web browser in response to form events. UI Policies control form behavior and can execute scripts for client-side conditions, whereas Script Includes, Access Control scripts, and Business Rule scripts are server-side mechanisms.

A Common Service Data Model (CSDM) product view presents product-specific CSDM use cases and identifies the associated CSDM tables and data, including relevant configuration-item information.

ServiceNow Knowledge Base records use User Criteria-based access control tabs to manage read and contribute permissions. The 'Cannot Contribute' related list/tab lets administrators explicitly define users or groups who are prevented from authoring or editing articles in the knowledge base, overriding any 'Can Contribute' criteria that might otherwise grant them access.

A user account establishes the employee’s identity in the instance. Adding that account to both the Hardware and Network groups gives the employee the group memberships needed to receive and perform work assigned to those teams. In ServiceNow, group members inherit the roles and assignment-related access associated with their groups.

A record-based trigger runs a flow after a record is created or updated. ServiceNow Flow Designer defines record triggers for these record operations, while date- and application-based triggers serve different event types.

The Common Services Data Model (CSDM) is ServiceNow’s standardized framework for defining service-related terms, relationships, and CMDB data placement. It acts as a blueprint for mapping IT services on the ServiceNow platform.

A filter condition compares a selected field to a value by using an operator. These three elements define what data the filter evaluates and how it evaluates it.

ServiceNow creates catalog items from Service Catalog > Catalog Definition > Maintain Items by selecting New on the Maintain Items list.

ServiceNow evaluates Access Control Lists (ACLs) in a layered, gated sequence. First, table-level ACLs are checked, moving from the most specific rule (e.g., a rule for the exact table) to the most general rule (e.g., a wildcard or parent-table rule). A user must satisfy the applicable table-level ACL before the platform proceeds any further — if table-level access is denied, no field-level ACLs are evaluated at all. Once table-level access is granted, the platform then evaluates field-level ACLs, again applying them from the most specific matching rule (e.g., table.field) down to the most general (e.g., table.* or .). This order ensures that broad access to a table is confirmed before more granular field-level restrictions are applied, preventing unnecessary processing and ensuring users only gain field access after passing the overarching table check.