what is retroactive in service now ?

Go to solution
elizabeth keen
Giga Contributor

‎03-31-2019 09:08 PM

what is retroactive in sla in  servicenow .

0 Helpfuls
  • 5,363 Views
1 ACCEPTED SOLUTION

Go to solution
shubham jagtap
Tera Guru

‎03-31-2019 09:20 PM

Hi,

can use retroactive start to retain timing information for an SLA when a task record changes. Retroactive pause prevents immediate breaches and notifications when retroactive start is enabled for SLA definitions.

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 time information for the task 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.

You can use the retroactive pause property to apply pause times to the new SLA.

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. To enable the retroactive pause property, select the Retroactive pause check box.
    Enabling this property ensures that the new task SLA record gets any pause time that would have been accumulated during the period between the retroactive start time and now. This pause time increases the breach time with the appropriate amount.
  6. Click Update.

What to do next

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 thecom.snc.sla.workflow.run_for_breached property to false.  you can refer below link: https://www.youtube.com/watch?v=7mfQ69aEFHE https://www.youtube.com/watch?v=DKv4LAZSH-0 after going throw this mark it as correct/helpful . Thank you

View solution in original post

4 REPLIES 4

Go to solution
Angshuman3
Mega Guru

‎03-31-2019 09:14 PM

Hi Elizabeth,

The below link should help you :-

https://docs.servicenow.com/bundle/madrid-it-service-management/page/product/service-level-managemen...

Hope this helps.

Mark the answer as correct/helpful if you are satisfied.

Thanks,
Angshuman

 

Go to solution
Moin4
Kilo Contributor
In response to Angshuman3

‎08-17-2021 12:27 PM

Thanks, got the point. 

0 Helpfuls

Go to solution
shubham jagtap
Tera Guru

‎03-31-2019 09:20 PM

Hi,

can use retroactive start to retain timing information for an SLA when a task record changes. Retroactive pause prevents immediate breaches and notifications when retroactive start is enabled for SLA definitions.

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 time information for the task 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.

You can use the retroactive pause property to apply pause times to the new SLA.

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. To enable the retroactive pause property, select the Retroactive pause check box.
    Enabling this property ensures that the new task SLA record gets any pause time that would have been accumulated during the period between the retroactive start time and now. This pause time increases the breach time with the appropriate amount.
  6. Click Update.

What to do next

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 thecom.snc.sla.workflow.run_for_breached property to false.  you can refer below link: https://www.youtube.com/watch?v=7mfQ69aEFHE https://www.youtube.com/watch?v=DKv4LAZSH-0 after going throw this mark it as correct/helpful . Thank you