Loading...

XML

Word

Printable

Details

Type: Feature Request
Resolution: Fixed
Priority: L3 - Default
Fix Version/s: 7.4.0, 7.4.0-alpha3
Affects Version/s: None
Component/s: engine
Labels:
- SUPPORT

Description

There is a configuration option for a call activity input parameter such that all local variables of the execution executing the call activity are passed to the new process instance (currently it is only possible to pass all reachable variables (i.e. local and non-local)). This feature enables using call activity in/out parameters in combination with camunda:inputOutput elements on the call activity element.

For example, it could look like (note the local attribute):

<callActivity id="callSubProcess" calledElement="checkCreditProcess" >
  <extensionElements>
    <!-- mapping variables into call activity -->
    <camunda:inputOutput>
      <camunda:inputParameter name="inputVariable">${in + 1}</camunda:inputParameter>
      <camunda:outputParameter name="outputVariable">${out + 1}</camunda:outputParameter>
    </camunda:inputOutput>

    <!-- passing variables to called process instance -->
    <camunda:in variables="all" local="true" />
    <camunda:out variables="all" local="true" />
  </extensionElements>
</callActivity>

The same should be possible for CMMN process/case tasks.

mgm-controller-panel

This is the controller panel for Smart Panels app

Attachments

Issue Links

is related to

CAM-4518 In the modeler, I cannot define camunda:inputOutput for call activities

Closed

CAM-4517 In the modeler, I can define a "local" variable mapping for a call activity

Closed

CAM-4733 In the modeler, I can define Input/Output parameters for a call activity

Closed

Activity

People

Assignee:: Matthijs

Reporter:: Thorben Lindhauer

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 01/Sep/15 4:18 PM

Updated:: 22/Jul/19 9:48 AM

Resolved:: 14/Oct/15 9:49 AM

For a call activity/process task, I can map all local variables to the called process instance