| || |
How to disable ObjectUnlock after Post
I am working on a client enhancement request that will lock all the fields in a defect, once a particular field is set to "Yes". To do this, I added a select statement and a series of Bug.Fields("Field_Name").IsReadOnly=true to the function Sub_FieldChange. This only works temporarily, b/c when I refresh the defect, I lose the lock. In testing the code,I noticed the function "ObjectLock" and "ObjectUnlock" are at work in the background, so my question to the forum is this...do I need to code something in the function Bug_AfterPost in order to retain the lock,do I need to invoke the SET function, or is there a way to disable the ObjectUnlock after a defect has been posted (and in my case, when a field = Yes. If these theories are wayyy off-base, or if there is a similar approved method, I would appreciate a suggestion. Thanks a lot...Whalon H.
Re: How to disable ObjectUnlock after Post
After the ticket is refreshed, the MoveTo function is triggered. Add code there to check the state of your field and if it's Yes, lock the fields.
<font color="#6B6B6B">Scott Genevish
Principal Consultant Designed Quality