I have a BPMN diagram where I need to exchange messages from one pool to another.
Basically my send task "Enviar convites" sends a message to another lane in my pool and to a lane in another pool.
This is the flow of the other pool and this other pool sends a message that is received on the first pool in the task "É informado da submissão da proposta de tema de tese".
My question is do I need to connect the task "Enviar convites" to "É informado da submissão da proposta de tema de tese"?
So, just to make things straight:
If so, then you need to link directly "Enviar convites" to "É informado da submissão da proposta de tema de tese".
In general, the control within one pool can go to different lanes. It doesn't break the flow. The activities within the same lane do not have to be continuously connected as long as there is connection across all lanes within the pool. On the other hand, the connection through messages leading to other pools doesn't ensure the continuity within the pool so there has to be a link within the pool leading from sending to receiving the message. The problem is there is no link (other than the messages to the external pool) linking the activities of sending and receiving the message, so this flow is broken.
In practice, your process doesn't stop while you're waiting for the response. This is what the (currently missing) arrow represents. Think also of other options: what if the response never comes? Do you wait indefinitely or is there a "timeout" (e.g. proposal deadline)? This shows best that there is something going on in the process, even if it goes into idle state for some time. Show it with the flow arrow.