| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
| Excerpt |
|---|
One or more |
When the named workflow event occurs, the trigger checks that any required condition is met and sets one or more actions.
Conditions
A condition must be met for the trigger to perform the specified action(s). Available conditions are
"conditions":[{"state": "(string value)"}]"conditions":[{"final":(boolean true/false)"true}]or“conditions":[{"final":false}]"conditions":[{"initial": (boolean true/false)
"final" condition is added together with another condition to an event, the condition is evaluated as an OR function.true}]or"conditions":[{"initial":false}]
The "initial" condition can be constrained to a named state in the workflow using the "state" condition.
| Info |
|---|
Boolean condition values |
Trigger conditions
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|
One or more workflow triggers can be added to a workflow using the visual editor or the code editor.
Triggers are created in JSON code.
| Code Block |
|---|
"triggers:"
[
{"event": "on-change-state",
"conditions":
[
{"state": "Rejected"} ],
"actions":
[
{"action":"set-message", "type":"info", "title":"Hey My Wonderful design and Tech Team", "body":"We have some work to do ... it was rejected!!!"}
]
}
] |
A workflow trigger can be added to a workflow using the visual editor or the code editor.
The code editor includes
color coding to easily distinguish property names, values, and different data types
autocomplete feature
dropdown selectors for available property names, including workflow trigger events, conditions, and actions
