-
Bug Report
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
3
-
XL
When using local process variables (setVariableLocal) in Camunda BPM,
- Optimize can have multiple variable values per variable per process instance (in group by variable reports)
- Optimize uses the local variable value in the raw data report as value for the variable (if local value was latest)
- Optimize uses both variable values in our new variable reports (e.g. summing even the variable values inside of the same process instance)
Please see screenshots from Cockpit and Optimize Reports as well as attached example BPMN process.
Expected behaviour:
Most probably we should ignore lower scopes for now and only use the process scope latest state, something that probably needs a follow up discussion.
This is the controller panel for Smart Panels app
[OPT-3893] Local Variables can lead to multiple variable values per process instance
| Issue Type | Original: Feature Request [ 2 ] | New: Bug Report [ 1 ] |
| Attachment | New: processvariabletest.bpmn [ 34684 ] |
| Description |
Original:
What is the desired functionality that you are missing?
Which problem are you going to solve with this functionality? |
| Mentioned Roles |
| Mentioned Groups |
| Attachment | New: Screenshot 2020-06-19 at 11.57.18.png [ 34685 ] | |
| Attachment | New: Screenshot 2020-06-19 at 11.57.44.png [ 34686 ] | |
| Attachment | New: Screenshot 2020-06-19 at 11.58.16.png [ 34687 ] | |
| Attachment | New: Screenshot 2020-06-19 at 11.58.34.png [ 34688 ] |
| Description |
New:
When using local process variables (setVariableLocal) in Camunda BPM,
* Optimize has the same variable twice with different values per process instance (in group by variable reports) * Optimize uses the local variable value in the raw data report as value for the variable * Optimize uses both variable values in our new variable reports (e.g. summing even the variable values inside of the same process instance) Please see screenshots from Cockpit and Optimize Reports as well as attached example BPMN process. *Expected behaviour:* Most probably we should ignore lower scopes for now and only use the process scope latest state, something that probably needs a follow up discussion. |
| Mentioned Roles |
| Mentioned Groups |