Workflow Triggers
A workflow trigger is a plugin that runs code as a workflow transitions from one step to the next, letting a workflow do work beyond simply moving between steps.
Overview
Triggers attach to a workflow action and fire when that action is selected. They encapsulate system logic that isn't itself part of the workflow — versioning an asset, publishing it, assigning the next step, or sending an email.
An action can carry more than one trigger. Cascade CMS ships with the pre-defined triggers listed below, and custom plugin triggers can be added to run your own code during a step transition.
Most triggers accept parameters — optional elements that narrow what the trigger does, such as naming the Destination a Publish trigger should target. Each trigger's own page documents the parameters it supports.
Order matters
When a workflow uses the Version, Merge, and publish triggers together, they must appear in that order for all three to be recorded correctly.
Assignment triggers
These decide who owns the next step, overriding the step's default assignment.
- Assign Step If User — Advances to a specified step when the previous step was completed by a particular user.
- Assign To Content Owner of Asset — Assigns the next step to the asset's content owner.
- Assign To Group Owning Asset — Assigns the next step to the group with write access to the asset's parent folder.
- Assign to Specified Group — Assigns the workflow to a named group.
- Assign To Workflow Owner — Assigns the next step to whoever started the workflow.
- Preserve Current User — Keeps the acting user when a workflow is submitted to a group rather than an individual.
Publishing triggers
These publish or unpublish content as the workflow advances.
- Publish — Publishes the asset in workflow to every enabled Destination.
- Publish Parent Folder — Publishes the asset's parent folder.
- Publish Set — Publishes every asset in a named Publish Set.
- Publish Containing Publish Set — Publishes the Publish Sets the asset belongs to.
- Unpublish and Delete — Unpublishes the asset and deletes it in one step.
Asset triggers
These act on the asset itself or on the folder around it.
- Version — Stores a version of the asset in its version history.
- Merge — Merges the working copy back into the current version.
- Delete — Deletes the asset in workflow.
- Delete Parent Folder — Deletes the asset's parent folder and everything in it.
- Copy Folder — Copies the asset's parent folder to a designated location.
Notification and workflow triggers
- Email — Sends a notification or completion email about the following step.
- Create New Workflow — Starts workflows for analogous assets, supporting translation and cross-site synchronization.