HighOrbit

The current decision task has a pass/fail outcome on the expression. If a more elaborate decision tree is required then multiple decision tasks have to be chained making for a messy diagram.

If a decision task had multiple expressions then 2 new decision task types could be created (or option button defining behavior):

1. First match where the path of the first expression evaluating to true is taken or the fail default path if none of the expressions evaluate to true. This would be similar to the existing task/form.

2. Multiple match where all the paths are taken (like a split task) for expressions evaluating to true or the fail default if none evaluate to true. This would have to be followed by a Join task or something like that.

That is a good suggestion. We actually have that exact feature scheduled for development in 2Q 2012 :)

It probably won't support multiple "true" paths however, it would just take the path of first condition that matches. It could get very confusing otherwise.