CSA Hub Part 1 Lists, Filters & Forms
⚙️ Part 1 · Topic 2 of 4

Lists, Filters & Forms

🕑 ~40 min read 🎯 High exam weight 📋 7 sections

List Anatomy

A List in ServiceNow displays multiple records from a single table in a tabular format. Understanding every part of a list is essential — the exam frequently tests this knowledge in scenario questions.

Analogy: A ServiceNow list is like Excel — but each row is a live database record, and every action (edit, delete, assign) is fully tracked in audit logs. You are never just editing a spreadsheet; you are interacting with a relational database.
Header Row

Displays column names. Clicking a column header sorts records ascending. Clicking again reverses to descending. An arrow indicator shows the active sort direction.

Record Rows

Each row represents one record from the table. The leftmost cell shows the row number. Clicking anywhere on a row opens that record's form view.

Row-Level Context Menu

Right-click any row to open the context menu. Options include: Open in new tab, Open in split view, Assign to me, Show matching, Copy URL, and more — depending on the table and your permissions.

List Controls (Top-Right)

Icons located at the top-right of the list: Actions menu (bulk operations), Column Selector (add/remove columns), and Export (CSV, Excel, PDF, XML).

Total Record Count

Displayed at the top-right of the list (e.g., "1–20 of 453"). This shows the total records matching the current filter, not just the current page.

Pagination Controls

Located at the bottom of the list. Default page size is typically 20 records. Users can navigate with First, Previous, Next, Last buttons. Page size is configurable per user.

Breadcrumb Filter Bar

The horizontal bar above the list showing active filter conditions as pill-shaped badges. Each pill represents one condition. This is the primary visual indicator of what filters are active.

Search Bar

Located at the top-left of the list. Performs a global text search across the visible columns. Not the same as the condition builder — it performs a LIKE query on all shown fields simultaneously.

Filtering Lists

Filtering is one of the highest-weighted topics for the CSA exam. You must understand the condition builder syntax, the breadcrumb filter system, and how AND vs OR logic works.

Condition Builder — 3-Part Syntax

Every filter condition is built from three parts:

[Field]   [Operator]   [Value]

Priority   =   1 - Critical   // Show only Critical priority records
State   is   In Progress   // AND the state must be In Progress
Assigned to   is not empty   // AND must be assigned to someone

AND vs OR Logic

AND — Narrows Results
  • All conditions must be true
  • Each AND reduces the result set
  • Example: Priority = Critical AND State = In Progress shows only critical incidents that are also in progress
  • Use AND when you want more specific, smaller result sets
OR — Broadens Results
  • At least one condition must be true
  • Each OR increases the result set
  • Example: Priority = Critical OR Priority = High shows critical and high records
  • Use OR when you want to include multiple acceptable values

The Breadcrumb Filter

After applying conditions, they appear as pill-shaped badges above the list. This is called the breadcrumb filter.

Active filter breadcrumb:
Priority = 1 - Critical × AND State = In Progress × AND Assigned to = Me ×
  • Click the × on a single pill to remove only that condition
  • Click anywhere on a pill (not the ×) to edit that condition in the condition builder
  • Click the main X at the left of the breadcrumb bar to clear ALL conditions at once
  • The breadcrumb persists between page loads — your filter is remembered in your session
Exam Trap: The breadcrumb shows ALL active conditions simultaneously. To clear ALL filters, you must click the X at the beginning of the breadcrumb row — not the X on individual pills. Clicking individual pill Xs removes conditions one at a time.

Filter Operators Reference

Concept: Operators define the relationship between a field and its value. The available operators depend on the field type — string fields have different operators than integer or date fields.
=
Exact match. Field value must equal exactly the specified value.
!=
Not equal. Excludes records where the field matches the value.
contains
String contains. Performs a LIKE %value% search. Case-insensitive.
starts with
Performs a LIKE value% search. Useful for prefix searches.
ends with
Performs a LIKE %value search. Less common, used for suffix matching.
is empty
Field has no value (NULL or blank). No value input required.
is not empty
Field has any value (not NULL). Useful for "assigned" checks.
between
For dates/numbers. Requires two values: a start and end range (inclusive).
> / <
Greater than / Less than. Used on numeric and date fields for range queries.
IN
Matches any value in a provided list. More efficient than multiple OR conditions.
NOT IN
Excludes records matching any value in the list. Opposite of IN.
does not contain
String does not include the substring. Opposite of "contains".

Saving & Sharing Filters

Frequently used filters can be saved so you don't need to rebuild them every time. Saved filters are accessed from the filter funnel icon in the list view.

Saving a Filter

