A process is a stateful instantiation of a scenario. Specific users are assigned as the defined actors. At any moment you are at a specific state in the process, from which you can do a number of actions.
A process is a deterministic projection, generated by processing responses following the update instructions and transitions of the scenario.
Processes need to be explicitly started via an event with a process resource. This resource should only contain the
A unique identifier. If the scenario is part of a Live Contract, this must be resource id that's valid for the event chain.
The title of the process. By default this is copied from the scenario, but can be updated during the process.
The scenario that the process is instantiated from.
The id of the event chain that the process belongs to.
A set with (instantiated) actors. The keys are used to reference the actors.
A list of responses that were giving for this process. Applying these response always results the current state that the process is in.
The next states following the golden flow.
A set of instantiated assets. The keys are used to reference the asset.
The properties of each assets can be modified via an update instruction. However, it's not possible to add assets, as they're not defined in the scenario.
A set of immutable assets copied from the scenario. The keys are used to reference the definition.
The current state object is similar to the state as defined in the schema. However the
actionsproperty contains full actions, not just keys.
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 all the 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.
Dynamic transitions from the current state to the next.