-
Bug
-
Resolution: Done
-
Critical
-
6.0.2
-
None
Description of problem:
If you set "variable name" in the multi-instance sub process, which is the variable which will store element of the current iteration, it is not possible to use this variable name in the Assignment section.
Version-Release number of selected component (if applicable):
6.0.2
How reproducible:
always
Steps to Reproduce:
1. Create process which includes multi-instance sub process
2. Set "variable name" of this multi-instance sub process
3. Model Human Task or Service Task within this multi-instance sub process
4. Try to perform an assignment of the variable name you have just set to the input of the newly modeled task - not possible, the value is simply not being displayed.
==== use attached git repository ===
- import repository
- open Parent project
- check the "variable name" of the multi-instance sub process
- try to assign this variable in the reusable sub process, which is modeled within the multi-instance sub process - it is not possible. It is not related to reusable sub process only, there can be whatever task which has Assignments section - human task, service task
Actual results:
Variable name of multi-instance sub process is not being displayed in the Assignments editor of the tasks modeled within this multi-instance sub process.
Expected results:
Variable name of multi-instance sub process is being displayed in the Assignments editor of the tasks modeled within this multi-instance sub process.
Additional info:
The workaround is to create PROCESS with the same name as the multi-instance subprocess "variable name", then perform the mapping, then delete the process variable.
- is related to
-
RHBPMS-1609 Element of current iteration does not get updated in the Multi-Instance sub process
- Verified
-
RHBPMS-793 On Entry/Exit action script is not executed in multi-instance sub process
- Verified
- relates to
-
RHBPMS-1609 Element of current iteration does not get updated in the Multi-Instance sub process
- Verified
-
RHBPMS-793 On Entry/Exit action script is not executed in multi-instance sub process
- Verified