Build your conditions in the condition builder. Once conditions are set and visible in the breadcrumb, click the star/save icon (or "Save filter" option in the funnel dropdown). Give it a descriptive name. It is saved to your user profile.

Accessing Saved Filters

Click the funnel/filter icon in the top-left area of the list. A dropdown shows your saved filters. Clicking a saved filter name immediately applies that filter to the list.

Filter Scope

Saved filters are per-user by default. They are tied to your user account and do not appear in other users' filter lists. Table administrators can create default filters visible to all users via list administration.

Favorite Modules

You can bookmark a navigation module by clicking the star/bookmark icon next to it in the Application Navigator. Favorited modules appear in the "Favorites" section of the nav for quick access — separate from saved list filters.

Tip: Saved filters appear in the funnel icon dropdown above the list. They are user-specific — not shared with teammates unless you export and reimport them. If you need org-wide filters, an admin can configure default list filters at the table level via List Administration.

List Personalization

ServiceNow allows each user to customize which columns appear in a list and in what order. These personalizations are saved to the user's profile and do not affect other users.

Column Selector

Click the wrench/gear icon at the top-right corner of the list. A dialog appears showing available columns. Add, remove, or reorder columns using drag-and-drop. Changes apply immediately and are saved to your profile for that specific list.

Personalization Scope

Column layouts are saved per-user, per-list. Changing the Incident list columns does not affect your Task list, and your changes do not affect any other user's view. This is a fundamental ServiceNow user personalization feature.

Sort Persistence

The sort order you apply to a list (by clicking a column header) is remembered between browser sessions for your user account. When you return to that list, your last sort preference is automatically applied.

Right-Click Column Header

