Hybrid workflows (examples)
Initial automated situation
Let's recall example 3 of the automated workflows.
A random number is generated and checked in the transitions. If this does not work, we retry until it works.
Human intervention
Human input in case of error
Now let's assume we have an expert at hand. If the first random number does not fulfil the conditions, we do not automatically try again, but instead we give up right away and rather give the task to our expert. He then selects a number manually because we think he can solve the problem better in this case.
Start the workflow (several times if necessary), look into the jobs and if the workflow job is in the human state, select Fill form from the context menu. When the job is finished, look at the log messages.
Import: (follow the instructions!)
We remove the waiting time in the first state so that there are no further cyclical checks after the initial check.
Furthermore, we add an additional state for the human input and set the priority of Transition 1 higher, so that the initial automatic check is always done first.
In the new state, we add a form in which the user is able to select a number. You know this from example 3 of the interactive workflows.
You can control who the human user is via the authorised users in the form. This provides automatic work dispatching.
Human selection of subsequent state in case of error
Another possibility is that we do not bother our expert at all with the selection of a number if the first random number does not fulfil the conditions. We know that he knows what the next sensible step is and let him select the next workflow state in the form. We achieve this by deactivating the automatic transition check in the form.
Start the workflow (several times if necessary), look into the jobs and if the workflow job is in the human state, select Fill form from the context menu. When the job is finished, look at the log messages.
Import: (follow the instructions!)
Forced initial human input/selection of subsequent state
Alternatively, you can of course force human input/selection via a form right in the first state and not even try with the initial random number.
Data transfer from profile to profile via workflow variables
Apart from 'pure' workflow variable values, lists and maps of profiles can be passed via workflow variable (i.e. from profiles in actions of transitions to form profiles in states). See VAR_AUTOSERIALIZE_DATA.
Furthermore, all variables of a profile can be written into a map with function copy variables into map() . This, of course, then also works in combination with VAR_AUTOSERIALIZE_DATA.
These lists and maps can be included as nodes in the source structure of a profile and used directly in the mapping (→ section Source structure menu).