ending process does not end tasks

[kukeltje]

http://jira.jboss.com/jira/browse/JBPM-392
and
http://jira.jboss.com/jira/browse/JBPM-590

are about this 'problem'

392 is closed as won't fix since there are some related loggings??? I personally do not see the problem here. Why not just cancel them?

Related to the ending of a process from a leg of a fork, this is a behaviour two of my colleagues (a minority according to Tom) did not expect. I personally did not expect this as well.

There is a workaround to write an actionhandler that cancels all open tasks.

The other solution is to add this to the 'end-complete-process' to end all tasks or add a new attribute end-task(s) to the end-state to do this like proposed in http://jira.jboss.com/jira/browse/JBPM-1184.

any suggestions?

[tom.baeyens]

anyone else got an opinion on this ?

ronald, you currently have the majority: 100% in favour of ending tasks :-)

can you update http://wiki.jboss.org/wiki/JbpmJpdl4 to reflect this. if this thread would switch to leaving tasks open, we can always update it again :-)

[jbarrez]

I vote in favour, too.

In current implementations, I'm adding a "processInstances.end not null" when I need to retrieve a task list.

So ending the task automatically would speed up these queries a bit ;-)
But conceptually it seems only logic to me that tasks are ended when the process ends.

[camunda]

+1
I also think it doesn't make sense to have open task instances for ended processes. Only in rare cases maybe, therefor it would be better to add an attribute for don't ending tasks...

By the way, there I have some thoughts on task management too, but I open up another thread...

[tom.baeyens]

"camunda" wrote:
By the way, there I have some thoughts on task management too, but I open up another thread...

please do.

i'll try to compile a list of topics that would be good to discuss in dublin.

[camunda]

Here we go: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155609

[kukeltje]

Do we change this behaviour in 4.0 or in combination with the 'end-process-completely' attribute in 3.2.x as well. Not a lot of people seem to use this attribute and I already have a patch.

[tom.baeyens]

i don't think it's good to change the default in 3.x.

[kukeltje]

no, not the default of a plain end-state, but only if one uses the end-process-completely attribute. A non-documented feature, that is not in the xsd, nor in the designer, nor in ......

Should not be a problem then... right? otoh, I have a patch that we can use locally, so it works for us now.