Incident SLA trigger on affected CI and Impacted Services/CIs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2024 10:55 AM
Hi All,
before Utah release I found a ServiceNow announcement for extending the SLA trigger functionality on incident (in fact task) that Service Offerings of the related lists "Affected CI" and "Impacted Services/CIs" would be considered in addition to the "Configuration Item" or "Service Offering" field in regards of triggering the Service Commitment SLAs of those Service Offerings.
My customer was waiting for that feature, but in Utah I can not find any hints for the feature. The SLA code (BR) seems to still just work on either the "Configuration Item" or "Service Offering" field and the doc article seems to be removed.
Was the feature postponed or canceled at all?
Will the SLA trigger be restricted to only one of those fields in future?
BR,
Oliver