The state a process that's instantiated from this scenario can be in.
All the possible states are described in the
statessection. Each state describes through which
actionit can transition to a new
- response: ok
- response: cancel
- action: complete
- action: next
A short title for the state.
A long description for the action that is shown when if the state is current or part of the golden flow.
Instructions that can be specific per actor. This is an object where the keys correspond with the actor keys.
employee: Fill out this form
employer: Waiting for employee to fill out the form
"employee": "Fill out this form",
"employer": "Waiting for employee to fill out the form"
An array with the keys of all actions that may be performed in this state.
The order of the actions matter, especially for automated actions. The first available action is considered to be the default action. This action is followed when determining the golden flow.
If there is only one action available action, you may replace the
actionsproperty with an
actionproperty with a single action key as value.
A transition defines the change from one state to the next. State transition definitions are more dynamic than the transition you can set in the response object.
Transitions are evaluated in order. If multiple transitions apply, only the first one is used.
Key of the action that must be performed for this transition to be selected.
Key of the response for which this transition would be selected.
A boolean that must be true for the transition to be selected. This is typically a data instruction.
Key of the state where to transition to.