topic Re: Best Practice for SLA based task flow in Alfresco Archive

Best Practice for SLA based task flow

sangv — Thu, 10 May 2012 13:53:33 GMT

I have a relatively simple use case and I am looking for some guidance on the best way to solve it. There are two actors, employees and managers. Managers track how the employees are performing the tasks and perform actions based on how much at risk employees are on missing the SLA for the task.So f

Re: Best Practice for SLA based task flow

c_arunrathnakum — Fri, 02 Aug 2013 09:09:05 GMT

Need solution please. Coming through same requirement

Re: Best Practice for SLA based task flow

frederikherema1 — Mon, 05 Aug 2013 08:04:41 GMT

The best way to solve this is doing this in a single process, as it's all related to a single use case. The best way to do this, IMHO, is to have multiple boundary-timer-events on the UserTask for the employee. These boundary-events should have cancelActivity="false" in the XML, which keeps the "employee" task alive when the timer fires.

When one of the timers fires (eg. first one at 3 days -> timeDuration="P3D"), you have a user-task for the manager called "Call employee X". The outcome of this tasks leads to an end-event. When the "Call employee X" task is completed, only the "forked" part of the process ends (caused by the timer) and the employee-usertask remains active. The other timers can have other timeDurations.

Finally, if there is a hard-deadline, you can have the timer cancel the activity and go to a manager-task "deadline expired". This way, after the 10 days, the employee won't have see the task in his task-list anymore.