Product Update

Affected SLAs No Longer Affected

Carlyn Manly
2020-09-26
1 Min Read

When a request is initially linked to a service instance, but is later linked to another service instance that is not hierarchically below the previous one, the affected SLA for the first service instance is no longer considered โ€˜affectedโ€™.ย  This is not uncommon.ย  For example, when someone is no longer able to access the SAP production environment, a request may be registered that is linked to this service instance.ย  A specialist may later determine, however, that the issue is caused by a Wi-Fi outage in one of the office buildings.ย  At this point, the specialist will update the service instance of the request to the buildingโ€™s Wi-Fi network.ย  This causes the affected SLA that is linked to the request for the SAP production environment to be marked as โ€˜SLA Not Affectedโ€™.

A support organization may want to see if it might be able to improve the initial service instance selection for its requests.ย  To facilitate this, it would be helpful to have a report that includes all affected SLAs that were later found to be unrelated to the request.ย  This report is now available in the โ€˜Reportsโ€™ section of the Analytics console.ย  It is called โ€˜Affected SLAs No Longer Affectedโ€™.

Affected SLAs No Longer Affected report