Our next wish belongs a simple functionality, but helps again to reduce programming effort and a source of error. Working on business cases there is often the situation that a task is addressed to an organisational unit and somebody takes the task over. The flow goes on, but due to some missing things it may come back to that special task. And to avoid that somebody else needs the setup-time again the former performer should be addressed again to rework the task. To summarize: first time address the task to a group afterwards to the first performer.
We have solved this with an attribute named remember receiver which is flagged for that special task as shown in the following graphic.
Do you have another idea how this behavior could be solved within the BPMN?