Workflow Terminology

An activity is a workflow block that organizes the individual actions the workflow performs as It runs

Activities are connected by transitions (lines) that establish the possible processing path

Conditions are an activity type available for a workflow

Conditions are used to transition - to move from activity to activity, you can add conditions

Stages

Workflows can provide a summary of workflow progress by updating any field designated as a Stage field

Activities are the organizational element that defines the individual actions a workflow performs as it runs. A transition, or line, establishes the processing paths or order in which activities are executed.

The three basic workflow activities are Approval, Notification, and Task. Approvals allow approvals to be generated and managed, while driving a record to fulfillment. Notifications allow users to be notified of events that occur during the workflow. Tasks allow task records to be created and modified. These activities are only available when the workflow is defined to run on a table which extends Tasks. Other activities include Timers which pause the workflow for a set period of time and Utilities which provide useful controls over the path of the workflow. Plugins can add specialized activities to the Core Activities list and custom activities can be created.

conditions are the start of a transition to the next activity in the workflow model, and all activities (except End) use conditions to route processing. Add conditions to activities by right-clicking the activity header. Approved, Rejected, Always, Skip and Error are common conditions.

Stages show workflow progress, but work a little bit differently for workflows that run against Service catalog Request Items [sc_req_item]. Still, add a designated stage field to any table (for example, Incident [incident]) for progress summaries.