Retain Familiar
Retain Familiar stipulates that you want a specific task to be executed by the same resource that executed a previous task in the same process instance. For example, the resource that handles the initial customer contact is the same one that handles the follow-up call.
Consider the following process:
In this example, all three tasks are assigned to the same organization unit. The Take Details task is allocated to a resource from the organization unit. Because the Followup task is in the same Retain Familiar group as the Take Details task, they are allocated to the same resource as well.
If you delete a resource, then Retain Familiar does not work as the resource is no longer available, but the work item remains offered to the participant(s) defined, and you might receive an error message. If you remove a resource from a position or group, Retain Familiar still works as the task is delivered to the resource even though they are no longer a member of the original position or group.
When there are parallel threads, it is possible for the second task to become active before the other has been completed. In such case, Business Studio do not know who the "preferred individual" is and therefore, cannot validate the pattern.
If the pattern is broken for any reason the ’familiar’ resource becomes the most recent resource used. For example, resource A performs the first step in a process, but is not available when the second task is allocated, so the task is allocated to resource B. When the third task is allocated, it is allocated to resource B, who has now become the ’familiar’ resource.
There are several ways to specify this pattern:
- On the right-click menu in the Process Editor
- On the Work Resource tab in the Properties view for the user task
- On the Work Resource tab in the Properties view for the process