Triggers
A JSON trigger
contains three different properties
Multiple trigger events can be added to a workflow.
A single trigger event will include one or more action actions.
Example
In a 4 state workflow, you might want the workflow to move immediately from a Rejected state to a more proactively named Triage state, rather than waiting for a user to manually transition the content.
o
You can use a trigger to listen for the state change event to the Rejected state and set the trigger action to immediately transition to the Triage state.
o
The trigger can be added to a workflow using workflow builder but it must be added in JSON markup notation.
"triggers": [ {"event":"on-change-state", "conditions": [ {"state":"Rejected"} ], "actions": [ {"action":"change-state", "state":"Triage"} ]} ]
If you want to add this trigger to a workflow using workflow builder, copy and paste the JSON code format (without the opening "triggers":
JSON markup notation) to the Triggers dialog in the Edit Workflow panel in workflow builder.
There are a number of events that can be used in a trigger - see JSON Trigger events
For each
event
you can set one or moreconditions
- see JSON Trigger conditionsTrigger
actions
can be added to a singleevent
- see JSON Trigger actions
Each action is enclosed in a pair of curly brackets { ... }
. Multiple actions are added as a comma-separated list. This list of actions is then enclosed in a pair of square brackets [ ...]
.
For example:
"actions":[{"action":"action1"}, { "action": "action2"}]
"actions":[{"action":"change-state", "state":"Triage"}, {"action":"set-message", "type":"warning", "body":"Rejected content, triage actions required", "mode":"autoClose"}]
Each trigger action can have a number of mandatory elements and optional elements depending on the action.
Trigger action and page workflow history
For audit purposes, both the rejected decision transition to the Rejected state and the subsequent trigger transition to Triage are recorded in the page workflow history.
o