Full Access ServiceNow CSA Tutorials

InServiceNow,Visual Task Boards (VTBs)provide aKanban-style interfaceto manage and track work. There arethree main typesof Visual Task Boards, but " Feature " is notone of them.

Freeform Board (Valid Type)

Manually created boards wherecards can be moved freelywithout predefined conditions.

Users canadd and organize tasks as needed.

Example: Personal task management.

Guided Board (Valid Type)

Createdfrom a list viewandlinked to a ServiceNow table(e.g., Incident, Change, Task).

Cards on the boardautomatically updatebased on conditions.

Example: Managing Incidents or Change Requests.

Flexible Board (Valid Type)

Similar toGuided Boards, but allows users tomanually reordertasks within lanes.

Offers moreflexibilitywhile still being linked to a data source.

Example: Sprint Planning or ITSM Workflows.

" Feature " is NOT a Visual Task Board type in ServiceNow.

ServiceNow does use the term " Feature " in Agile Development (for tracking high-level product functionalities), but it is not related to VTBs.

Types of Visual Task Boards in ServiceNow:Why is " Feature " Incorrect?

Why Other Options Are Correct?Guided, Flexible, and Freeformare thethree valid typesof Visual Task Boards in ServiceNow.

Visual Task Boards Overview

ServiceNow Visual Task Boards

Types of Visual Task Boards

Creating and Using VTBs

References from ServiceNow CSA Documentation:

InServiceNow Flow Designer, users can accessdetailed informationabout actions added to a flow via theHelp Panel. The Help Panel providescontextual guidanceand documentation about the available actions, conditions, and steps within the flow.

Displays Information About Actions:

When an action is selected in Flow Designer, theHelp Panelprovidesdescriptions and usage details.

Helps users understandwhat the action doesand how to configure it.

Accessing the Help Panel:

Inside Flow Designer, users can click theHelp icon ( ? )or expand the Help Panel from the side.

This providesinline documentationfor added actions.

Guidance for New Users:

The panel providesServiceNow documentation links and tipsto help users build flows effectively.

Key Features of the Help Panel:Why Option C (Help Panel) is Correct?TheHelp Panelprovides built-in documentation and details about actions added to the flow.

Why Other Options Are Incorrect?A. Virtual Agent Help→ Incorrect

Virtual Agent Help is related tochatbot and conversational assistance, not Flow Designer.

B. Local Action Help→ Incorrect

No such feature exists in ServiceNow; action details are found in theHelp Panel.

D. Flow Assistant→ Incorrect

Flow Assistanthelps withbuilding expressions and selecting data pillsbut does not provide action documentation.

ServiceNow Docs – Flow Designer Help

ServiceNow Learning – Flow Designer and Automation Best Practices

ServiceNow Developer Portal – Flow Designer Action Configuration

References from Certified System Administrator (CSA) Documentation:

InServiceNow, administrators canreuse the same notification contentacross multiple channels (such asemail, SMS, and push notifications) by usingCommon Notification Content.

Consistency Across Channels

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

Easier Maintenance

Instead ofcreating separate contentfor 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 totake 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:

InServiceNow Knowledge Management, thepublishing and retiring process for knowledge articlesis managed throughWorkflows. These workflows define the steps an article must go through before it is published, updated, or retired.

Submission:

A user creates a knowledge article and submits it for approval.

Approval Process:

Based on the workflow, an article may require manager or SME (Subject Matter Expert) approval.

Publishing:

Once approved, the article ispublishedand made available in the Knowledge Base.

Updating & Versioning:

If edits are needed, the article enters adraft or reviewstate.

Retirement:

When an article is no longer needed, it follows the workflow toretire or archiveit.

Knowledge Approval Publish(requires approval before publishing)

Knowledge Instant Publish(automatically publishes the article)

Knowledge Retire(handles retiring or archiving articles)

A. Approval Policies(Incorrect)

ServiceNow does not use a separate " Approval Policy " for knowledge articles; approvals are managed within the workflow.

B. Approval Definitions(Incorrect)

There is no such specific feature in ServiceNow. Approvals are configured within workflows, not separate definitions.

C. Workflow Designer(Incorrect)

TheWorkflow Designeris a tool used tocreate workflows, but it does not control the publishing process directly. The workflows themselves do.

E. State Lifecycle(Incorrect)

While knowledge articleshave a lifecycle (Draft → Review → Published → Retired), this is controlledby workflows, not by an independent " State Lifecycle " feature.

Knowledge Workflows

ServiceNow Knowledge Management

How Workflows Control Knowledge Article Publishing & Retiring:Common Knowledge Workflows in ServiceNow:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation: