hey there,
i want to define a conditional intermediate catch event for waiting for complete “Task11”. like this:
how should i fill these options:
hey there,
i want to define a conditional intermediate catch event for waiting for complete “Task11”. like this:
how should i fill these options:
Hi @masoud_h
task11Executed
and set it to true
.#{task11Executed}
I don’t trust in conditional events. Hence I would place a message throwing event after the user task and explicitly send a message to the other process branch.
That violates the BPMN spec (short version is Message must cross a process boundary).
I could see using a placeholder process though (when the condition happens, message start the “Task 11” process, and when Task 11 is complete, message back.). But I would want a lot more details on how this is supposed to work overall. The way OP initially drew it, it is possible to get the token to Task 11 before it gets to Y, which I think they want it to simply continue at that point, rather than waiting for the Task 11 completion… which may never arrive.
You are right. No message event is necessary here. Since we stay “on the same level” in the process, an X-join and a transition would do. Or, to avoid the lines crossing half the model, a link throwing and link catch.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.