- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-11-2017 12:28 AM
Hi all,
we are having SLA running on sc_req_item.
It should run during the whole lifecycle of the RITM, however it should be paused during execution of certain catalog tasks.
Any ideas how this can be achieved?
I was thinking about business rule on sc_task listening for insert of "certain" records and pause SLA in the script.
The update of sc_task record into one of "Completed" state will trigger the SLA again....
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-12-2017 08:05 AM
Hi Peter,
No, as Task SLA is running on RITM then TaskSLAController runs when RITM is updated, not when related Catalog Task is updated. This is why you need to actually update RITM ideally to move Task SLA to another stage (paused / in progress). If you do not reflect the update of Catalog Task on RITM somehow then the Pause Condition of SLA Definition is not met (as nothing changed on RITM) and it is still In Progress. If you update it to Paused by your script in business rule, you would need to do that properly by existing functions (as you need to set also Pause Time etc. to ensure the pause duration is correctly calculated once it is resumed), but there is still the problem that whoever updates RITM, the Pause Condition is evaluated again and it is still not met so Task SLA is resumed.
See below the relationships of SLA scripts for more details (Task update is here the RITM as Task SLA runs on RITM):
Best regards,
Dominik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-12-2017 08:05 AM
Hi Peter,
No, as Task SLA is running on RITM then TaskSLAController runs when RITM is updated, not when related Catalog Task is updated. This is why you need to actually update RITM ideally to move Task SLA to another stage (paused / in progress). If you do not reflect the update of Catalog Task on RITM somehow then the Pause Condition of SLA Definition is not met (as nothing changed on RITM) and it is still In Progress. If you update it to Paused by your script in business rule, you would need to do that properly by existing functions (as you need to set also Pause Time etc. to ensure the pause duration is correctly calculated once it is resumed), but there is still the problem that whoever updates RITM, the Pause Condition is evaluated again and it is still not met so Task SLA is resumed.
See below the relationships of SLA scripts for more details (Task update is here the RITM as Task SLA runs on RITM):
Best regards,
Dominik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-12-2017 08:11 AM
Dominik:
Thanks for sharing this flow. This should really help those trying to better understand the SLA calculation process.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-12-2017 08:14 AM
Maybe I could write a blog here with this picture I created for myself to understand all the dependencies between particular scripts. Hopefully that helps 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2017 11:14 PM
You should definitely do that and write it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-12-2017 08:06 AM
Or at least no, if there is not sync of comments from Catalog Task to Requested Item 🙂