SLA Repair dependency on sys_audit records of task_sla

[madhuv]

Hi Team,

We have been asked to disable (and also delete existing) sys_audit records for task_sla table. Wanted to know if SLA repair is anywhere dependent on them (i.e audit records of task_sla).

Regards

Madhu

[Community Alums]

Hi @madhuv ,

Yes, it will have an impact i believe!!

SLA Administrators can repair SLA records to ensure SLA timing and duration information is accurate.

Repair of SLAs is useful to determine accurate timing information if your system has SLA records that contain incorrect values. For example, you may need to repair SLA records as a result of:

• Changing the SLA definition or SLA schedule for any task SLA that is still active.
• Changing the conditions of the SLA definition for any task SLA that is still active.
• Some other system anomaly.

The repair function removes the SLA record, then recreates and recalculates it from the start, including recreating the workflow. The repair uses the history from the Task and if appropriate will also create new Task SLAs that did not previously exist. For example, a new Task SLA may be needed if a new SLA Definition has been added since an associated Incident was created or updated.

SLA repair does not use the history of dot-walk fields but considers only the final state of the dot-walk fields. For example, if a pause condition is set to an incident dot-walk field as incident.caller_id.location and in real time the location is set to London, and later changed to San Diego. Then, when the SLA repair runs, only the final location is considered. So, if SLA is in pause state when the incident.caller_id.location is San Diego, repair pauses immediately as it does not consider the previous London location.

[madhuv]

Hi Sandeep,

Thanks for your reply.

From the text you have pasted , I see one line "The repair uses the history from the Task " , guess it would the history of task which is associated and not the history of task_sla.