---
title: "Transitions"
canonical: "https://support.appfire.com/space/CDMC/2192776606/Transitions"
format: markdown
---
> Macro (aura-html)

## Overview

**Workflow transition** is the action that moves a document from one **workflow state** to another. Transitions define the path a document follows through its lifecycle, such as from draft to review or from review to approval.

![Workflow overview diagram showing workflow states.](media://318cbd78-650a-438b-8296-8d8b1b97211c)

## Types of transitions

Each transition can be triggered manually (for example, by a user clicking a button) or automatically (for example, using a trigger or rule).

> ℹ️ You can add multiple transitions to a state, but only one of each transition type (automatic or manual) can be added to that state. Each transition is added to a specific state and includes its type and destination state.

## Automatic transitions

These transitions occur without user interaction, based on workflow events or conditions:

### Approved transition

- Occurs when a user (or all assigned users) approves the content.
- It can only be added to a state with content review (approval).

![Workflow editor showing an approved transition configured for a workflow state.](media://4c042100-9a32-4253-bf9c-d50430421c10)

### Rejected transition

- Occurs when a user (or all assigned users) rejects the content.
- Can only be added to a state that has a content review (approval).

![Workflow editor showing a rejected transition configured for a workflow state.](media://20a81a77-93ee-4dd3-bad6-bbafcaa3dc92)

### Updated transition

The **updated** transition must be added to the state. Can be added alongside other transition options, for example, a content review or a select transition.

- Occurs when a user edits and saves a change to the content.
- An **updated** transition removes any reviewers previously assigned using the workflow dialog if the state also contains a content review.

> 📝 Adding or removing a label or attachment does not affect the **updated** transition.

### Expired transition

The expired transition must be added to the state, which must be configured with a due date.

- Occurs when a due date added to the state is reached.
- If no due date is added (or has been removed before the due date), no expiry occurs.
- The[ content expiry workflow](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/2192776431) has an **expired** transition added to the **Approved** state.

A state can have one, more than one, or all of these possible transitions. The **approved** and **rejected** transitions are only available when the state contains an approval (content review).

> ℹ️ Transitions can also occur due to a trigger action listening for a workflow event, such as a change of state or a page approval. These can be added to the workflow as a JSON trigger.

## Manual transitions

These require the user to trigger the transition:

- **Select** – allows the user to choose from one or more destination states when transitioning the content.
  

### **Select transition** 

A select transition moves the page to another state based on your selection.

- When a state has select transitions configured, the *Workflow State* dialog displays a **Possible transitions** section. Each available transition is shown with its name and destination state.
- Click the transition name to move the page to the destination state.
  
- The **select** transition can’t be added to a state that contains an approval.

**Related topics**

- [States](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/2193066115)
- [Workflow state dialog](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/2193129918)
- [Workflow visual builder editor](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/2193162438)