Historic Process instance variable is out of date for serialized Java object

pstapl — Mon, 14 Dec 2015 15:02:16 GMT

I am using Activit's forms to change the field values in a Serializable Java object as part of a process.I have noticed that the historic process instance variables are often out of sync with the runtime version of the variables when the process has finished (and sometimes even during the process ex

Re: Historic Process instance variable is out of date for serialized Java object

jbarrez — Wed, 16 Dec 2015 12:35:05 GMT

Does the runtime variable reflect the change? Ie. when you add another task after it, and you fetch the object, are the runtime values updated?

Re: Historic Process instance variable is out of date for serialized Java object

pstapl — Mon, 21 Dec 2015 09:38:32 GMT

The runtime variables seem to be updated correctly after all user tasks - this problem only seems to affect the historic variables.

I updated my example to contain a new User Task after the other two. It does not have any form properties. New BPMN XML is:

<code>
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:activiti="http://activiti.org/bpmn" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlnsmgdc="http://www.omg.org/spec/DD/20100524/DC" xmlnsmgdi="http://www.omg.org/spec/DD/20100524/DI" typeLanguage="http://www.w3.org/2001/XMLSchema" expressionLanguage="http://www.w3.org/1999/XPath" targetNamespace="http://www.activiti.org/test">
<process id="myProcess" name="My process" isExecutable="true">
    <startEvent id="startevent1" name="Start"></startEvent>
    <endEvent id="endevent1" name="End"></endEvent>
    <userTask id="usertask1" name="User Task">
      <extensionElements>
        <activiti:formProperty id="field1" name="Field1" type="string" expression="${myobject.field1}" required="true"></activiti:formProperty>
        <activiti:formProperty id="field2" name="Field2" type="string" expression="${myobject.field2}" required="true"></activiti:formProperty>
      </extensionElements>
    </userTask>
    <sequenceFlow id="flow1" sourceRef="startevent1" targetRef="servicetask1"></sequenceFlow>
    <serviceTask id="servicetask1" name="Service Task" activiti:class="com.example.mytest.MyServiceTask"></serviceTask>
    <sequenceFlow id="flow4" sourceRef="servicetask1" targetRef="usertask1"></sequenceFlow>
    <userTask id="usertask2" name="User Task">
      <extensionElements>
        <activiti:formProperty id="field1" name="Field1" type="string" expression="${myobject.field1}" required="true"></activiti:formProperty>
        <activiti:formProperty id="field2" name="Field2" type="string" expression="${myobject.field2}" required="true"></activiti:formProperty>
      </extensionElements>
    </userTask>
    <sequenceFlow id="flow5" sourceRef="usertask1" targetRef="usertask2"></sequenceFlow>
    <sequenceFlow id="flow6" sourceRef="usertask2" targetRef="usertask3"></sequenceFlow>
    <userTask id="usertask3" name="User Task"></userTask>
    <sequenceFlow id="flow7" sourceRef="usertask3" targetRef="endevent1"></sequenceFlow>
</process>
</definitions>
</code>

I then updated the testcase to retrieve both the runtime and historic variable and print it out after the first, second and third user task. (For the third task there is no runtime verison). New testcase is:

<java>
package com.example.mytest;

import java.util.HashMap;
import java.util.Map;

import org.activiti.engine.runtime.ProcessInstance;
import org.activiti.engine.task.Task;
import org.activiti.engine.test.ActivitiRule;
import org.activiti.engine.test.Deployment;
import org.junit.Assert;
import org.junit.Rule;
import org.junit.Test;

public class ProcessTest {

@Rule
public ActivitiRule activitiRule = new ActivitiRule();

@Deployment(resources = {"MyProcess.bpmn"})
@Test
public void test() {

ProcessInstance pi = activitiRule.getRuntimeService().startProcessInstanceByKey("myProcess");

Map<String, String> properties;
Task task;
MyBean myobject;

properties = new HashMap<String, String>();
properties.put("field1", "value1");
properties.put("field2", "value2");

task = activitiRule.getTaskService().createTaskQuery().processInstanceId(pi.getId()).singleResult();
activitiRule.getFormService().submitTaskFormData(task.getId(), properties);

System.out.println("After 1st User Task");
// Retrieve and print historic variable
myobject = (MyBean) activitiRule.getHistoryService().createHistoricVariableInstanceQuery().processInstanceId(pi.getId()).variableName("myobject").singleResult().getValue();
System.out.println("Historic value - field1: " + myobject.getField1() + " field2: " + myobject.getField2());
// Retrieve and print runtime variable
myobject = (MyBean) activitiRule.getRuntimeService().getVariable(pi.getId(), "myobject", MyBean.class);
System.out.println("Runtime value - field1: " + myobject.getField1() + " field2: " + myobject.getField2());

properties = new HashMap<String, String>();
properties.put("field1", "value3");
properties.put("field2", "value4");

task = activitiRule.getTaskService().createTaskQuery().processInstanceId(pi.getId()).singleResult();
activitiRule.getFormService().submitTaskFormData(task.getId(), properties);

System.out.println("After 2nd User Task");
// Retrieve and print historic variable
myobject = (MyBean) activitiRule.getHistoryService().createHistoricVariableInstanceQuery().processInstanceId(pi.getId()).variableName("myobject").singleResult().getValue();
System.out.println("Historic value - field1: " + myobject.getField1() + " field2: " + myobject.getField2());
// Retrieve and print runtime variable
myobject = (MyBean) activitiRule.getRuntimeService().getVariable(pi.getId(), "myobject", MyBean.class);
System.out.println("Runtime value - field1: " + myobject.getField1() + " field2: " + myobject.getField2());

task = activitiRule.getTaskService().createTaskQuery().processInstanceId(pi.getId()).singleResult();
activitiRule.getFormService().submitTaskFormData(task.getId(), properties);

System.out.println("After 3rd User Task");
// Retrieve and print historic variable
myobject = (MyBean) activitiRule.getHistoryService().createHistoricVariableInstanceQuery().processInstanceId(pi.getId()).variableName("myobject").singleResult().getValue();
System.out.println("Historic value - field1: " + myobject.getField1() + " field2: " + myobject.getField2());
// Retrieve and print runtime variable
// Does not work, as the process is finished. Returns ActivitiObjectNotFoundException
//myobject = (MyBean) activitiRule.getRuntimeService().getVariable(pi.getId(), "myobject", MyBean.class);
//System.out.println("Runtime value - field1: " + myobject.getField1() + " field2: " + myobject.getField2());


Assert.assertEquals(0, activitiRule.getRuntimeService().createProcessInstanceQuery().count());
myobject = (MyBean) activitiRule.getHistoryService().createHistoricVariableInstanceQuery().processInstanceId(pi.getId()).variableName("myobject").singleResult().getValue();
Assert.assertEquals("value4", myobject.getField2());
}

}
</java>

The output from the execution gives:

<code>
After 1st User Task
Historic value - field1: null field2: null
Runtime value - field1: value1 field2: value2
After 2nd User Task
Historic value - field1: null field2: null
Runtime value - field1: value3 field2: value4
After 3rd User Task
Historic value - field1: value3 field2: value4
</code>

So it appears that after the first and second user task the historic process instance variable is not updated at all, but after the 3rd user task it is updated correctly. The runtime variable is always updated correctly.

topic Historic Process instance variable is out of date for serialized Java object in Alfresco Archive

Historic Process instance variable is out of date for serialized Java object

Re: Historic Process instance variable is out of date for serialized Java object

Re: Historic Process instance variable is out of date for serialized Java object