Overview
Configuring Applications for Collaboration is about the screens and signals that let people work together on records. It starts with lists (condition builder filters, breadcrumbs, grouping, list editing, tags) and forms (fields, sections, related lists, views, reference fields), then moves to configuring them with Form Layout or Form Designer, saving work with templates and options like Insert and Stay, and refining forms with formatters, reference qualifiers and dependent fields.
The second half is about collaboration on work: the Task table that incidents, problems and changes extend, assignment and approvals, work notes versus additional comments, Visual Task Boards for visual work management, visualizations and dashboards in Platform Analytics, and email notifications driven by record changes or events. It leans on Domain 1 navigation and feeds directly into Self Service & Automation, where catalog tasks and flows produce the records these tools manage.
How it's tested
Questions describe a user goal in a list, form, board, dashboard or email and ask which feature or setting achieves it, or why something did not behave as expected. Troubleshooting stems are common: an email was not received, a card move did not change a field, a filter returned the wrong records. Read for the exact behaviour required, not the feature name that sounds closest.
-
Which feature does this
A collaboration need is described (copy a record, share a filtered view, see work visually, alert a group) and you choose the platform feature built for it.
-
Why did it not happen
A notification, board or form behaved unexpectedly and you identify the setting responsible, such as recipient options or board type.
-
Scope of a list or form change
You decide whether a change affects one user, one view or all users, for example personal columns versus list layout versus a form view.
A manager wants a board where dragging an incident from one lane to another changes its assignment group automatically. Options are a freeform board, a flexible board, a guided board on Assignment group, and a dashboard. Only a guided board ties lanes to a field value, so moving a card updates the record. Freeform and flexible boards let users organise cards, but lane moves do not change the field.
Objectives 9
Official objectives from the ServiceNow outline, in outline order.
3.1 Lists, Filters, and TagsFinding, narrowing and labelling records in lists.
- What it means
- Lists show records from one table. The condition builder creates filters from conditions joined by AND and OR, breadcrumbs show the active conditions, and tags are labels users attach to records to find them later.
- What to understand
- Clicking a breadcrumb removes every condition to its right, Show Matching and Filter Out from a cell's context menu build conditions quickly, and filters can be saved and reused. Tags can be private or shared with other users or groups, and a tagged record can be found by filtering on its tag.
- How it shows up
- A user needs incidents that are either priority 1 or assigned to their group and still active, and you identify the condition structure that returns exactly those records.
- Common confusion
- Mixing up AND and OR placement, which changes the result set, or thinking a breadcrumb click removes only the condition clicked.
3.2 List and Form anatomyThe parts of lists and forms and what each control does.
- What it means
- A list has a title bar with menus, a filter breadcrumb, column headers with context menus, row checkboxes with bulk actions, and paging. A form has a header with a context menu, fields, sections, related links, related lists, and field status indicators.
- What to understand
- Reference fields store a link to another record and offer a lookup icon and a preview icon; a red indicator marks a mandatory field that is empty; related lists at the bottom show records linked to the current one. The activity stream on task forms distinguishes work notes, visible to fulfillers, from additional comments, visible to the requester.
- How it shows up
- A question points to a form element (the preview icon, a related list, a field indicator) and asks what it shows or does.
- Common confusion
- Treating work notes and additional comments as interchangeable, when only additional comments are meant for the caller.
3.3 Form ConfigurationChanging which fields appear and where, by view.
- What it means
- Administrators change form content with Form Layout (a two-column slushbucket that can add dot-walked fields) or Form Designer (a drag-and-drop editor), arranging fields into sections. Changes apply to the form view being edited.
- What to understand
- A view is a named version of a form or list layout, such as Default or Self Service, and view rules can choose a view by condition or device. Editing the layout of one view does not change the others, so a request for one audience usually means a separate view.
- How it shows up
- A team wants a simpler incident form without affecting the service desk, and you choose to create and configure a separate view.
- Common confusion
- Editing the Default view for one team's needs, which changes the form for everyone who uses that view.
3.4 Form templates and saving optionsPrefilling forms and choosing how a record is saved.
- What it means
- A template stores field values that can be applied to a new or existing record to fill common entries quickly. Saving options include Save (stay on the form), Submit or Update (save and leave), Insert (save as a new record and leave) and Insert and Stay (save as a new record and stay on it).
- What to understand
- Insert and Insert and Stay create a new record from the current values and leave the original unchanged, which makes them a quick way to copy a record. Templates can be kept personal or shared with groups or everyone, and applying one overwrites the fields it contains.
- How it shows up
- A fulfiller needs a new incident almost identical to the open one and wants to keep editing the copy, which points to Insert and Stay.
- Common confusion
- Using Save or Update after changing values, which overwrites the original record instead of creating a new one.
3.5 Advanced Form ConfigurationFormatters, reference qualifiers, dependent fields and related lists.
- What it means
- Advanced options refine form behaviour without code: formatters add non-field elements such as the activity stream or process flow; reference qualifiers limit which records a reference field offers; dependent fields filter one choice list by another; annotations add guidance text; related lists can be added or removed.
- What to understand
- A reference qualifier restricts the lookup choices (for example only active users in one department) using a simple condition, a dynamic filter or an advanced script. Dependent fields make subcategory choices follow the selected category. These are configuration, not customization.
- How it shows up
- Users keep selecting inactive users as the caller, and you choose a reference qualifier on that field.
- Common confusion
- Using a UI policy to hide wrong choices, when the right tool to limit reference lookup results is a reference qualifier.
3.6 Task ManagementThe Task table, assignment, approvals and work notes.
- What it means
- Task is a base table that incident, problem, change and catalog task extend, so they share fields such as Number, State, Assigned to, Assignment group, Priority and Active. Work is routed with assignment rules or flows, and approvals are recorded as approval records linked to the task.
- What to understand
- Because these tables inherit from Task, features built on Task (assignment, approvals, SLAs, the activity stream) work across all of them. Assignment rules can set the group or person automatically based on conditions, and priority on incidents is commonly calculated from impact and urgency rather than set directly.
- How it shows up
- A question asks why a field added to Task appears on incident and change forms, or how to route incidents to a group automatically.
- Common confusion
- Thinking fields must be added separately to each task type, or confusing the assignment group with the user record's group membership.
3.7 Visual Task Boards (VTBs)Freeform, guided and flexible boards for visual work.
- What it means
- Visual Task Boards show tasks as cards in lanes. Freeform boards are not tied to a list and cards are added manually; guided boards are based on a list and use a field as the lanes; flexible boards are based on a list but with lanes users define.
- What to understand
- On a guided board, moving a card to another lane updates the underlying field (for example State or Assigned to). On flexible and freeform boards, lanes are for organising and moving a card does not change the record's field. Boards can be shared with members for team collaboration.
- How it shows up
- A team wants card moves to change the state of each task, and you choose a guided board with State as the lane field.
- Common confusion
- Expecting a flexible board to update records when cards move, because it is also built from a list.
3.8 Visualizations, Dashboards, and Platform AnalyticsReporting on current data and trends, and sharing it.
- What it means
- Platform Analytics brings visualizations (reports), dashboards and Performance Analytics together. Visualizations show the current state of table data as charts, lists or single scores; dashboards combine them with filters; Performance Analytics indicators collect scores on a schedule to show trends over time.
- What to understand
- A standard visualization queries data at the moment it is viewed, so it cannot show how a measure changed over past weeks unless that history is collected; Performance Analytics data collection jobs store scores for trends, targets and breakdowns. Sharing controls who can see a visualization or dashboard, and scheduled delivery can email results.
- How it shows up
- A manager wants to see whether the open-incident backlog is rising week by week, which points to a Performance Analytics indicator rather than a one-off bar chart.
- Common confusion
- Assuming a standard report can show historical trends of a value that is not stored over time.
3.9 NotificationsWhen an email sends, who gets it and what it says.
- What it means
- An email notification is defined by three parts: when to send (record inserted or updated with conditions, or an event fired), who will receive (users, groups, users or groups in fields, event parameters) and what it will contain (subject, message, email template).
- What to understand
- Events let scripts or flows trigger notifications, passing recipients or data in parm1 and parm2. Send to event creator controls whether the person who caused the change is notified, the weight setting suppresses lower-weight duplicates to the same recipient, and users can manage their own notification preferences.
- How it shows up
- An admin tests a notification by updating a record and receives nothing, while others do; the cause is that Send to event creator is not selected.
- Common confusion
- Assuming the notification is broken when the tester was excluded as the event creator, or forgetting that outbound email must be enabled for the instance.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Condition builder AND vs. OR
AND narrows the result by requiring every condition, while OR widens it by accepting records that match either condition.
- Remember
- Clicking a breadcrumb removes all conditions to its right, not only the one clicked.
- Tested as
- Filter questions test whether a given condition set returns the intended records.
- Trap
- Reading 'active and priority 1 or 2' without checking whether the OR applies to priority only.
-
Tags
User-created labels on records that let people group and find records across lists.
- Remember
- Tags can be kept private or shared with specific users, groups or everyone.
- Tested as
- The answer for lightweight, user-driven labelling without adding a field.
- Trap
- Creating a new choice field when users only need personal or team labels.
-
Reference field
A field that stores a link to a record in another table and displays a value from it, such as a user's name.
- Remember
- It offers a lookup icon to search and a preview icon to view the referenced record.
- Tested as
- Form anatomy and dot-walking questions rely on knowing what a reference stores.
- Trap
- Thinking the display text is copied into the record rather than linked.
-
Form view
A named layout of a form or list, such as Default or Self Service, that can differ from other views of the same table.
- Remember
- Layout changes apply only to the view being edited, and view rules can select a view automatically.
- Tested as
- Used when one audience needs a different form without affecting others.
- Trap
- Editing the Default view for a single team.
-
Insert and Stay
Saves the current form values as a new record and keeps the user on that new record.
- Remember
- The original record is not changed; Insert does the same but returns to the previous page.
- Tested as
- The answer for quickly copying a record and continuing to edit the copy.
- Trap
- Choosing Save, which updates the original.
-
Template
A stored set of field values that can be applied to a form to fill it quickly.
- Remember
- Templates can be personal or shared and overwrite any fields they contain when applied.
- Tested as
- Appears in questions about speeding up repetitive record creation.
- Trap
- Confusing a template with a default value, which applies automatically to every new record.
-
Reference qualifier
A filter on a reference field that limits which records users can pick.
- Remember
- It can be simple (conditions), dynamic (a saved dynamic filter) or advanced (a script).
- Tested as
- The answer when users select inappropriate records in a lookup.
- Trap
- Choosing a UI policy or ACL to restrict lookup choices.
-
Task table inheritance
Incident, problem, change and catalog task extend the Task table and inherit its fields.
- Remember
- A field added to Task appears on every table that extends it.
- Tested as
- Explains shared fields, shared assignment and shared SLAs across task types.
- Trap
- Adding the same field to each child table separately.
-
Work notes vs. additional comments
Work notes are internal to fulfillers; additional comments are visible to the requester and usually trigger a customer notification.
- Remember
- Use additional comments only for text the caller should read.
- Tested as
- Frequent in task collaboration scenarios.
- Trap
- Posting internal troubleshooting in additional comments.
-
Guided Visual Task Board
A board built from a list where lanes are values of a chosen field.
- Remember
- Moving a card between lanes updates that field on the record.
- Tested as
- The answer whenever card moves must change data.
- Trap
- Choosing a flexible board, whose lane moves do not update records.
-
Performance Analytics indicator
A measure, such as number of open incidents, whose score is collected on a schedule to show trends.
- Remember
- Trends need collected scores over time; a standard visualization shows only current data.
- Tested as
- The answer when a stem says 'trend', 'over time' or 'week by week'.
- Trap
- Picking a bar chart of current records for a historical question.
-
Notification: when, who, what
Each notification defines when to send, who will receive it and what it will contain.
- Remember
- Triggers are record insert or update with conditions, or a fired event.
- Tested as
- Most notification questions map to one of these three sections.
- Trap
- Looking for recipients in the message content section.
-
Send to event creator
A recipient option that controls whether the user who caused the triggering change also receives the email.
- Remember
- When it is cleared, an admin testing by updating the record will not receive the email.
- Tested as
- A classic 'why did I not get the email' question.
- Trap
- Concluding the notification conditions are wrong.
-
Event and parameters
A named event, queued by a script or flow with the record and two parameters, that notifications can be set to fire on.
- Remember
- parm1 and parm2 can carry recipients or values for the email.
- Tested as
- The answer when an email must be triggered by something other than a simple field change.
- Trap
- Thinking every notification must be tied to an insert or update.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Freeform vs. guided vs. flexible Visual Task Boards
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Freeform | Board not based on a list; cards added manually | Lanes are custom and card moves do not change records | Expecting it to stay in sync with a list |
| Guided | Board based on a list with lanes from a field | Moving a card updates the lane field on the record | Forgetting that a lane move changes data |
| Flexible | Board based on a list with user-defined lanes | Lane moves organise cards but do not update fields | Assuming it updates records like a guided board |
Save vs. Insert vs. Insert and Stay
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Save / Update | Writes changes to the current record | Original record is modified | Using it to make a copy |
| Insert | Saves current values as a new record | Original unchanged; returns to the previous page | Expecting to stay on the new record |
| Insert and Stay | Saves current values as a new record | Original unchanged; stays on the new record | Confusing it with Save |
Visualization vs. dashboard vs. Performance Analytics
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Visualization (report) | Chart, list or score from table data | Reflects data as it is now | Using it for historical trends |
| Dashboard | Collection of visualizations with shared filters | Combines views; does not store history itself | Assuming a dashboard adds trend data |
| Performance Analytics indicator | Measure with scores collected on a schedule | Shows trends, targets and breakdowns over time | Expecting history before collection started |
Work notes vs. additional comments
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Work notes | Internal journal for fulfillers | Not shown to the requester | Using them to update the caller |
| Additional comments | Customer-visible journal | Shown to the requester and often emailed | Posting internal details there |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Save to copy
- What candidates pick
- Change a few fields and click Save to produce a similar record.
- Why it looks right
- Save is the most familiar button.
- Why it's wrong
- Save writes the changes to the existing record; Insert or Insert and Stay creates a new record and leaves the original intact.
Clue to watch for The stem says 'similar', 'copy' or 'new record based on this one'.
-
Flexible board for data updates
- What candidates pick
- A flexible board when moving cards must change the State field.
- Why it looks right
- Flexible boards are built from a list, so they seem linked to the data.
- Why it's wrong
- Only guided boards map lanes to a field, so only they update records when cards move.
Clue to watch for Moving a card must 'update', 'change' or 'set' a field.
-
Report for a trend
- What candidates pick
- A bar chart of open incidents grouped by week opened.
- Why it looks right
- It shows weeks on an axis and looks like a trend.
- Why it's wrong
- It shows when current records were opened, not how the open backlog changed over time; that needs collected Performance Analytics scores.
Clue to watch for Words like 'trend', 'over time' or 'compared with last month' about a changing value.
-
Missing email during testing
- What candidates pick
- Rewrite the notification conditions because the admin did not receive the email.
- Why it looks right
- Conditions are the usual cause of notifications not firing.
- Why it's wrong
- If others receive it, the conditions work; the tester was the event creator and Send to event creator is cleared.
Clue to watch for The admin made the triggering change and other recipients did receive the email.
-
Default view for one team
- What candidates pick
- Remove fields from the Default incident view so the facilities team sees a simpler form.
- Why it looks right
- It is the fastest way to simplify the form.
- Why it's wrong
- Everyone using the Default view loses those fields; a separate view, selected for that team, meets the need.
Clue to watch for The request comes from one team and others must keep their form.
-
UI policy to limit lookup choices
- What candidates pick
- A UI policy to stop users picking inactive users in a reference field.
- Why it looks right
- UI policies control field behaviour on forms.
- Why it's wrong
- UI policies set mandatory, visible or read-only; restricting which records a lookup offers is the job of a reference qualifier.
Clue to watch for Users select the wrong records from a reference lookup.
-
Internal note to the caller
- What candidates pick
- Post troubleshooting details in additional comments.
- Why it looks right
- It keeps everything visible in one place.
- Why it's wrong
- Additional comments are visible to the requester and usually emailed; internal details belong in work notes.
Clue to watch for The information is meant only for the support team.
Answer framework
Use these steps to choose the right collaboration feature or diagnose why one misbehaved.
- Name the outcome exactly: find records, change a form, copy a record, see work visually, measure over time, or alert people.
- Decide the audience and scope, since one user, one view, one team or everyone each points to a different setting.
- For records and forms, check whether the original must stay unchanged, which separates Save from Insert and Insert and Stay.
- For boards and analytics, ask whether data must change on a card move (guided board) or history is needed (Performance Analytics).
- For notifications, walk through when, who and what in order, then check Send to event creator, weight and user preferences before blaming conditions.
Practice question
Want more like this? The ServiceNow CSA practice test has questions for every domain.
Checklist
0 of 15
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Work through the objectives in the outline's order, because each builds on the last: lists and filters, then list and form anatomy, then form configuration, templates and saving options, and advanced form configuration. Do every step in a Personal Developer Instance rather than reading about it, since questions test exact behaviour such as what a breadcrumb removes or where Insert and Stay leaves you.
The high-priority concepts are the Task table and its children, Visual Task Board types, and notifications. Create one board of each type and move cards to see which one changes the record. Build a notification from scratch, trigger it yourself with Send to event creator on and off, and trigger it with an event to see parm1 used as a recipient.
Candidates commonly underestimate Platform Analytics. Build one visualization and one dashboard, then read how a Performance Analytics indicator collects scores so you can tell a current-state question from a trend question.
Afterwards, move to Self Service & Automation, whose catalog tasks and flows create the records you have just learned to manage, and drill mixed practice sets that include troubleshooting stems.
FAQ
Why is this domain weighted so heavily?
It is 20% of the exam because lists, forms, tasks and notifications are what administrators configure most often. It also has the most objectives of any domain, nine in total.
What is the difference between Form Layout and Form Designer?
Both change which fields appear on a form view. Form Layout uses a two-column slushbucket and makes dot-walked fields easy to add, while Form Designer is a drag-and-drop editor for arranging fields and sections visually.
When should I use a template instead of a default value?
A default value fills a field automatically on every new record, while a template is applied on demand and can fill several fields at once. Use templates for common scenarios that apply only some of the time.
Which Visual Task Board updates records when cards move?
Only a guided board, because its lanes are values of a field. Freeform and flexible boards organise cards without changing the underlying records.
Do I need deep Performance Analytics knowledge?
Expect to know what indicators, breakdowns and data collection do and when trend reporting needs them. Detailed indicator source design is beyond the core of this domain.
Why might a user not receive a notification they should get?
Common causes are Send to event creator being cleared when they made the change, a higher-weight notification to the same recipient suppressing it, the user's own notification preferences, or outbound email being disabled.
How many questions should I expect from this domain?
At 20% of 60 questions, plan for about twelve. ServiceNow does not publish per-domain counts, so treat that as a planning estimate.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 3 knowledge
You have covered lists, forms, saving options, tasks, boards, analytics and notifications. Check that you can pick the exact feature, and diagnose a misbehaving one, under timed conditions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the ServiceNow CSA AI tutor Get any concept explained your way