-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
Acceptance Criteria (Required on creation):
In https://docs.camunda.org/manual/7.16/user-guide/process-engine/variables/#input-output-variable-mapping, it is not clear to which scope local variable is created once variable is defined via InputParameter in Modeler. In actual, variable is created local to execution rather than local to activity in this case.
Change following line:
"The name attribute of an inputParameter denotes the variable name inside the activity (a variable to be created in local to execution scope)"
Hints (optional):
This is the controller panel for Smart Panels app
[CAM-14223] Documentation: Clarify the scope in which local variable is created in case of InputParameter mapping
This ticket was migrated to github: https://github.com/camunda/camunda-bpm-platform/issues/2708. Please use this link for any future references and continue any discussion there.
this whole thing of scope vs execution is extremely confusing. When I enter a Task and use Input mapping, I intuitively expect the variables created (mapping result) to be "local variables" for this task. This is exactly what Cockpit shows by the way. But if I call "GET localVariable" for this task, then the local variables are not returned. I dont want to mess with "execution scope" to get this local variables. What is the purpose then of Input mapping, if it is not to simulate passing of parameters and "scope isolation" ?