1 of 1 people found this helpful
call activity is intended to refer external process definitions (from another file). So either eclipse plugin is now aware of your other files, if they reside outside of current project or there is a bug. In source code there is 'calledElement' attribute that should be the process id of the process definition it shall invoke.
This is the code for the CallActivity:
<bpmn2:callActivity id="CallActivity_1" drools:waitForCompletion="true" drools:independent="true" name="Offerte" calledElement="Offerte"> <bpmn2:incoming>SequenceFlow_33</bpmn2:incoming> </bpmn2:callActivity>
How does it link to the source-file?
The called process produces two signals; one a message end event (indicating that the tender is rejected), the other a boundary signal (the tender is accepted and the process should continu).
How do I link these messages to receiving actions in the envoking process?
they must be part of the same knowledge base as within kbase process ids must be unique and by that it can easily start it. So make sure that you add both process definitions into the same kbase.