search

camunda / camunda-modeler-token-simulation-plugin

Token simulation as a plugin for the Camunda Modeler
179 stars 24 forks source link

The plugin does not create optional token for Boundary Message event (non-interrupting) #34

Closed vatsekov closed 3 years ago

vatsekov commented 3 years ago

Describe the Bug

The plugin does not create optional token for Boundary Message event (non-interrupting)

Create a diagram containing Boundary Message event (non-interrupting) image

Expected Behavior

There should be a possibility to create a new token for the message boundary event

Environment

Windows 10 Camunda modeler 4.8.1

nikku commented 3 years ago

Hi @vatsekov.

Obviously you can only trigger a non-interrupting boundary message event the moment the task is active. The user task, as it stands is simply passed through and thus is not active so you as a user can trigger the boundary event. Not sure what you do expect in your scenario.

Check the receive task which has waiting (receive) semantics:

capture YdcOGj_optimized

vatsekov commented 3 years ago

Hi @nikku But why the User task is simply passed through? The Camunda engine waits for its completion before the process continues (unlike the Manual task, which is is handled as a pass-through activity). There could be multiple tokens triggered on the optional path of the boundary event, while the engine waits for the User task completion. Shouldn't the Simulation wait for user click before processing the User task, instead of treating it as a pass through?

Thank you

nikku commented 3 years ago

I believe what you expect is https://github.com/bpmn-io/bpmn-js-token-simulation/issues/9, right?

The token simulation tool is not meant to 1:1 simulate async boundaries / wait states the engine supports. Instead, it is meant to teach people about the token flow. Thus you'll see some differences between the simulator and the engine.

vatsekov commented 3 years ago

yes, I think it would be a logical behavior for the User task. Thank you