topic Re: Request historic task variables is empty in Alfresco Archive

Request historic task variables is empty

dominik_eisenbe — Thu, 13 Jun 2013 13:32:11 GMT

Hi, i tried to request variables of completed user tasks, but allways get an empty list, when executing:List<HistoricVariableInstance> variables = historyService.createHistoricVariableInstanceQuery().taskId(historicTask.getId()).list();‍‍‍Using the taskService dows not work for historic tasks.

Re: Request historic task variables is empty

trademak — Fri, 14 Jun 2013 07:08:08 GMT

Hi Dominik,

The variable instance query is the one you should use for this. What history level are you using?
How did you retrieve the historicTask variable?

Best regards,

Re: Request historic task variables is empty

dominik_eisenbe — Mon, 17 Jun 2013 07:12:44 GMT

Hi trademak,

the history level was set to audit. I now changed this to full in my spring activiti configuration. Nevertheless, the list of historic variables is empty.

The way, I retrieve the historic task is:
<java>
List<HistoricTaskInstance> list = historyService.createHistoricTaskInstanceQuery().finished().processInstanceId(processInstanceId).list();
</java>

Best regards
Dominik

Re: Request historic task variables is empty

trademak — Mon, 17 Jun 2013 08:37:11 GMT

Audit should also be file to fill the variables in the historic variables table.
You are using Activiti 5.12, right?
Can you create a unit test that shows your issue?

Best regards,

Re: Request historic task variables is empty

mpriess — Wed, 28 Aug 2013 17:39:12 GMT

Hi Tijs,

I created today with Dominik together a example process and a unit test to reproduce the problem.

https://github.com/MPriess/activiti-historyservice

Best regards,

Michael and Dominik

Re: Request historic task variables is empty

frederikherema1 — Wed, 04 Sep 2013 09:14:22 GMT

WHen submitting a task-form, the variables are flushed to the process instance, they are not task-local. Only taskLocal (taskService.setVariableLocal()) are recored with a taskId in the history.

So those values are recorded in the history as "process" variables, rather than task-variables. This is not a bug…