State Triggers & Transitions Overview

A trigger is what causes an object to move from one state to another. There are three types of triggers:

  • Button: Added to configurable forms as buttons, which a user clicks to move the object from its current state to another state (e.g., clicking the Submit for Review trigger on a form will move the object to the In Review state).
  • Timed: Moves an object to a specified state and can perform actions on a nightly basis. For example, you can create a trigger that notifies users of an overdue deadline or reminds them to launch an assessment on a particular day. This trigger type can’t be added to the Creation state. Read more here: Timed Triggers & Nightly Emails Schedule.
If a single state contains multiple timed triggers with conditions, you must create separate transitions for each timed trigger.
  • Consume Orchestration Event: Uses an existing state or object type’s Send Orchestration Event action to automatically transition an object to another predefined state (e.g., Closing an audit object will also automatically close all issue objects in an Open state). This trigger type also can’t be added to the Creation state.
    The Creation state with a trigger configured to transition to the object to the Draft state.

Important Notes

  • Creating a transition on a trigger specifies the state an object moves to.
  • On that transition, you can create actions that happen once the object moves to the next state. 
  • Multiple triggers and transitions can be saved to a single state. 
  • You can also add conditions that define certain requirements before an object moves to the next state and/or an action is performed.
  • Read more here: Actions on Transitions and here: Add a Condition to a Transition
All triggers must have transitions saved to to successfully move the object from state to state. Read more here: Edit or Delete a Trigger, Transition, or Action.