I have read the specifications of xpdl2.0.and i have a question which i hope someone can explain to me.in xpdl2.0 specifications,when it describes the semantics of inclusive gateway and parallel gateway(in the section of 7.6.2.3.4.),it says Incoming Sequence Flows that have a source that is a downstream activity (that is, is part of a loop) will be treated differently than those that have an upstream source. They will be considered as part of a different set of Sequence Flows from those Sequence Flows that have a source that is an upstream activity. I want to know how to treat the Incoming Sequence Flows that have a source that is a downstream activity differently.

In an inclusive-or merge, the issue is to decide which subset of the incoming sequence flows will be synchronized. These are determined by a dynamic analysis of the upstream splits (inclusive decisions)that feed this merge. A downstream token returning to this merge is not to be combined with upstream tokens arriving at the merge; hence the distinction mentioned in the spec.

In bpmn2.0 they have tried to clarify this explanation: The Inclusive Gateway is activated if

thank you for answering my question. but i have annother question. I have noticed these sentences in bpmn2.0.The Inclusive Gateway is activated if

The gateway will proceed with the current token, i.e. not wait for the next token that is headed for the non-empty sequence flow.

Hi, I have question about proceeding with current token for an inclusive gateway. For eg, as i shown scenario in the file attached, if activity A is completed, gate G1 is activated irrespective of activity B. Here my question is, how to handle activity B, do we have to leave activity B unattended once ativity A is completed and gate G1 is activated?