Legacy Workflow

You can add default stages to use for a table, and stages to existing workflow

Update sets manage the published state of all versions of a workflow prior to committing the workflow version on a local instance.

A workflow is complete when it reaches the End activity, even if there are still active branches of the workflow in progress. To ensure that both branches are completed, add a Join activity to resolve the branches.

You can add input variables to existing workflows and add them to update sets.

Deleting workflow input variables, like insert and update actions, creates a customer update record in a user's current update set.

Troubleshooting tools for workflows enable administrators to isolate execution paths, compare contexts, and track incomplete activities.

Within workflow there are several different types of variables that are available.

The ValidateParentFlow validator reports any workflows that use the workflow as a subflow.

The ValidateTransitionIn validator finds activities that do not have inbound transitions and cannot execute in the workflow.

The ValidateScriptForCurrentDotUpdate validator finds workflow activities with scripts that use the current.update() function.

Tailor workflows exactly the way you want them.

Workflows that are associated with the Requested Item [sc_req_item] table have a specific type of workflow input.

You can do many things using the Workflow Editor.

The workflow engine runs in a predefined order relative to business rules and database operations. It caches commonly-used published workflows to improve performance.

The personalized JavaScript that users create in workflow activity variables is vulnerable to run-time syntax errors. Available error information is available in a tooltip when you point to a workflow activity in an error state.

The system employs two types of events: registered platform events and workflow events.

Workflow fields may indicate when a record required by the workflow is deleted.

The system tracks workflows in update sets differently than other records because workflow information is stored across multiple tables.

Workflow is a legacy application that provided a drag-and-drop interface for automating multi-step processes across the platform. Each workflow consists of a sequence of activities, such as generating records, notifying users of pending approvals, or running scripts. The graphical Workflow Editor represents workflows visually as a type of flowchart. It shows activities as boxes labeled with information about that activity and transitions from one activity to the next as lines connecting the boxes.

The workflow engine can generate detailed performance timing data that is useful for troubleshooting slow workflows.

You can enable the collection of workflow run time metrics to determine whether workflows are performing as expected or consuming additional resources.

Data separation restricts workflow contexts to users who are either in the same domain of the workflow or are members of a parent domain.

Domain separation is supported in the Workflow application. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

Workflow application scope determines the access that an application has to the information in a workflow, specifically to the data contained in the activities in that workflow.

Workflows can indicate workflow progress by updating any field designated as a stage field.

Stage sets are named groups of workflow stages commonly used together. Create a stage set and assign it as a default set to any number of tables. You can import the choice list values of a workflow field as stages for a workflow, and export a stage set to create a new one.

The system provides a timeline view of history activities associated with a workflow context.

Workflow validation examines different characteristics of a workflow to locate issues that might prevent the workflow from being published or cause it to fail. The validation report summarizes the results of each separate workflow validation.

To prevent users from making changes to a workflow that affect other users of the system, workflows must be checked out before they can be edited.

Enable workflow stage fields to display approvers, change the number of approvers to display, or disable displaying approvers.

The Encrypted Workflow Scratchpad plugin (com.snc.encrypted.scratchpad) provides encrypted scratchpad support for workflow context and workflow executing activities.

The graphical Workflow Editor provides a drag-and-drop interface for automating multi-step processes across the platform.

Create, edit, validate, and publish workflows to automate multi-step processes across the platform. Understand workflow activities and variables and how to use them effectively. Take a deeper look at how workflows are constructed, validated, and used.

You can monitor the status of workflow pause requests using Workflow Pause Request.

Use Workflow Pause Group Requests to pause, or resume, groups of workflows, or all active workflows. If pausing a group of workflows, use filtering functions to select the workflows. If pausing all active workflows, select the Pause All check box to indicate that all currently active workflows should be paused.

Pause individual workflow contexts. Specify the date and time of day at which the workflow context should resume.

The workflow context performs the activities and transitions defined in the workflow with the new record as current.

The following workflow activities trigger events.

Workflow uses several Glide events.

An existing workflow already contains two input variables.

In addition to being run based on conditions, workflows can also be scheduled to perform at a particular time, similar to a scheduled job.

Error handling provides visual cues within the workflow, such as error descriptions for activities in pop-ups, and detailed log records.

