Automation Features Use Cases - An Overview
Automation Features Use Cases - An Overview
This document outlines use cases for automation features in ServiceDesk Plus MSP Cloud. It showcases how the features can be leveraged to address operational needs and challenges, streamline workflows, and enhance productivity.
Each use case includes:
Scenario: A business scenario where automation can be leveraged.
Prerequisite: Setup or configurations to be in place before applying the action.
Action: A gist of essential configurations.
Configuration: The essential configurations that address the scenario.
Terminologies
Customer-specific | The automation rule must be configured separately for each customer. Before setting up the rule, select the appropriate customer from the drop-down in the application header. Note: For all use cases in this document, Zylker and SolversHQ are MSP customers. |
Site-specific | The automation rule must be configured separately for each customer's site. Before configuring the rule, use the Filter by Site drop-down to filter the appropriate customer's site. |
Module-specific | The automation rule must be configured separately for each module. Before setting up the rule, select the relevant module from the module filter. |
Refer to this document for an overview of automation features in ServiceDesk Plus MSP Cloud.
Related Articles
Workflows Use Cases
Workflows Pointers Workflows can be configured for All Customers as well as for a specific customer, but not site-specific. This setting is module-specific. Separate workflows for incident requests and service requests can be configured. If an asset ...
Use Cases
Scenario: Convert Incident to Service Request Currently, only incident requests can be created via email using the default template. However, Zylker wants to create service requests based on specific keywords found in the email, aligning with their ...
Life Cycles Use Cases
Life Cycles Pointers Life Cycles can be applied to All Customers or a specific customer. Life Cycles are not site-specific. However, you can apply life cycles for specific sites under Conditions. If a template is associated with a life cycle, the ...
Business Rules Use Cases
Business Rules Pointers Incident and Service Request business rules are customer-specific and site-specific. Change business rules are neither customer-specific nor site-specific. However, you can apply change business rules for specific customers ...
Triggers Use Cases
Triggers Pointers Triggers can be configured for All Customers or a specific customer. Once configured, the Customer cannot be changed. Triggers are module-specific and not site-specific. However, you can configure for specific sites of customers ...