consider introducing different scope for variable mapping
lastchiliarch opened this issue · 1 comments
lastchiliarch commented
motivation
To be compatible with other BPMN runtimes, we need to introduce different scopes for variable mapping which means input mapping should be defined in the local scope, while the output mapping may be merged into the parent scope.
Doc: https://docs.camunda.io/docs/components/concepts/variables/#inputoutput-variable-mappings
business background
Considering sending msg in different situations, the send_notice service task will face variable conflict or overwrite if input mapping does not define in local scope.
If we change and introduce a local scope for input mapping, it will help a lot.
lastchiliarch commented
@nitram509 I'm not quit understand how to deal with the output mapping. What do you think?