Output Parameter Mapping by different ways to end a rerenced process instance

Flowable Engine
1

Following behavior happens:

When a process instance is started whithin a Call Activity is deleted by RuntimeService#deleteProcessInstance, the CallActivityBehavior#completing method is called and output parameter mapping is performed. However, when a process instance started within a Call Activity is canceled by a boundary event (with cancelActivity=true) attached to the call activity, then here it is not the case.

Is this an intented behavior and if so, what is the consideration behind that?

2

No, that doesn’t sound as intended.

I would actually assume that in both cases no output mapping happens, as the called process instance never reached the end (and thus the output variables could potentially not have been created).

3

@joram so that means there will be a change in the product for this?