Depending on your needs and business processes, you can assign tasks to agents in two ways:

  • manually by specifying the values of the Assignment Group and Assigned User fields.
  • using the task auto assignment engine. The engine allows you to automate task assignments by various criteria, defined by conditions and assignment types, and implement business logic before a task is assigned. Tasks auto assignment allows you to balance employee workload and create different rules for different kinds of tasks.

Manual assignment


The "out-of-the-box" solution has preconfigured restrictions for assigning users or groups depending on the values of relevant fields. The reference restrictions for Assignment Group and Assigned User fields in the Task and ITSM Task tables are defined within the dynamic filters. These filters are stored in the Filter Option Dynamic (sys_filter_option_dynamic) table. From the ITSM Task table, the restrictions are inherited by the incident, user query, problems, request, change request tables.

Dynamic filter TableDescription

List of users based on assigned group

TaskIf you specify an assignment group, you can assign only an employee who belongs to this group in the Assigned User field.

If you do not specify an assignment group, you can select any employee record in the Assigned User field.

List of groups based on assigned user.

Task

If you specify an assigned user, you can only select the group the user belongs to in the Assignment Group field. 

If you do not specify an assigned user, you can select any group in the Assignment Group field.

List of ITSM_agent on assigned groupITSM Task

If you specify an assignment group, you can select only an employee that is in this group and has the admin or ITSM_agent role in the Assigned User field..

If you do not specify an assignment group, you can select any employee that is in this group and has the admin or ITSM_agent role in the Assigned User field.

Create an assignment rule


Role required: admin.

To create a new assignment rule, complete the steps below:

  1. Navigate to Auto Assignment → New Rule.
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to apply the changes.

Keep in mind that a task auto assignment only triggers new record creation. The auto assignment rules cannot be configured to handle record update events. For example, the auto assignment does not work when the state or any other field value changes.

Auto Assignment Rule form fields

FieldMandatoryDescription
NameYSpecify the assignment rule name.
DescriptionNType a description of the assignment rule.
TableY

Specify the table extending from the Task table and containing the objects to assign (like incidents, requests, and so on).

Assignment Type 

Y

Specify the assignment type. Available options:

  • Custom – allows you to define assignment logic more flexible, including scripts. For example, a custom rule with specific conditions can assign a particular user that is competent for such a task.
  • Load Balancer – allows you to assign tasks to people that are least loaded so far within the group specified. For example, John Doe is already processing three tasks. He cannot take another one, so the current task is automatically assigned to Barbara Wilson who is processing two tasks. Thus, no employees within this team are overloaded with tasks. 
  • Round Robin – allows you to assign tasks to employees within the specified group interchangeably: one after another in a queue. For example, if John Doe got a task this time, the next task is assigned to Barbara Wilson.

If you use the Load Balancer assignment type, you need to configure a load balance element. This element defines which tasks to consider as completed ones. If not defined, the balancer takes into account all task records that are assigned to users.

Consider a case when a load balance element is not created:

  • In the department, the employees can only work on 2 tasks at a time (maximum).
  • John Doe has worked for 10 years and completed 1000 tasks.
  • Barbara Wilson has worked for 1 year and completed 100 tasks.

Since the load balancer cannot define which tasks are completed and which ones are not, all new tasks are assigned to Barbara Wilson because loader considers John more loaded in comparison to Barbara and counts all tasks assigned to him for 10 years.

But if a load balance element definesthe records in the Closed state as "completed", the load balancer ignores these tasks.



Assigning to inactive userN

Сhoose the system response options if a user who the task should be assigned to is inactive. The available choice options:

  • Restrict assigning
  • Display warning
  • Ignore
WarningY

Specify a warning message. The default value is "Task is assigned to inactive user". This field only appears if the Display warning option is selected in the Assigning to inactive user field.

ConditionY

Define the conditions to meet before the assignment rule is triggered.

Use the condition builder to configure a filter that suits your needs. You can create complex AND and OR filters with more than one condition in one filter.

