In the BPMN specification is an attribute called startQuantity that sets the number of tokens needed to activate an activity. In Camunda 8 I have selected an activity and added an extension property called startQuantity and set its value to 2. When I run this the activity is already activated with one token and does not wait for the second one as I would expect.
Camunda doesn’t implement this part of the specification. Since it’s not graphically represented, this makes the semantics of a BPMN model very hard to understand.
Hi, thanks for your prompt answer.
There are the workflow patterns thread merge
and thread spilit.
While I can understand the decision of not implementing this because it’s not graphically represented it makes the exchange of BPMN workflow specifications between different tools harder. Rgds Andreas