Use SLA retroactive start

You can use retroactive start to retain the timing information for an SLA when a task record changes.

About this task

When a task record changes, typically a new SLA may be attached, with a new set of timing information. This is useful if you are re-assigning an incident to another group and want to attach a new SLA record with new timing information.

However, you may want to retain the task's time information in specific situations. For example, an incident is raised with a priority of 3 - Moderate and the priority changes to 1 - Critical after 3 hours. A priority 1 SLA is attached to the incident at that time. You can use retroactive start to ensure this SLA timing is adjusted retroactively to count from when the incident was first created, rather than from when the incident's priority changed. This reflects the actual time the user contacted you.

Note: When retroactive start is enabled, it may result in task SLAs being breached as soon they attach, which will trigger multiple notifications. To prevent the workflow from being processed for these breached SLAs, set the com.snc.sla.workflow.run_for_breached property to false.

Procedure

  1. Navigate to Service Level Management > SLA > SLA Definitions.
  2. Open the relevant SLA definition record.
  3. In the Start condition section, select the Retroactive start check box.
  4. From the Set start to, select the event from which the SLA starts.

    This option determines the start time used for every task SLA record created from this SLA definition.

    For example, you can select Opened to start the SLA from when the task form was initially opened to create the record, which accurately reflects the time the end user contacts the service desk. Alternatively, you can select Created to start the SLA from when the task form was initially saved.

  5. Click Update.