Business Key for Call Activity is always checked
ingorichtsmeier opened this issue · comments
Hi @ingorichtsmeier, thank you very much for your feedback. :)
I tried to reproduce your issue, but call-activity-elements work correctly in my setting, even if the business-key is checked and unchecked in different situations:
Could you please reveal your modeler's version and maybe any extraordinary setting, or maybe even provide the respective process-model?
BR Florian
Hi @rnschk,
here is a process model to reproduce:
The error appeared after adding a variable input mapping to the first Call Activity. It doesn't propagate the business key.
Kind regards, Ingo
Hi @ingorichtsmeier, thank you. I just released v0.0.6 that should fix this issue.
The issue was caused by the variables-in-mapping used in call-activity 'CA 1'. Looking at the xml-data, one can see that both, the business-key as well as the variable mapping are written as extension-elements of type 'camunda:in', which finally lead to this behaviour.
<bpmn:callActivity id="0cfxanm" name="CA 1" calledElement="hello">
<bpmn:extensionElements>
<camunda:in source="1" target="1" />
<camunda:in businessKey="#{execution.processBusinessKey}" />
</bpmn:extensionElements>
...
</bpmn:callActivity>
BR Florian