That means the DB instance of the record has changed and do you want to potentially over write the changes. Approvals fire filters that modify the DB entry.
-----Original Message----- From: Andrew C Goodall <[email protected]> To: arslist <[email protected]> Sent: Thu, Sep 1, 2011 7:26 pm Subject: disable change flag on hidden fields ** ITSM 7.5.01 What are some of the scenario’s where you’d want to keep the “disable change flag” = false on a hidden field? I ask because we’re seeing some behavior on “CHG:Infrastructure Change” where users are receiving the message: “This record has been updated by another user since you retrieved it..." even tough all they did was an Approve or reject action. I found some BMC hidden z_Temp fields were the “disable change flag” = false So I’m trying to rack my brain as to why you’d ever want a hidden field to have “disable change flag” = false? Regards, Andrew Goodall Software Engineer 2 | Development Services | jcpenney . www.jcp.com The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If the reader of this message is not the intended recipient, you are hereby notified that your access is unauthorized, and any review, dissemination, distribution or copying of this message including any attachments is strictly prohibited. If you are not the intended recipient, please contact the sender and delete the material from any computer. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
