How to Trigger the SLA from workflow only and does not trigger like normal SLA Definition works
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
16 hours ago
I create one SLA definition and want to trigger it through workflow only . But it trigger it from SLA definition , want to make it disable .
and to trigger SLA from workflow, I follow these script but it didn't work

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
15 hours ago
Not that I'm aware, as it's not intended functionality.
You could potentially call TaskSLA directly, which is the script include which TaskSLAController invokes. But I've never tested the functionality to know the impact it might have on wider SLA calculations.
// new TaskSLA(contractSLAgr, taskGR)
// -- add a new task_sla GlideRecord, related to the taskGR GlideRecord, based upon the contractSLAgr GlideRecord
// (assumes the caller has already made the decision to add it, and is actively preventing
// multiple overlapping requests to add the same contract_sla)
//
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
16 hours ago
Why to do this?
Why not stick to OOTB process and let instance handle the trigger of SLA based on Start condition?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
16 hours ago
Because the start conditions which I want to configure can't be possible in OOTB Start condition.
That 's why I created those conditions in workflow, and now i want to trigger it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
15 hours ago
on what condition the SLA should start?
share those
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
15 hours ago
1. When Person added in particular Azure AD Group
2. One field in catalog , delivery date is less than 5 days from today.
3. Once 4 approval get approved.
4. Weekend should not be counted in that 5 days.
5. When user is adding in particular AD Group, checks Schedule Delivery date should be 7 days more than requested delivery date.