feat(bpmn): support default flow with condition

[danielkelemen]

No description provided.

[skayliu]

Hi, @danielkelemen, According to the BPMN2.0 of Table 10.123 – ExclusiveGateway Attributes & Model Associations Description/Usage of the default sequence flow.

The Sequence Flow that will receive a token when none of the
conditionExpressions on other outgoing Sequence Flows evaluate
to true. The default Sequence Flow should not have a
conditionExpression. Any such Expression SHALL be ignored.

I'm wondering why this PR is not following the BPMN2.0 standard?

[danielkelemen]

Hi @skayliu,

This change is still under a little dispute and I personally suspect that we will not merge it at the end. I just opened the PR to run the tests and see how much work it would be.

The reason of the dispute is that:

Any such Expression SHALL be ignored.

It says it should be "ignored" and the platform right now doesn't ignore it but fails during such deployment.

The default Sequence Flow should not have a conditionExpression.

On the other hand, this sentence says "should not have a conditionExpression" so users shouldn't deploy such processes either.

I feel like the specification is a bit ambiguous.
What do you think?

-Daniel

[skayliu]

I feel like the specification is a bit ambiguous.
What do you think?

May be you can take a look at this Exclusive gateway not allowed default flow to have a condition

[danielkelemen]

May be you can take a look at this Exclusive gateway not allowed default flow to have a condition

That was actually the trigger for this, too. C7 right now won't accept a deployment with conditional default flow.