Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Getting started with workflows

Log in to subscribe to topics and get notified when content changes.

Getting started with workflows

The graphical workflow editor provides 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 workflow starts when a triggering event occurs. Common triggers include a record being inserted into a specific table, or a particular field in a table being set to a specified value. For example, you might create a workflow that runs whenever a user requests approval for an item they want to order from the catalog.

When an activity completes, the workflow transitions to next activity. An activity might have several different possible transitions to various activities, depending on the outcome of the activity. Continuing the example above, if the user's request is approved, the activity might transition to an activity that notifies someone to order the item; if the user's request is denied, the activity might transition to notifying the user that their request has been denied.

The graphical workflow editor represents workflows visually as a type of flowchart. It shows activities as boxes labelled with information about that activity and transitions from one activity to the next as lines connecting the boxes.

At each step in a workflow:
  1. An activity is processed and an action defined by that activity occurs.
  2. At the completion of an action by an activity, the workflow checks the activity's conditions.
  3. For each matching condition, the workflow follows the transition to the next activity.

When the workflow runs out of activities, the workflow is complete.