Call activities are used to start an instance of another process definition. The original process waits until the called process is complete before continuing with its own process flow.
The calledElement
property uses a processDefinitionId
to define the type of process to start.
Process variables can be mapped from the originating process to the called process as inputs. Similarly, process variables from the completed called process can be passed back to the originating process as outputs. The mapping between the two processes is defined in the <process-name>-extensions.json
file for the process definition under the mappings
section.
Call activities are graphically represented by a single, thick rounded rectangle without an icon inside.
The XML representation of a call activity is:
<bpmn2:callActivity id="Task_5" name="Start request process" calledElement="process-a6d6ca00-cbb6-45d6-ae24-50ef53d37cc4">
<bpmn2:incoming>SequenceFlow_8</bpmn2:incoming>
<bpmn2:outgoing>SequenceFlow_9</bpmn2:outgoing>
</bpmn2:callActivity>
Note: Call activities can only be used to start a process instance of a process definition that exists in the same application as the process that is calling it.
© 2023 Alfresco Software, Inc. All Rights Reserved.
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.