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.

PROCESS_CANCELLED event not sent for parent process when call activiti subprocess encounters terminate all end event

jim1

We have a top level process which uses a <callActivity> element to start a subprocess.
One of the routes through the subprocess ends with a terminateAll end event. This is correctly cancelling both the sub process and parent process.

However, we have an ActivitiEventListener which logs each process as it ends, and we're only seeing a PROCESS_CANCELLED event being thrown for the sub process. I'd expect to also see one for the parent process as well.

Is this intended? If so, is there a way that we can detect that the parent process is also being cancelled?

Thanks.

Find more posts tagged with

Comments

jbarrez

Can you post an example xml to clarify? Are we talking about an embedded subprocess or a call activity here?

jim1

Hi,
Yes, this is using call activiti.

Example processes:

Parent
<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" xmlns

mgdc="http://www.omg.org/spec/DD/20100524/DC" xmlns

mgdi="http://www.omg.org/spec/DD/20100524/DI" xmlns:inhealth="http://inhealthcare.co.uk/bpmn" typeLanguage="http://www.w3.org/2001/XMLSchema" expressionLanguage="http://www.w3.org/1999/XPath" targetNamespace="http://activiti.org/test">
<process id="listener-parent-process-v2" name="listener-parent-process-v2" isExecutable="true">
    <startEvent id="sid-33128A96-BB1E-42E0-BCFB-C03F485801E5">
    </startEvent>
    <parallelGateway id="sid-43DDB3E8-5433-4BA7-B733-21826129FCF3"/>
    <sequenceFlow id="sid-C5F548B9-25F7-4171-A60A-C077D4332212" sourceRef="sid-33128A96-BB1E-42E0-BCFB-C03F485801E5" targetRef="sid-43DDB3E8-5433-4BA7-B733-21826129FCF3"/>
    <userTask id="sid-D00EB5FC-A179-424E-B2CC-3BFD89D43439" name="Parent flow task" activiti:async="true" activiti:candidateGroups="USER" activiti:category="CAT1" />
    <callActivity id="listener-sub-process" name="listener-sub-process" activiti:async="true" calledElement="listener-sub-process">
    </callActivity>
    <sequenceFlow id="sid-4ABCD301-736C-4577-B455-75E6537BE2D4" sourceRef="sid-43DDB3E8-5433-4BA7-B733-21826129FCF3" targetRef="listener-sub-process"/>
    <sequenceFlow id="sid-287C9C37-BFA3-47A2-B382-5C16F2A606A0" sourceRef="sid-43DDB3E8-5433-4BA7-B733-21826129FCF3" targetRef="sid-D00EB5FC-A179-424E-B2CC-3BFD89D43439"/>
    <endEvent id="sid-6D84CC2E-0929-4187-866E-2A7FC59786BB"/>
    <sequenceFlow id="sid-93E0256E-F5C7-4D2B-935C-925D5A66BE4C" sourceRef="sid-D00EB5FC-A179-424E-B2CC-3BFD89D43439" targetRef="sid-6D84CC2E-0929-4187-866E-2A7FC59786BB"/>
    <sequenceFlow id="sid-A0861B97-3CBD-4FDF-B4D8-83FA319C0D18" sourceRef="listener-sub-process" targetRef="sid-6D84CC2E-0929-4187-866E-2A7FC59786BB"/>
</process>
</definitions>
</code>

Subprocess
<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" xmlns

mgdc="http://www.omg.org/spec/DD/20100524/DC" xmlns

willb

Jim _ You're completely right. I consider this a bug. See my post... and my own answer / solution to the problem. Not pretty, bit of a hurdle, but it works. In our case, we are concerned with boundary events that cancel the Call Activity as well as the parent process being terminated. Neither of those occurrences fire the PROCESS_CANCELLED listener point.

Activiti