2.1 Platform Overview & Navigation

Why Platform Overview & Navigation Matters

Quick Answer: ServiceNow is a single Now Platform running as a multi-instance, cloud-hosted application on one relational database. Every workflow, list, and form reads and writes records in that database. The Certified System Administrator (CSA) exam expects you to navigate the Next Experience interface, use the Application Navigator, and explain how global and scoped applications differ.

Platform Overview and Navigation is roughly 7% of the CSA exam. It is small in weight but foundational: nearly every other domain assumes you can find a module, filter a list, open a form, and reason about where data is stored. Administrators who skip these basics struggle with the heavier database and configuration domains later.

The Now Platform Concept

ServiceNow is delivered as Platform as a Service (PaaS). Customers do not get separate product silos; they get one extensible platform on which IT Service Management, HR, Customer Service, and custom applications all run. Key ideas to memorize:

• Single data model — all applications share one relational database. A custom field added to a table is visible anywhere that table is used.
• Instance-based — each customer gets one or more isolated instances (for example, a dev, test, and prod instance), not shared tenancy in one database.
• Extensible tables — most operational records extend the Task table, inheriting fields like number, state, assigned_to, and priority.
• Configuration over code — most behavior is built with declarative tools (forms, UI Policies, Flow Designer) rather than custom programming.

Now Platform UI Generations

Next Experience is now the default for new instances. UI Builder is not a "theme" — it is a separate tool for assembling pages from reusable components, most commonly for Workspaces.

The Application Navigator

The Application Navigator is the primary way administrators reach functionality. In Next Experience it opens from the All menu in the unified navigation header.

• Applications are top-level groupings (for example, Incident, Change, User Administration).
• Modules are the links inside an application (for example, Incident > Open, Incident > Create New).
• The filter text box does a type-ahead search across application and module labels.
• The navigator is role-filtered: a module only appears if the user holds a role that grants access, and Access Control List (ACL) rules still gate the underlying data.
• Favorites (star icon) pin frequently used modules; History lists recently visited pages.

A common exam trap: a user "cannot see a module." The cause is almost always a missing role, not a broken module — modules have a roles field that controls visibility.

Lists and Forms

Nearly all work happens in lists and forms.

• A list displays many records from one table in rows and columns. You can sort by a column, group records, perform bulk updates, and add columns via the list personalization gear.
• A form displays a single record for viewing or editing. Forms have sections, related lists, and field-level controls.

Filtering Lists

Breadcrumbs are read left to right: the leftmost segment is the table/base filter and each segment to the right narrows the result. Clicking a segment removes the conditions to its right.

Favorites and History

Favorites persist per user and can point to modules, filtered lists, or specific records. You create one by dragging an item to the Favorites tab or clicking the star. History is an automatic, time-ordered list of recently opened pages and is useful for retracing steps without rebuilding a filter.

Global vs Scoped Applications

This distinction is heavily tested.

Global is the legacy shared space where most baseline platform configuration historically lived. Scoped applications are isolated: their tables, scripts, and properties are namespaced so one app cannot silently break another. Modern best practice is to build new applications in their own scope.

Mental Model

flowchart TD
  A[Now Platform - single instance] --> B[One relational database]
  B --> C[Tables extend Task or base tables]
  A --> D[Next Experience UI]
  D --> E[Application Navigator: Apps and Modules]
  E --> F[Lists - many records]
  E --> G[Forms - one record]
  A --> H[Application Scope]
  H --> I[Global - shared]
  H --> J[Scoped - isolated namespace]

Understanding this model makes the heavier Database Management and Configuration domains far easier, because every UI element ultimately maps back to a table and a scope.