topic Re: History by User Task Claim time in Alfresco Archive

History by User Task Claim time

ruedesilva — Thu, 05 May 2011 21:06:19 GMT

Hi,The project that we are working on requires that the system track how long a user spends on a task. This has to be starting from when a user claimed the task (not when the task started). Currently I do not see this in the DB or any mechanism to handle this. The reason for this is that the company

Re: History by User Task Claim time

frederikherema1 — Mon, 09 May 2011 09:10:19 GMT

Hi,

You could use an task-listener for this. You define the handler to the tasks that need to be monitored, triggering on the event "assignement". In the assignement-handler code, you can (for example) add a local variable to the task (delegateTask.setVariableLocal("claimTime", Calendar.getInstance().getTime()). If you set the histroy-level high enough, task-variables are stored in the history and can be queried for. With some code (or custom query), I guess you can calculate the duration.

see http://activiti.org/userguide/index.html#taskListeners

Re: History by User Task Claim time

jbarrez — Mon, 09 May 2011 09:20:04 GMT

No, that information is not availble in the database at this point, you'll need to add your own variable to track this time.

Re: History by User Task Claim time

ruedesilva — Mon, 09 May 2011 15:15:13 GMT

Thanks for the information. I thought the Assignment event happens prior to the 'create' event so that the setting the variable in an task listner would not have the correct time? i.e Does the assignment event happen again when a user claims a task or a manager delegates the task to a user? Or is it just a one time reference when the task gets created?

thanks,
Rue

Re: History by User Task Claim time

frederikherema1 — Tue, 10 May 2011 07:08:23 GMT

If the activiti:assignee (or BPMN 2.0 humanperformer counterpart) is used, the assignement-event is fired RIGHT before the create event. In this case, it's the same as the create time, so you can just use that time, no? If assignee is null at that time, you know that the task is created unclaimed.

When assignement is set later (using service call for example), you can check if your task-variables already contain a "claim" date from prior assignements (or assignement when task was created). So yes, each assignment causes an event to be thrown.

Re: History by User Task Claim time

dbrucegrant — Fri, 13 Feb 2015 19:45:40 GMT

claim_time_ is now a column in the act_hi_taskinst table. Is there a way (in 5.16.3) to access this value through a query OR do I still have to track my own instance of date claimed in a local variable instance?

Thanks,
Bruce.

Re: History by User Task Claim time

jbarrez — Wed, 18 Feb 2015 15:50:14 GMT

No, it seems that the query doesn't support claim time at the moment.

Cheesy answer: always welcoming pull requests 😉

Re: History by User Task Claim time

alin — Fri, 19 Jun 2015 05:06:21 GMT

Could you create your own createNativeTaskQuery() to access the claim time?

Re: History by User Task Claim time

trademak — Sun, 21 Jun 2015 18:40:18 GMT

Sure that's possible. You can use the NativeHistoricTaskInstanceQuery. But we should add it to the default API as well.

Best regards,