This content has been marked as final.
Show 3 replies
-
1. Re: decision conditions
kukeltje Dec 27, 2006 10:25 AM (in response to tom.baeyens)Tom,
Don't you partly contradict yourself here:
current behaviour is still very awkward. a decision will scan and evaluate all transitions that have a condition first. the first transition for which its condition resolves to true will be taken. if no transition with a condition resolves to true, the default (=the first one) will be taken.
and
explain the less intuitive behaviour... snif. A decision will take the first transition that has no condition or that has a condition which resolves to true.
Assuming the 'order' is the order in the jpdl file. -
2. Re: decision conditions
tom.baeyens Dec 28, 2006 3:31 AM (in response to tom.baeyens)explain the less intuitive behaviour... snif. A decision will take the first transition that has no condition or that has a condition which resolves to true.
the second part is indeed the WANTED behaviour and not the less intuitive behaviour. should not have been there. just ignore the second part: 'A decision will take the first transition that has no condition or that has a condition which resolves to true. ' in that paragraph. -
3. Re: decision conditions
brittm Jan 4, 2007 1:01 PM (in response to tom.baeyens)As stated, It is very un-intuitive and certainly doesn't clearly document what is going on in the decision. I always try to make all of my transition criteria explicit, and can't imagine ever seriously writing a Decision node that would rely on the old behavior. I imagine other developers aren't relying on it either.
As Tom mentioned, the docs were wrong and no one even noticed.
I would vote for the change.
-Britt