The ValidateSingleEnd validator finds and identifies multiple End activities in a single workflow.

The ValidateSubflows validator detects any workflows included as subflows that are either inactive, deleted, or not available as a published workflow for the current user.

The ValidateDanglingTransition validator finds and reports any transitions that do not terminate on an activity.

The ValidateInputVarUpdateSetDependencies validator examines update sets to ensure that workflow input variables for a given workflow have not been deleted in different update sets than those currently In progress.

The ValidateLowestCommonTable validator reports the lowest table in the Glide hierarchy that the workflow uses.

The ValidateTableChange validator reports any activities in the workflow that are invalid given the table associated with the workflow version.

The ValidateTransitionOut validator finds activity conditions with no exit transitions.

The ValidateUpdateSetDependencies validator identifies all the subflows called in the current workflow and determines if any of those subflows are being edited in a different (in progress) update set.

The ValidateUpdateSetParentDependencies validator identifies all the workflows that call the current workflow as a subflow and determines if any of those parent workflows are being edited in a different update set that is in progress.

The ValidateWorkflowStageColumn validator detects and reports when the stage field (stage column) for a workflow is not correct or is unusable.

The ValidateWorkflowEndStages validator checks that in workflows with stages, the end activity of the workflow has a stage named Complete or Completed.

The ValidateWorkflowStateValues validator checks a number of stage aspects in workflow activities for correctness.

When a workflow is opened in the canvas, the title bar displays the workflow title and the workflow status in italics. Possible states are Checked out by <name> and Published.

Several workflow events are available in the base system.

There are several functions that relate specifically to workflow events.

A workflow stage field displays icons to indicate the workflow stage.

The default workflow palette contains workflow activities and existing workflows you can use as subflows.

In the properties of a workflow, you can configure settings such as its application scope, start conditions, schedule, inputs, stages, and run time metrics. You can also view information such as the workflow author, version, and history.

Certain roles are required to use workflows.

Workflow stage renderers determine how a workflow displays stages in a workflow field.

For full flexibility, workflows store information over a number of different tables.

ServiceNow offers several workflow validators for workflow designers to test their workflows.

You can request the Workflow Pause Utility plugin (com.glideapp.workflow.pause) if you have the admin role. This plugin may include demo data and activates related plugins if they are not already active.

Canceling a workflow stops the workflow from executing and sets the workflow context State to Canceled. To cancel an executing workflow, you can use the cancelContext(context) script. You can define an onCancel script to clean up unresolved workflow activities.

An administrator can reroute the workflow when a script error occurs by creating an error condition exit for specific activities within the workflow. This allows the workflow to process script errors in a predictable way and not create undesirable results.

Automate a multi-step process by creating a workflow with the Workflow Editor.

Automate a multi-step process by creating a workflow from the list view of any table that supports workflows.

Automate a multi-step process by creating a workflow from an SLA definition.

Workflows can provide a summary of workflow progress by updating any field of the Workflow type. If the field is a workflow field, it displays an icon to indicate the workflow stage progress.

When you create a new service catalog item, you can create a new corresponding workflow at the same time.

Review the process of preparing a subflow for use in a parent workflow, and for preparing the parent workflow to use a subflow.

Approval activities react differently to script errors than the other activities.

A Stage field allows the workflow context to show additional workflow information, such as the stage name and the estimated completion time for an activity.

On the Workflow Operations Dashboard, view and add widgets to help you monitor workflows. Review the performance of workflows and determine which workflows must be improved.

You can add or modify workflow stages.

Use this process to pass variables from a parent workflow to a subflow.

Use keyboard commands to navigate and operate the Workflow Editor Welcome page.

To complete a workflow, you add workflow activities, validate the workflow, and publish it.

Use keyboard commands to navigate and operate the Workflow Editor canvas.

The Workflow Editor is an interface for creating and modifying workflows by arranging and connecting activities to drive processes.

The platform includes accessibility features that makes the interface accessible to users with disabilities.

Workflow Pause Utility provides functionality you can use to pause or resume all workflow contexts, a subset of qualified workflow contexts, or individual workflow contexts. You designate the data and time of day at which the paused workflows should resume, and can manually resume individual workflows as needed.

A workflow can launch another workflow as an activity.