...
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 a user performs the Go transition, this will always trigger a follow-up transition.
For example, if the a user enters Number=3 during the Go transition, this leads to the
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
We configured our workflow conditions so that always exactly only ever one condition can be true. This way, the user will never be stuck at the
| Status | ||||
|---|---|---|---|---|
|
Conditions
Use conditions to ensure that only ever one transition is possible for the follow-up transition. 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
...
Simple Yes / No example
A simpler use case is when there are only two transitions leading away from status and you evaluate the same condition; one condition is negated.
...
Check it: Follow Up Transition post function
Yes: Condition a == b?
No: Condition a != b?
Fast forward example
Some extra steps in your workflow might only be necessary if a condition is not fulfilled. Otherwise, that step could be skipped.
...
Management approval
See the Conditional Approval Process use case for another real-life example.
...
Usually, the problem can be tracked down by reviewing the expected outcome of the post function;
if exactly one condition is valid, the corresponding transition will be triggered.
| Info |
|---|
It's important to do your analysis with the same user that encountered the problem. There might be issues with permissions that could lead to a different result, depending on the user performing the transition. |
Consider an issue blocked at the Junction status: How many transition buttons does it have? Only if there is exactly one transition available, the follow-up will be triggered. If you have none or more than one transition button, review your workflow conditions on the transitions leading out from the Junction
| Status | ||||
|---|---|---|---|---|
|
If there is only one button, there might be something wrong with that transition. For example, a validator could prevent the transition from getting completed.
...