Prevent Editing precondition bug?
Hi,
For one of our custom work item types, on the Save Work Item (server) operation I'm using the Prevent Editing precondition to stop anyone changing it while it progresses through a few consecutive workflow states (I have "Allow workflow actions" ticked, so it can do the state transitions okay). However, I've noticed that although in each of the individual states I'm unable to change the attribute values and save, if I change them at the same time as changing the state in the Actions dropdown, it lets the changes go through without complaint. Is this a bug?
I can see why it might be desirable to allow this when transtitioning to or from a read-only state. If it's allowable to change it, save, then perform the action and save again, why not allow both to be done together and only save once? Similarly, if you could change the state, save, change the attributes and save, then why not allow both and eliminate the extra save in between. But even allowing for those cases, whenboth the before and after states of the action are read-only I wouldn't expect it to allow anything else to change when I do the transition and save...
I suspect the explanation is simpler, though, and if "Allow workflow actions" is configured it simply skips any other checks if the state has changed. Should I raise a ticket for this?
Andy.
For one of our custom work item types, on the Save Work Item (server) operation I'm using the Prevent Editing precondition to stop anyone changing it while it progresses through a few consecutive workflow states (I have "Allow workflow actions" ticked, so it can do the state transitions okay). However, I've noticed that although in each of the individual states I'm unable to change the attribute values and save, if I change them at the same time as changing the state in the Actions dropdown, it lets the changes go through without complaint. Is this a bug?
I can see why it might be desirable to allow this when transtitioning to or from a read-only state. If it's allowable to change it, save, then perform the action and save again, why not allow both to be done together and only save once? Similarly, if you could change the state, save, change the attributes and save, then why not allow both and eliminate the extra save in between. But even allowing for those cases, when
I suspect the explanation is simpler, though, and if "Allow workflow actions" is configured it simply skips any other checks if the state has changed. Should I raise a ticket for this?
Andy.
One answer
That sounds like a bug to me.
Please do open a work item on jazz.net for it, so the dev team can review.
Cheers,
Geoff
On 1/17/2012 6:23 AM, ats wrote:
Please do open a work item on jazz.net for it, so the dev team can review.
Cheers,
Geoff
On 1/17/2012 6:23 AM, ats wrote:
Hi,
For one of our custom work item types, on the Save Work Item (server)
operation I'm using the Prevent Editing precondition to stop anyone
changing it while it progresses through a few consecutive workflow
states (I have "Allow workflow actions" ticked, so it can
do the state transitions okay). However, I've noticed that although
in each of the individual states I'm unable to change the attribute
values and save, if I change them at the same time as changing the
state in the Actions dropdown, it lets the changes go through without
complaint. Is this a bug?
I can see why it might be desirable to allow this when transtitioning
to or from a read-only state. If it's allowable to change it, save,
then perform the action and save again, why not allow both to be done
together and only save once? Similarly, if you could change the
state, save, change the attributes and save, then why not allow both
and eliminate the extra save in between. But even allowing for those
cases, when both the before and after
states of the action are read-only I wouldn't expect it to allow
anything else to change when I do the transition and save...
I suspect the explanation is simpler, though, and if "Allow
workflow actions" is configured it simply skips any other checks
if the state has changed. Should I raise a ticket for this?
Andy.