ServiceDesk Plus comes with built-in capabilities that allow users, who have minimal technical expertise, to set up rule-based automations. Administrators can establish a service desk that handles requests on auto-pilot via automations.
The various automation services in ServiceDesk Plus are listed as follows:
You can employ multiple automation rules on a request at different stages of its life time. Each automation rule has a unique objective and an application pattern. Refer to the table below to understand how the automation rules operate uniquely:
|
Automation Rules |
Objective and Application |
Modules from where the data is validated |
|
Business Rules |
|
Requests |
|
Service Level Agreements |
|
Requests and Changes |
|
Request Life Cycle |
|
Requests |
|
Custom Triggers |
|
Requests, Problems, Changes, Projects (and their associated tasks) |
|
Request Timer Actions |
|
Requests |
|
Notification Rules |
|
Requests, Problems, Change, Projects, Releases, Solutions, Assets, Purchase, Contract, Reports (and their associated approvals/tasks) |
|
Closure Rules |
|
Requests, Problems, Change, Releases (and their associated tasks) |
|
Technician Auto Assign |
|
Requests |
|
Workflows |
|
Changes and Releases |
|
Custom Schedules |
|
Validates data from any module via Reports |

ServiceDesk Plus automations applied during a request lifetime
Sometimes, multiple automation rules maybe applicable to a request after it is created or edited. In such cases, a clear order of execution is defined in ServiceDesk Plus as shown below.
Execution order of automation rules in incident and service requests:

Execution order of automation rules in change requests:
