Certified System Administrator CSA Full Course Free

In ServiceNow Flow Designer, a data pill represents variables, record fields, or outputs from previous steps that can be used dynamically in the flow.

Data pills allow flow designers to reference record data without manually specifying table fields.

Dragging a data pill onto a flow step ensures that the correct values are automatically mapped from the referenced record.

This is the recommended method for using record data within a flow.

Why is Option D Correct?

Why Are the Other Options Incorrect?❌ A. Drag the table icon onto the flow definition

Incorrect because Flow Designer does not use table icons for referencing records.

Instead, it utilizes data pills and actions to retrieve and manipulate record data.

❌ B. Use the condition builder to specify the desired values

Incorrect because the condition builder is used for decision logic (e.g., If-Else conditions), not for referencing record data.

❌ C. Specify the source table on the data pill related list

Incorrect because you cannot manually specify a table in a data pill.

Data pills are automatically created when an action retrieves data from a record.

❌ E. Add the table reference using the slush bucket

Incorrect because slush buckets are used in ServiceNow for selecting multiple items (e.g., roles, groups), not for referencing record data in a flow.

ServiceNow Flow Designer - Using Data Pills

ServiceNow Flow Designer - Best Practices for Record Referencing

ServiceNow ITSM - Automating Workflows with Flow Designer

References to Official Certified System Administrator (CSA) Documentation:

On the Reports page in ServiceNow, different sections allow users to see which reports are visible to various audiences.

Why These Options Are Correct?✅ C. My reports

Displays reports created by the logged-in user.

These reports are private unless explicitly shared.

✅ E. Dashboards

Dashboards consolidate multiple reports and make them visible to specific audiences.

Users can share dashboards with groups or individuals.

✅ F. Global

Global reports are available to all users with reporting access.

These reports are not restricted to a specific user or group.

✅ I. All

The "All" section lists every report the user has access to, including:

Personal reports

Shared reports

Global reports

Reports from dashboards

Why the Other Options Are Incorrect?❌ A. Group

There is no "Group" section in the Reports page.

However, reports can be shared with groups, but there is no direct "Group" view.

❌ B. Department

Departments do not determine report visibility in the Reports page.

Report access is controlled by roles, users, and groups, not departments.

❌ D. Team

Teams are not a standard report visibility category in ServiceNow.

Reports are shared at user, role, and global levels, not by "Team."

❌ G. Admin

There is no "Admin" section in the Reports page.

However, Admins can access all reports via the "All" section.

❌ H. Analytics

Analytics is a separate module in ServiceNow, primarily used for Performance Analytics (PA) and dashboards.

It is not a standard report visibility section.

❌ J. Company

There is no "Company" section in the Reports page.

Reports can be shared at a global level, but not specifically by "Company."

ServiceNow Reports - Managing Visibility and Access

ServiceNow Reporting Guide - Sections of the Reports Page

ServiceNow Dashboards and Report Sharing Best Practices

References to Official Certified System Administrator (CSA) Documentation:

In ServiceNow, the personal_list role allows users to add or remove fields from a list view without requiring full administrator privileges.

Modify List Layout (Columns & Fields)

Users can add, remove, or rearrange columns in list views.

Save Personal List Preferences

Customizations apply only to the user, unless they have additional permissions to modify system-wide settings.

Does NOT Allow System-Wide Changes

Unlike the admin role, personal_list only affects personal views of lists, not global configurations.

A. personalize.control ❌ (Incorrect)

No such role exists in ServiceNow.

C. ui_page_admin ❌ (Incorrect)

This role allows users to manage UI Pages, but it does not provide list customization permissions.

D. ui_action_admin ❌ (Incorrect)

This role is used to manage UI Actions (buttons, links, and client-side scripts), not list view configurations.

Key Capabilities of the personal_list Role:Why Other Options Are Incorrect?

Role-Based List Customization

ServiceNow List Personalization

User Roles and Permissions

ServiceNow User Roles

References from ServiceNow CSA Documentation:

In ServiceNow, administrators can reuse the same notification content across multiple channels (such as email, SMS, and push notifications) by using Common Notification Content.

Consistency Across Channels

Ensures that the same message format is used across email, SMS, and push notifications.

Easier Maintenance

Instead of creating separate content for each channel, administrators can manage all notification content from one place.

Dynamic Content

Supports variables and dynamic placeholders to customize messages based on recipient data.

A. Configure Default notification content ❌

Incorrect: There is no "default notification content" feature in ServiceNow.

B. Enable Actionable notification content ❌

Incorrect: Actionable notifications allow users to take actions directly from the notification, but they do not manage common content.

D. Set up Related notification content ❌

Incorrect: No such feature as "Related notification content" exists in ServiceNow.

Key Features of Common Notification Content:Why Other Options Are Incorrect?

Common Notification Content Overview

ServiceNow Notification Management

Setting Up Common Notification Content

Creating Reusable Notification Content

References from ServiceNow CSA Documentation: