How SLA can have dynamic Duration for each catalog task
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2017 09:09 PM
Hi All,
I have duration variable on catalog item. We need to give value in that variable for SLA duration. SLA is going to get attached to catalog task. I have created one field on task to get the value of duration variable on task. I have created one SLA. I want to attach this SLA to task. but the duration of sla should be populated by duration field of task.
Please help me to resolve this issue.
I have used one logic. I have created one before business rule which will alter the value of sla duration every time when we enter the record in sc_task table. But when I have multiple task for multiple RITM, latest value of duration field of SLA is reflecting in all task of different RITM.
I dont want to create separate SLA for each task.
Regards,
Sumit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2017 09:16 PM
Hi,
I don't think you can do this by working around the Duration field on the SLA table, you should NOT do it as it might affect other SLA definitions.
Also, your logic sounds like creating new SLA each time a task is created. We cannot alter the duration field.
can you try doing this, whenever the SLA gets attached to the task, catch it and try updating the duration field.
Thanks,
Vinitha.K
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2017 10:46 PM
Hi Vinitha,
Sorry. I have created field on sc_task not on SLA. I tried to change the duration value of attached SLA but it always takes value from its SLA definition.
Please suggest.
Regards,
Sumiy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-26-2017 01:54 PM
what we did to acomodate sla's on cat tasks was to put the priority field onto catalog tasks.. .and on the catalog task activity...
now we defined catalog task priorities as 1 BD, 2BD etc.. and created sla's based on the cat task priority...
in the workflows it is a tad redundant as you have to basically set the fulfillment time twice... and your priority table choices get pretty long.. but it does work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-26-2017 07:51 PM
Hi Andrews,
thanks for reply.
But I guess this is not relevant to my question. can you please read question once and try to suggest.
Regards,
Sumit