Convert an SLA to an SLA Definition You must replicate the default SLA record as a new SLA definition. About this task To convert old SLAs to SLA Definitions: Procedure Transfer the Name and Table fields. If desired, check the Retroactively Start checkbox. If checked, this will cause the SLA to calculate from the moment the record is created (or from the date and time on the selected task), rather than the moment the SLA is attached. This is especially helpful for Task SLAs that will attach to active incidents that have old SLAs currently running. Transfer the Conditions field to the Start Conditions field. Make sure to add Active is True as well, so that the new Task SLAs don't attach to closed incidents when they are updated. Define a new set of Pause Conditions and Close Conditions. Set the Duration Type and Duration fields. The old SLAs did not support relative duration, so to define the Task SLA to behave similarly to the old SLA, select User Defined Duration as the Duration Type and put the total length of time of all of the escalations here. For instance, an old SLA that has escalations of 4 hours to Moderate, 2 hours to High, and 2 hours to Overdue, the new Task SLA should have Duration set to Days 0 Hours 08:00:00. Calendars have been replaced by Schedules, so if schedules haven't been defined yet, they will need to be. Instead of escalations, attach an SLA Workflow. There is a default SLA workflow, however, you must create a new workflow to replicate the escalation levels on the old SLA. Escalation Levels are defined hour-by-hour, whereas the SLA Workflow uses a percentage timer. So for the above example of 4 hours to Moderate, 2 hours to High, and 2 hours to overdue, the workflow will need a 50% timer and then two 25% timers. The new task SLA records do not use the Escalation or Made SLA fields on the task record. Example The following example is an old SLA for Priority 1 incidents to be resolved on a Monday-Friday (8-5) Calendar, with escalations to Moderate at 4 hours, to High at 2 hours, and to Overdue at 2 hours: Figure 1. Old SLA Example This is the new Task SLA created from the same information: Figure 2. New SLA Example This is the workflow which powers the new Task SLA. Note: This example workflow responds to each escalation by firing off an event. A business rule can be configured to respond to escalation events, or the workflow can be adjusted to match the organization's process. Figure 3. New SLA Workflow Task SLA tableWhen an SLA Definition is triggered against a particular task, the Task SLA record is generated and contains all the tracking data for the specific SLA on that record. In many cases there will be multiple Task SLA records against a single task since many definitions apply. The Task SLA [task_sla] table stores Task SLA records for the SLAs attached to particular tasks.