Right-clicking a column header reveals additional options: Group by this field (groups records by that column's values), Show Visual Task Board, Pin to top, and aggregate function options.

Aggregate Functions

For numeric columns, right-clicking reveals aggregate options: SUM, COUNT, AVG, MIN, MAX. The aggregate result appears at the bottom of the list column. Useful for quick calculations without running reports.

Admin: List Layout Editor

Admins can set default column layouts for all users via the List Layout editor (accessed via right-click → Configure → List Layout). This sets the baseline view, but users can still personalize on top of this default.

Exam Trap: Personalizing list columns does NOT affect other users — it is strictly user-specific. Admins set default column layouts for all users via the List Layout editor (Configure > List Layout), not through their own personal column selector.

Form Anatomy

When you open a record from a list, you see its Form view. Forms are the primary interface for viewing and editing individual records. Every form follows a consistent structure.

Form Header
  • Record number/name at top (e.g., INC0001234)
  • Breadcrumb path showing table and record
  • Form controls/action buttons
  • Record state indicator
  • Attachments icon (paperclip)
Form Body — Fields
  • Two-column layout (most forms)
  • Field label on left, input on right
  • Mandatory fields marked with red asterisk (*)
  • Read-only fields appear grayed out
  • Fields grouped into logical sections
Field Decorators
  • Red asterisk (*) — mandatory field
  • Lock icon — read-only or locked field
  • Magnifying glass — reference field lookup
  • Info icon (i) — field tooltip available
  • Circular arrows — field recalculates automatically
Related Lists (Bottom)
  • Separate list views below the main form
  • Show records from OTHER tables related to this record
  • Example: Incident form shows "Work Notes", "Affected CIs", "Change Requests"
  • Each related list can be filtered/sorted independently
Concept — Related Lists: Related lists show records from other tables that have a Reference field pointing back to this record. This is a foreign key relationship. For example: the "Tasks" related list on an Incident shows all Task records where Task.parent = this Incident. Deleting the parent record does not automatically delete related list records (configurable).

Special Field Types on Forms

Reference Fields

Display a text input with a magnifying glass icon. Clicking the magnifying glass opens a lookup dialog to search and select a record from the referenced table. You can also type directly — ServiceNow will auto-suggest matching records.

Choice Fields

Rendered as a dropdown select. The available options are defined in the Choice list for that field. Admins manage choice lists via the Choice List editor. Users cannot add ad-hoc options — only admins can.

Journal Fields (Activity Log)

Shown at the bottom of most forms as the Activity section. Displays a chronological history of all Work Notes and Comments. Journal entries are append-only — once submitted, they cannot be edited or deleted, creating an immutable audit trail.

Mandatory Fields

Marked with a red asterisk (*). You cannot save or submit the record without providing values for all mandatory fields. If you attempt to save with empty mandatory fields, ServiceNow highlights them in red with an error message.

Form Controls & Saving Records

The buttons available on a form depend on whether you are viewing an existing record or creating a new one. Understanding the distinction between each button is a common exam topic.

Save / Update
Saves changes to an existing record and stays on the form. "Update" is the label used on existing records; terminology may differ by form/version.
Submit
Creates a new record. Appears on blank new-record forms. After submission, typically redirects to the list view or the newly created record.
Save and Stay
Saves the record without refreshing the page or navigating away. Useful when making many changes and wanting to preserve form state and scroll position.
Insert
Creates a copy of the current record as a brand-new record. Useful for creating similar records without re-entering data. The original record is unchanged.
Revert
Discards all unsaved changes on the form and reverts to the last saved version of the record. Does not affect previously saved data.
Delete
Permanently removes the record from the database. Requires delete permission. No confirmation screen in all versions — use with caution.
Warning: Delete is permanent. ServiceNow does not have a built-in recycle bin by default. Once a record is deleted, it cannot be recovered through the UI. Some organizations implement soft-delete by convention (setting an Active = false flag) rather than hard-deleting records, but this requires custom configuration and is not the default behavior.

Field Types Reference

ServiceNow has a rich set of field types. The exam tests both identification (what type is used for X) and behavioral differences (how they store/display data).

Field Type Input Control Use Case & Notes
String Text box (single line) Short text: names, titles, descriptions. Max length configurable. Supports contains/starts with operators.
Integer Numeric input Whole numbers: counts, priority numbers. Supports >, <, between operators. No decimal places.
Boolean Checkbox True/False only. Used for Active/Inactive flags, yes/no fields. Stored as 0 or 1 in the database.
Choice Dropdown select Fixed set of options defined in the Choice list. Admin manages available values. Users cannot add new options.
Reference Lookup field with magnifying glass Links to a record in another table (foreign key). Stores the sys_id of the related record internally.
Glide List Multi-select reference Multiple records from the same referenced table. Similar to Reference but allows many-to-many relationships.
Date/Time Date/time picker Timestamps for created, updated, resolved dates. Stored in UTC; displayed in user's local timezone.
Journal (Work Notes / Comments) Append-only entry area Activity log entries. Append-only — cannot edit past entries. Work Notes = private; Comments = public.
HTML Rich text editor (WYSIWYG) Formatted content with bold, lists, links. Used for knowledge articles, email bodies.
Currency Number + currency selector Financial values with currency code. Supports multi-currency environments. Stored with currency code metadata.
URL Text input (renders as link) Website addresses. Validates URL format. Displayed as a clickable hyperlink in read mode.
Script Code editor (Monaco) JavaScript code for business rules, client scripts. Syntax highlighting and validation included.
Exam Trap — Journal Fields: Work Notes are private — only agents and internal users with access can see them. Comments are public — visible to end users in the Service Portal. Both are Journal field types and are both append-only (you cannot edit or delete a previously submitted entry). This distinction is frequently tested.
Exam Trap — Sorting vs Filtering: Sorting a list by clicking a column header does NOT change which records appear — it only reorders the currently visible records. Filtering changes which records appear by applying conditions. These are two completely separate operations. Many students confuse them in scenario questions.
Tip — Opening Records in New Tab: You can open any record in a new browser tab by middle-clicking or right-clicking the row number on the left side of the list and selecting "Open in new tab." This lets you compare records side-by-side without losing your current list view and filter state.

Key Exam Points Summary

High-priority concepts that frequently appear on the CSA exam for this topic:

📌 Filter Breadcrumb

The blue pills above the list show active conditions. Click individual pill × to remove that condition. Click the main breadcrumb X to clear ALL filters at once.

📌 Saved Filters = User-Specific

Saved filters are personal by default. Accessible from the funnel icon. Admins set org-wide defaults via List Administration, not the personal filter save feature.

📌 Column Personalization = User-Specific

Adding/removing/reordering columns via the gear icon only affects YOUR view. Admin uses List Layout Editor to set defaults for all users.

📌 Work Notes vs Comments

Work Notes = private (agents only). Comments = public (Service Portal visible). Both are Journal fields. Both are append-only.

📌 Sort ≠ Filter

Sorting only reorders records already in the list. Filtering changes which records appear. Completely independent operations.

📌 Delete = Permanent

No built-in recycle bin. Deleted records are gone. Some orgs use Active=false soft-delete pattern, but this is custom — not default ServiceNow behavior.

📌 Reference Field Storage

Reference fields display the record's display value (e.g., user's name) but internally store the sys_id (GUID) of the referenced record.

📌 Related Lists = Other Tables

Related lists at the bottom of forms always show records from different tables that reference this record — not records from the same table.

← UI Navigation Properties & Branding →