...
The Follow Up Transition post function evaluates the workflow conditions of all the next transitions on the target status of the current transition. If exactly one condition is valid, that transition will be triggered as a follow-up.
Configuration
The Follow Up Transition post function does not have any additional parameters to configure, however, you must have a least one workflow condition configured.
Consider the following workflow:
...
Our issue has a mandatory number custom field.
At the end of the Go transition, we have configured a Follow Up Transition post function.
Each transition leading away from the status
has a workflow condition:Status colour Yellow title junction 'Under Five' has the condition: Number field < 5?
'Exactly Five' has the condition: Number field == 5?
'Over Five' has the condition: Number field > 5?
When the user performs the Go transition, this will always trigger a follow-up transition.
...
We have been careful to configure our workflow conditions so that always exactly only one condition can be true. This way, the user will never be stuck at the
| Status | ||||
|---|---|---|---|---|
|
Configuration
The Follow Up Transition post function does not have any additional parameters to configure, however, you must have a least one workflow condition configured.
Conditions
Let's continue the example from above, where a number field is evaluated. We will configure three conditions; one for each outgoing transition from the
| Status | ||||
|---|---|---|---|---|
|
Under Five
...
Exactly Five
...
Over Five
...
Asynchronous Execution
...
Simple Yes / No example
A simpler use case is when you have only two transitions leading away and you evaluate the same condition; one condition is negated.
...
See the Conditional Approval Process use case for another real-life example.
Asynchronous execution
| Include Page | ||||
|---|---|---|---|---|
|
Troubleshooting
Problem: Workflow is blocked at the Junction status
...