nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

processInstance.isEnded never gives correct status

gs76pl

hi,

this seems like a basic question but it looks like any call to processInstance.isEnded never returns TRUE even when the actual process has been completed. I suspect that in in order to get actual process status one should execute a process query like below

ProcessInstanceQuery pq = runtimeService.createProcessInstanceQuery().processInstanceId(pid);
ProcessInstance pi = pq.singleResult();
‍‍‍‍

but even with this query when the process has been completed pi variable is null. Bearing that all in mind what is the purpose of having isEnded method when one never gets correct results while using it?

Find more posts tagged with

Comments

ronald_van_kuij

when the processinstance is active you ALWAYS get the CORRECT result 🙂 But for the real use I have no idea…

gs76pl

perhaps you're getting correct results for a process status while calling other processInstance methods e.g. isActive etc. but as i said when one uses isEnded the result is always wrong (completed process doesn't change its processInstance status isEnded to true). The code/flow i've been testing for this is as below:

<br><definitions id="definitions"<br> xmlns="<a href="http://www.omg.org/spec/BPMN/20100524/MODEL" rel="nofollow noopener noreferrer">http://www.omg.org/spec/BPMN/20100524/MODEL</a>" xmlns:activiti="<a href="http://activiti.org/bpmn" rel="nofollow noopener noreferrer">http://activiti.org/bpmn</a>"<br> targetNamespace="Examples"><br><br> <process id="helloProcess"><br><br>&nbsp; <startEvent id="start" /><br>&nbsp; <sequenceFlow id="flow1" sourceRef="start" targetRef="collect1" /><br><br>&nbsp; <userTask id="collect1">&nbsp; <br>&nbsp; </userTask><br><br>&nbsp; <sequenceFlow id="flow2" sourceRef="collect1" targetRef="end" /><br><br>&nbsp; <endEvent id="end" /><br><br> </process><br><br></definitions><br>

and the java code:

<br>ProcessInstance pi = runtimeService.startProcessInstanceByKey("helloProcess");<br><br>String taskId = taskService.createTaskQuery().singleResult().getId()<br>taskService.complete(taskId);<br><br>pi.isEnded()<br>

for the code as above pi.isEnded() call returns FALSE even though the whole process has been completed as there was only one userTask

ronald_van_kuij

I never mentioned isActive() and I was only making a joke… sorry that that was not clear…

What you mis here is that the pi you use is a 'disconnected' representation of the instance state. The only updates take place in the database. So you have to refresh the pi and then pi will be null since it is not active anymore. It will be in the history tables though where you can see the state.

This is one of the less obvious things of activiti, but once you know this, it works.

gs76pl

thanks for the clarification.
i've suspected something like that is going on (the same way drools flow works) but unless i miss something more isEnded method doesn't make sense in my opinion.
As you said once the process has been completed its history is available through history service ie.

<br>HistoricProcessInstance hpi = historyService.createHistoricProcessInstanceQuery().processInstanceId(pid).finished().singleResult()<br>

above works fine with my code and i can see that my process has been ended.

The problem i have with the ProcessInstance is that if it's disconnected and one need to refresh it (i assume below code is the only way to refresh a process instance)
<br>ProcessInstanceQuery pi = runtimeService.createProcessInstanceQuery().processInstanceId(pid).singleResult();<br>once the process has been ended runtimeService will never find it and as a result pi will always be null. As a consequence isEnded method doesn't make sense because:
1. if the process is active than above query will return NOT NULL (no need to call isEnded)
2. if the process has ended than above query will return NULL (no need and more importantly no way to call isEnded)

ronald_van_kuij

Correct, that is why I said

But for the real use I have no idea…

jbarrez

One reason I use it for is for unit tests with processes that have all automatic steps … but it's obviously not a 'real' use case

louis44

I'd like to follow up on gs76pl's question as it doesn't make sense to me either. Why does isEnded() exist on ProcessInstance if its behavior is so counter intuitive.

jbarrez:if your process has all automatic steps, how do you use isEnded()? When all of the steps have executed, does isEnded() return true or false?

louis44

Sorry, I just searched more and found this: http://forums.activiti.org/content/processinstanceisended-returns-false. In this thread, jbarrez indicates that if the process has all automatic steps, isEnded() will return true.

jbarrez

Correct. Always remember Activiti API's return a 'snapshot' of the data, not necessarily the 'current' state.