Drop on flow should remove redundant incoming and outgoing sequence flows.

[nikku]

I'm considering a scenario where the Task to be dropped on a sequence flow already has incoming and outgoing sequenceflows.

Given our current way of dropping all incoming and outgoing flows are being kept. During execution this effectively duplicates the token (a Task with two outgoing sequenceflows is effectively an AND split. This is something one most likely does not want to achieve (cf. screencast below).

In the presence of default flows or sequence flows with conditions the situation is slightly different, as these are not redundant / semantically equal.

Tasks

• Remove redundant sequence flows when dropping on flow

Two sequence flows are redundant, if they connect the same source / target and (have the same condition or are both default flows).