You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the 'Condition' action step module completely stops the automation in its tracks if the result of the condition evaluation is false. This means that nothing you have in the chain after that even gets an input value, preventing you from running any further conditions.
This is what is output to the test runner console:
Ideally, the condition step would allow the user to create a visual branch for the true and false outputs, but failing that, my suggestion would be the following:
IF the condition returns true
THEN continue as normal.
IF the condition returns false,
THEN
Store a reference to that particular condition step in memory
Skip any automation steps following that step until
you reach a condition step that evaluates the result of the stored condition step.
Continue the automation flow from that point.
Given the fact that a condition only has two possible outcomes (true/false), evaluating it more than twice makes no sense anyway, and limiting the state to storing only the last actioned condition module is enough to do things like below.
That way you effectively allow for nested if/then conditions to be created without adding much complexity to the code.
step 1: Action
step 2: Condition
step 3: Action
step 4: Action
step 5: Action
step 6: Condition evaluating {{steps.2.result}}
step 7: Action
step 8: Condition
step 9: Action
step 10: Condition
step 11: Action
step 12: Action
step 13: Condition evaluating {{steps.10.result}}
step 14: Action
step 15: Condition evaluating {{steps.6.result}}
step 16: Action
step 17: Action
step 18: Action
The text was updated successfully, but these errors were encountered:
Currently, the 'Condition' action step module completely stops the automation in its tracks if the result of the condition evaluation is false. This means that nothing you have in the chain after that even gets an input value, preventing you from running any further conditions.
This is what is output to the test runner console:
Ideally, the condition step would allow the user to create a visual branch for the true and false outputs, but failing that, my suggestion would be the following:
Given the fact that a condition only has two possible outcomes (true/false), evaluating it more than twice makes no sense anyway, and limiting the state to storing only the last actioned condition module is enough to do things like below.
That way you effectively allow for nested if/then conditions to be created without adding much complexity to the code.
The text was updated successfully, but these errors were encountered: