Once the activity or event is selected, the performers Assignment window will be displayed. In this window you can assign an allocation according to three types of conditions: Allocation Rules, assignment Method and Preconditions.
Determines the specific user or users that should carry out the Activity. To define allocation rules click on Add Condition icon ().
Allocation rules are built by specifying operands and operators as shown in the next image:
User properties are a set of user characteristics such as name, e-mail, boss, etc. Some user properties are defined by default, but you can create additional user properties according to your business needs.
The user properties defined by default are:
•User id: Identification number in data base of a specific user.
•Area: Department of an organization
•Location: Geographic location. This section also defines offices or branches, if applicable. In Bizagi, a user can only belong to one location.
•Role: Conduct or role carried out by a person in the organization. In Bizagi, a user can have one or more roles.
•Skills: Ability or aptitude for an action. A person’s special skills allow him/her to carry out an Activity. In Bizagi, a user can have one or more skills.
•Positions: Organizational structure. It indicates the positions and their chain of command.
•Stakeholder: A knowledge worker who will be logging in to the Work portal to carry out daily work. In Bizagi, a user can be in one or more Stakeholders.
Comparator allows comparing a user property with a specified value. You can select between Equals to or Not Equals to a condition.
Specifies the type of the source where the condition value will be taken from. A type, of the source's value, can be one of the following.
•An Expression: Allows defining a business rule to establish the value of a condition. You can define an expression or select an existing one from the set of default expressions defined by Bizagi. This source is only available for some use properties such as User id and identification number.
Default expressions included in the system are:
oCurrent Assignee: Returns the user currently working on the Process.
oCurrent Assignee Boss: Returns the boss of the user currently working on the Process. This expression has variations as CurrentAssigneeBoss_Level2, CurrentAssigneeBoss_Level3 etc to access different hierarchical levels.
oCase Creator: Returns the user who created the case.
•A Data Binding: Allows selecting an attribute in the Process Data Model.
•An Entity Value: Allows selecting the value from a list of values displayed for the Parameter Entity.
What is the Current Assignee?
The concept of current assignees is the last person who executed a BPMN element in the case of a process. Therefore, the current assignee is contextualized by the element where you are consulting the assignees. To have a better understanding of this concept, let us review some examples.
Example 1: sequence of tasks
Assume that Task 2 is allocated with the Current Assignee property. And Johana executed the previous task (Task 1). Then the Current Assignee is Johana, and Task 2 will be assigned to her.
Example 2: tasks in parallel
Assume that Task 4 is allocated with the Current Assignee property. When the previous tasks are executed in parallel, then the current assignee will be the last person who executed any of the tasks. In the image below, shows that if Johana finishes last, the current assignee will be her. On the other hand, if Carlos finishes last, then Carlos will be the current assignee.
Is the value of the allocation condition. This value is set according to the value type selected.
You can define one or more conditions by using the And/Or operator.
Provides a set of functions to select how Bizagi allocates a Task to the available users.
The four options are:
•By Load: The Task is allocated to the user with the lightest workload or with the least “jobs pending” on the project. Only user Tasks are considered, while allocated events and automated task are ignored. However, the system first checks whether anyone in the user's group has already worked on the case. If so, he/she is assigned the Task, regardless of the user's workload compared to the rest of the group.
•Everyone: Allocations are given to all users with the characteristics indicated. The first person to take ownership of the case (i.e., click on it in the pending inbox and then clicking on "take ownership" option) will be assigned to perform the task; consequently, it will no longer be displayed for the others to see. If the person who was assigned to perform the task releases it, it will become available again to all users that match the assignment rules. For further detail regarding this assignment method, check the Details on assignment to everyone article.
•Sequential: Each Task is assigned evenhandedly and sequentially among the users who satisfy the allocation criteria, regardless of their workload. However, if a Task is instantiated several times, this Task will be assigned to the same user that was allocated the first instance, and the assignment method will not apply in this case.
•First available user: With this method, tasks are allocated to the user that will first be available according to the time zone associated. There may more than one user available. In such cases, Bizagi will determine the task performer by evaluating the workload of each available user.
When the assignment method returns more than one candidate, Bizagi evaluates if any of them have been previously allocated to the case. If there is a user who complies with the allocation rule and has previously worked on the case, that user will be allocated.
Assignment Method in Events
The Event has no assignment Method. The method will be, by default, to Everyone.
Allows carrying out the allocation based on business rules. These results return a result of true or false, indicating whether or not the condition that applies to the defined profile was met. In other words, a precondition allows a user to establish rules in order to decide which allocation rule to follow.
Preconditions are activated by clicking the add button of the Preconditions option. Each tab represents a precondition and contains its own allocation rule and assignment method, this way an Activity allocation can be done by a combination of assignment rules and assignment methods according to the business conditions.
Preconditions are defined by expressions which can be configured by clicking on the Select Expression option (). You can define Boolean or scripting expressions according to your needs.