...
- To enable the application to generate SLA-related notifications, ensure that the following configuration parameters are set properly:
- SLA_ENABLE_SUPPRESSION_ON_PENDING_ACTIONS - Set this parameter to Yes only when switching On SLA monitoring for the first time. After the initial enabling of SLA monitoring, set the parameter to No. When the parameter is set to No, the SLA actions are not suppressed. This setting enables the system to generate SLA actions of Assignment and Notification.
- SLA_PROCESS_HIGHEST_ACTIONABLE_THRESHOLD_RULES - Always set this parameter to Yes. This parameter is useful when more than one threshold are breached at the time of applying a target to a ticket. For example, consider a situation where two thresholds with sort orders 1 and 2 are breached at the time of applying a target on a ticket. If this parameter is set to Yes, then only the actions for the Threshold with sort order 2 executes. The system ignores the Threshold with sort order 1.
For more details about these parameters, see Service-Level Management Related Parameters.
- To enable a support group to receive the notifications, enable the SLA Escalation flag for that group. When a ticket is assigned to a group for which the SLA Escalation flag is disabled, SLA notifications are not processed for that group. However, the SLA targets do get applicable for that ticket.
Example:
Customer has an SLA Target where matching condition is: Ticket priority = Critical. The SLA Target is configured to send an email to the Assigned Group if there is no response to the ticket within 10 minutes.
An analyst creates a ticket with Priority = Critical and assigns the ticket to the Service Desk (L1) group. The SLA Escalation flag is not enabled for Service Desk (L1) group.
So, even though the SLA target is applied to the ticket, the system does send any SLA notifications to the group.
...