Workflow Best Practices Introduction (KB0538524)

Part of the ServiceNow platform that automates the multi-step process.

A Workflow is defined as a series of Activities that follow execution paths.
An Activity is a set of instructions that can include script, logging, approvals, record processing, timers, and wait time.
- Activities can process inputs from other Activities
- Activities can provide output for other Activities to process
- Processing continues as the Activity determines which execution path to follow upon completing its work
Workflows use conditions and their table associations to determine when to start, execute, continue, and end.

Part of the ServiceNow platform that automates the multi-step process.

Automation
- Workflows are reusable
- Workflows can call other workflows (called subflows)
Expansion of Self-Service offerings
Standardization of processes
Feedback to stakeholders in a timely fashion (stages, notifications)

When to use a workflow:

Automate a defined, multi-step process
Automate a repeatable process
When logic can be modularized
When a standard response is needed for every table Glide Record transaction insert, update, delete, and create

When not to use a workflow:

If a response to every transaction cannot be standardized when set, workflows execute on every Glide Record transaction
For example, if a workflow is defined for the Request [sc_request] table, the workflow runs on every insert, update, delete, and create
If end conditions are not defined.

Click the following links to view each Workflow Best Practices section.

Notifications