The Camunda Modeler seems to have a problem supporting cross pool flows with send tasks / receive tasks. What are the reasons why this is forbidden?
Hi @Edmondo_Porcu,
what exactly is your problem whith the modeler? Which situation are you not able to model? Can you give an example? For me, I can model send and receive tasks.
Regards Michael
Can you model cross pool flows as I mention in the title?
1 Like
Thank you. I was trying to model the flow to the boundary of the pool and it seems to be forbidden, can you please clarify?
Pointing the message flows to the boundary of the pools should work as well:
Can you specify why it is not working for you?
Thank you very much, apparently there is somethng stopping me
as you can see in the screenshot where I ty to drag the flow, the upper pool with 3 lanes become RED
I think I was able to reproduce it. If the upper pool has two lanes, then the flows are not possible and this is true for messages and send tasks.
if you want to model a message flow that is pointing to a pool with multile lanes do the following:
You have to set the tip of the flow to the beginning of the pool (second picture) and not at a specific lane (first picture). This allows you to model message flows even with pools that have multiple lanes
Regards
Michael
1 Like
Thank you very much. Makes sense. Is this situation an hint that I should have two symmetric separate diagrams with a collapsed pool in each of them representing “the other part” or do you think is fine to use this kind of modeling?
The way of modelling always depends on the process. If this behaviour represents the actual process and is clear to understand for you and other stakeholders, then there is no problem modelling it this way.
1 Like