SLA No Longer Affected

Affected SLASometimes an SLA is no longer considered affected by a request. That happens, for example, when the provider that is responsible for the SLA has rejected the request.

In such cases, the provider is still held accountable for meeting the response target of the SLA, but not for its resolution target. To make it easy to identify such requests after drilling down into the list of requests from an SLA report, the text ‘Not affected’ is now displayed in the Completion column.
Affected SLA no longer affected