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 & ReceiveTask

chentaoactiviti

I use ParallelGateWay to implement two ways to the end .
But when one of them arrived the end event, the task on the other side still can be executed by user or group.only when I deleted the processInstance , they would be deleted. So why ? Doesn't Activiti5.3 support the asynchronism?

Find more posts tagged with

Comments

hrabe

A ProcessInstance only ends if all executions paths ends.

chentaoactiviti

thanks for quickly reply.

you mean ,the gateway doesn't work? But when I used the jBPM5 ,it works.

ronald_van_kuij

jbpm5 != activiti 🙂

Best is to check the specs then to see what the official behaviour should be.

matthiasn

Hi there,

would there be any other way to achieve this in activiti? I would like to have a separate fork, such as in the parallel gateway, that allows me to end the instance through a receiveTask. Or is there another way to terminate the instance from the outside when I need some cleanup done before the endtask through a spring based service task? Instances should either end through a timer-based boundary event in one fork or a receiveEvent in the other fork in my scenario. Even better would be to be able to define a global receiveTask as a boundary event.

Thanks,
Matthias