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 actions.
Example
In a 4 state workflow you might want the workflow to move from a Rejected state to a more proactively named Triage state.
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 as JSON markup format.
"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 - please see JSON Trigger events.
For each event you can set one or more conditions - please see JSON Trigger conditions.
Trigger actions can be added to a single event - please see JSON Trigger actions.
For example:
"actions":[{"action":"action1"}, { "action": "action2"}]
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.
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