Configuring Applications for Collaboration
About 20% of the CSA exam — see all 6 domains.
What this domain covers
- Lists, Filters, and Tags
- List and Form anatomy
- Form Configuration
- Form templates and saving options
- Advanced Form Configuration
- Task Management
- Visual Task Boards (VTBs)
- Visualizations, Dashboards, and Platform Analytics
- Notifications
What it covers: lists, forms, filters, tags, task management, Visual Task Boards, dashboards/Platform Analytics, and notifications. This is heavily about day-to-day admin configuration.
Lists and forms are the two primary record views.
- A list shows many records; a form shows one record. List controls include column headers (click to sort), the condition builder / filter, the list mechanic breadcrumb, and personalizing columns via the gear/list controls.
- Filters are built with the condition builder (field → operator → value), can be AND/OR, and can be saved. A saved filter is shared through its visibility setting (Me, Group, or Everyone); a Favorite is a personal shortcut, not a way to share. The breadcrumb at the top of a filtered list lets you remove or edit conditions quickly.
- Tags let users label records for their own quick retrieval; tags can be personal or shared.
Form configuration:
- Form layout / Form Designer controls which fields appear and their arrangement.
- Form templates pre-populate field values to speed up record creation.
- Form sections, related lists, and UI elements (formatters, annotations) round out the form.
- Saving options: Save (stay on the form), Submit/Update (save and leave), Insert and Insert and Stay (create a copy as a new record).
Task management: ServiceNow's Task table is the parent of Incident, Problem, Change, and many others, so they share fields like Number, State, Assigned to, Priority. Priority is derived from Impact × Urgency via a Priority Data Lookup Rule (Data Lookup & Record Matching): a lookup table maps each Impact/Urgency combination to a Priority value. Precedence vs. business rules is order-dependent: in the order of execution, before business rules with order < 1000 run before the data-lookup engine, and those with order ≥ 1000 run after it (and can override the looked-up value). A before rule with order below 1000 sets its value first, so the data lookup can overwrite it. The lookup does not hold absolute precedence over all business rules.
Visual Task Boards (VTBs) are Kanban-style boards (Freeform, Guided, or Flexible) for managing tasks as cards across lanes. Only Guided board lanes map to a field, so moving a card updates the record. Flexible board lanes are custom, and moving a card does not change the task. Freeform boards display task records of any type, including personal tasks.
Platform Analytics is the current umbrella that unifies Reporting and Performance Analytics into one experience. Dashboards present reports and Performance Analytics indicators/widgets. (Use "Platform Analytics" for the product; "Performance Analytics" specifically means the indicator/time-series engine.) Reports are built on a table + a type (bar, pie, list, etc.) and can be scheduled or shared.
Notifications (System Notification > Email) send email based on events or conditions (e.g., when an incident is assigned). They have a When to send, Who will receive, and What it will contain.
Sample questions from this domain
Three of the 60 in this domain, with the reasoning. The full set is in the question bank.
An administrator wants new Change Request records to open pre-filled with a standard set of field values to save agents time. Which feature should they use?
- A. A data policy
- B. A form section
- C. A related list
- D. A form template ✓
Why: Form templates pre-populate field values when a record is created, speeding up data entry for repetitive cases. A data policy enforces mandatory or read-only rules on the server and on imports, but it does not fill in values. A form section only groups fields on the form layout, and a related list shows records associated with the current record.
On an Incident record, an agent clicks a save option that keeps them on the same form after saving their changes. Which option did they most likely use?
- A. Update
- B. Save ✓
- C. Insert
- D. Insert and Stay
Why: Save commits the changes but leaves you on the current record. Update saves and navigates away (back to the list). Insert creates a new record from the current one and leaves the form, and Insert and Stay creates a copy and stays on that new copy, so neither keeps you on the original record.
The Priority field on an Incident is read-only and is set automatically. It is most commonly derived from which two other fields?
- A. Severity and Impact
- B. Impact and Urgency ✓
- C. Category and Urgency
- D. Caller and Impact
Why: Out of the box, Priority is calculated from Impact and Urgency using a data lookup (the priority matrix). Severity is a separate Incident field that the default lookup does not use. Category and Caller help with routing and context, but neither is an input to the default Priority calculation, so any pairing that includes them is wrong.