To filter among performers depending on previous performers in a role assigned to a task or a lane use Performers Filters.

There are three different filters:

  • All - default setting that gives all performers in the assigned role permissions to perform the task(s)
  • * Previous - the role is filtered according to the previous performer.
  • * All previous - the role is filtered on all previous performers 

*These filters may impact other role assignments. For example, the Previous filter will overrule any other roll or lane assignments, like in the example below. 

How to add a Performers Filter

1. Double-click on the lane or task that you want to add a filter to. The settings panel opens.

2. Open the Roles settings, and the Performers Filter selections are shown. Mark the preferred value and the filter will be automatically saved.

When to use Performers Filters

Performers filters are used to assign who will be the performer in a certain role when there is a group of potential performers. For instance, in the process example above where customers can create support tickets, you want to make sure that the customer who created the ticket is the one who will get the task to Complement ticket information, if needed. In this case you should set the performers filter to Previous, which mean that the performer of the Complement ticket information task will be the same performer who previously acted in the specific role.

If the performers filter All would be set in the example above, all clients would have got the task to Complement ticket information. If you have more than one client, this is probably not  something you want to happen. 

Note: If the performers filter Previous performer is applied to a task and you share it with a user that was not originally configured as one of the users who can perform the task, there is a possibility that the process will get stuck. The reason for this is that the Previous filter overrules any other roles assigned to the task. So even if a user from outside the pool of authorized users completes the task, they will then be considered the previous performer and will be assigned the task in the future instead of it being assigned to the previous performer within the pool of authorized users.