If you need to configure a general rule (for example, to assign all tasks to a specified employee), use a workaround by specifying a common condition like:

ID is not empty



Assigned GroupY

Specify a group that is responsible for this kind of tasks.

If several groups can work on a task, add a relevant condition, for example:
[Assigned Group] is [X]
Then the auto assignment rule selects users from the X group (defined in this Assigned Group field), if this X group is selected in a task record.


When a responsible group is assigned, the Assigned User field becomes non-mandatory. 



Assigned UserY

Specify a person that is responsible for this kind of tasks.

This field only appears when the Custom option in the Assignment Type field is selected. 


When a responsible user is assigned, the Assignment Group field becomes non-mandatory. 


ActiveNSelect this checkbox to activate this rule.
Use ScriptN

Select this checkbox to specify the script that implements the advanced assignment logic. You can script actions for assigning users and/or groups.

This checkbox only appears when the Custom option in the Assignment Type field is selected. 


WatcherN

Reference to a business rule containing the assignment logic (conditions, groups, and so on). This rule is automatically created when the form is saved. The relevant field is also populated with the business rule ID automatically. 

You can manage this business rule later in an appropriate section (System Definition → Business Rules).

Group ScriptN

Specify the script that implements an advanced logic for a group assignment.

This field appears when the Use Script checkbox is selected.


User ScriptN

Specify a script that implements an advanced logic for a user assignment.

This field appears when the Use Script checkbox is selected.



The server-side business logic may not work for system tables if the creation or updating of records is initiated by the backend. For example, an Import Set is created as part of loading an Import Source, or an Email is created as a result of a notification rule, and so on.

A list of table examples for which server-side business logic may not work:

  • Main Log (sys_log)
  • Script Log (sys_log_script)
  • Exception Log (sys_log_exception)
  • Record Deletion Log (sys_record_deletion_log)
  • Import Set (sys_import_set)
  • Activity Feed Item (sys_activity_feed_item)
  • Email (sys_email)


Load balancer elements

If you create a Load Balancer assignment type, define which tasks are not taken into account while evaluating the team's load. You should exclude the completed tasks. To do this, complete the steps below:

  1. Open the auto assignment rule of the Load Balance type.
  2. In the Related Lists area, select the Load Balance Element tab.
  3. Click New and fill in the fields.
  4. Click Save or Save and Exit to apply the changes.

An alternative way to create a load balance element is the following:

  1. Navigate to Auto Assignment → Load Balance Elements.
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to apply the changes.

Load Balancer Element form fields

FieldMandatoryDescription
Autoassignment RuleYReference to the auto assignment rule for which this configuration is done. If you create an element out of the related list, this field is populated automatically.
Completed StatesN

Specify the states that can be defined as "completed". All other states related to this rule will be considered "incomplete".

You can specify more than one state in this field.


You can find an example with filled fields in the screenshot below.

Round Robin elements

The Round Robin Element table stores information about the next group member to be assigned to a task. The count starts with "0" (group member 1). When the Current User Count field value is equal to "1", it means that the next task will go to group member 2.

Unlike the load balance element, the system automatically creates a relevant element once the auto assignment rule is executed. The round robin element does not have to be created manually.

To create a round robin element, complete the steps below:

  1. Open the auto assignment rule of the Load Balance type.
  2. In the Related Lists area, select the Round Robin Element tab.
  3. Click New and fill in the fields.
  4. Click Save or Save and Exit to apply the changes.

An alternative way to create a round robin element is the following:

  1. Navigate to Auto Assignment → Round Robin Elements.
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to apply the changes.

Round Robin Element form fields

FieldMandatoryDescription
Autoassignment RuleYReference to the auto assignment rule for which this configuration is done. If you create an element out of the related list, this field is populated automatically.
Current User CountYSpecify a value that defines a user to be assigned to the next task. Note that "0" here means the first employee in the queue.



Related articles