Bug/Feature request on reference naming
When renaming a reference, it seems to be partly a new object in K2 Workflow.
Especially in the loop step (tested with 5.2) there are problems/errors:
The wizzard allows to rename the automatically created reference for the loop data. However, the system looses reference when one actually renames the reference. Current behviour:
- If the reference is used somewhere within the loop, the system shows an error that the old reference (Item=>Value) is not defined. One has to replace the referencing to get rid of the error.
- When the workflow is deployed, it throws an error. It says that the reference (the changed one) is not defined.
Suggestion: Allow renaming of the reference, exchange automatically the name where it is used, allow proper deployment.
1
vote
