Red Hat Bugzilla – Bug 1248986
DataIOEditor dialog remembers old process variables as Source or Target options
Last modified: 2015-11-23 10:46:47 EST
Description of problem:
DataIOEditor dialog remembers old process variables which have been edited or deleted.
Version-Release number of selected component (if applicable):
6.3.0 community (version which uses the new DataIOEditor dialog for editing DataInputs/ Outputs / Associations).
Steps to Reproduce:
1. Create a new BP
2. Add a new process var "myvar", datatype "String"
3. Add a User Activity
4. Create a DataInput called "myinput", datatype "String", with source "myvar"
5. Change the name of the process var "myvar" to "yourvar"
6. Edit the Associations of the User Activity
7. The Source of "myinput" is still set to "myvar" and "myvar" is listed in the drop-down.
Works good, but I have a little remark.
Assignments property and Source code of elements remembers old process variables which have been edited or deleted. You need to open Assignments and save it without any changes or save whole project and reopen it. For clear incorrect link. see Attachment.
Also bug 1273871 was opened.
Created attachment 1085118 [details]
Assignments after process variables renaming
The behaviour in the DataIOEditor is improved, in that it doesn't remember the old process variable that was renamed.
Kirill - as the behaviour reported in the BZ is fixed, and you've opened https://bugzilla.redhat.com/show_bug.cgi?id=1273871 for the more general problem of process variable renaming, can we close this BZ?
remaining things are relate to this issue not to new one. But you are right if new one will be fixed this issue also will be resolved. So we have two options for 6.2 release: to finish this one and fix new one for next releases or close it and concentrate on new issue.
Kris - will you take a look at this and decide what we should do for 6.2?
The underlying issue is that when the user renames a process variable which is linked to a DataInput, the sourceRef of the dataInputAssociation isn't updated, so it still refers to the old process variable, which is now invalid (https://bugzilla.redhat.com/show_bug.cgi?id=1273871).
The bug I reported here and made the commits for is that after renaming the process variable, the DataIOEditor still showed a link to the old process variable. The fix involved removing the link to the old process variable when the DataIOEditor is opened. This is a limited fix.
To fix the issue fully, we'd need to update all references to process variables whenever a process variable is renamed, i.e. fix https://bugzilla.redhat.com/show_bug.cgi?id=1273871
I spoke to Tiho about this and he indicated that resolving this is not a minor thing. That's why I wonder whether we should close this BZ for 6.2 and fix BZ1273871 for the next release.
Note that this isn't a regression. This behaviour was present in bpms6.1.
I suggest we close this one of as a sufficient (temporary) fix, and keep the other one open until we implement full refactoring support. So putting back to ON_QA, so they can close this off as verified for 6.2, wdyt?
OK, let's do it in this way.