flowable / flowable/flowable-engine
Decision Tables in Multi-Instance Subprocesses Write Output to Main Process
- Dominant language
- Java
- Stars
- 9.5k
- Forks
- 2.9k
- Avg merge
- 7h 8m
- Merged PRs (30d)
- 2
Description
**Describe the bug**
When you attempt to use a decision task inside of a multi-instance subprocess that operates in parallel, the output variables get written to the main process. This causes all instances of the multi-instance subprocess to "see" the outputs from the last executed decision table.
**Expected behavior**
Output variables from decision tasks should be scoped in such a way to be usable inside of parallel multi-instance subprocesses
**Code**
Sample app attached. The sample app contains a groovy script task that creates an `items` array containing the numbers 1, 2, & 3. Following that there is a parallel multi instance sub-process containing a decision task and a user task with a form. Decision task takes the `item` passed into the specific instance and uses one a rule to write it back out to `item_out`. The user tasks form supplies a way to view `item`, `item_out`, and a `p_var` process variable set by the script task. Looking at the executions of the decision table in the flowable-admin app, it's clear that each instance is operating on the correct `item` variable and putting out a correct output, but only the last `item_out` is displayed for all forms.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.