- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2024 06:55 AM
During a recent audit finding, we discovered that incidents which are created direct to Resolved don't get an SLA attached. Obviously, the SLA would always be met, both Assigned and Resolution; however, our audit team wants to see that an SLA gets attached.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 09:29 AM
As it turns out, the Stop Condition runs first so since that condition check to see if State == Resolved, the SLA never attaches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 10:52 PM
Hi @Curtis2 ,
Yes off-course and its obvious that we should not put start and stop condition same.
Glad that it resolved your issue.
-------------------------------------------------------------------------
If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.
Regards
Runjay Patel - ServiceNow Solution Architect
LinkedIn: https://www.linkedin.com/in/runjay
YouTube: https://www.youtube.com/@RunjayP
-------------------------------------------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2024 08:24 AM
Unfortunately, after duplicating your SLA definition, it still is not attaching to the Incident.