-
Bug
-
Resolution: Done
-
Critical
-
None
-
7.22.0.Final
-
2019 Week 23-25, 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20)
The data output variable associated to a user task, if declared twice, is not being properly stored in the resulting XML file, in fact it's not present at all.
As an example use the distribution IT Orders example. See attached screenshot where parameter "approved_" is declared twice, once moving this process to Stunner and trying to save it, the variable disappears on the resulting .bpmn file.
See: Steps to Reproduce
Actual restult: The variables, once declared twice, are not being present on the result BPMN file (XML), so once running or loading the process, the data output assignments are not being present anymore.
Expected result: The variables are being properly stored in the BPMN file, even if declared twice.
- blocks
-
JBPM-8464 Migrate itorders main case to use new process designer
- Resolved
- duplicates
-
JBPM-8977 BPMN Editor removes output variables from task without alerting or throwing error
- Resolved
- is duplicated by
-
RHPAM-2242 Stunner - [BPMN] Data output associations not working properly when declared twice
- Closed
- is related to
-
RHPAM-2521 BPMN Editor removes output variables from task without alerting or throwing error
- Closed