Here is a recurrent use case: imagine a process design in which you have a human task that is a bottleneck preventing the execution of several other human tasks.
This stalled task might be at risk of exceeding a deadline, or needs to be cancelled. How can you warn the next actors who are waiting for an input to start their own work?
The current available option is to implement this go-around with a boundary event linked to an automated task that sends an email, then loops back to the parent activity. However, this is a bit awkward and clutters up your process diagram.
Here is a contribution that provides a better way of handling this kind of situation: a connector that will allow you to “get the next tasks’ actors.”
With this, you can retrieve a list of unique user names from the human tasks that are directly connected to your bottleneck task. Warning them of a stalled process will simply require adding an email connector, or extending this one to send emails.
You can find this useful connector in Community Contributions.