Thanks LJ and everyone else for the responses. I realize logically why these messages occur. This really all stemmed from me trying to understand what BMC workflow is causing this just on an Approve or reject selection from the process bar.
During this investigation I noticed that when a user clicked on the approver tab the Save button would highlight because BMC did not disable the change flag on some hidden z_Temp fields. So wondered under what circumstances you may not want the change flag to be disabled on a hidden field. I realize that the "This record has been updated by another user since you retrieved it..." is probably filter related from a push - probably by them updating the Approval Status field. BMC support just cam back and reported this is related to SW00342156. Regards, Andrew Goodall Software Engineer 2 | Development Services | jcpenney . www.jcp.com <http://www.jcp.com/> ________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of LJ LongWing Sent: Friday, September 02, 2011 9:10 AM To: [email protected] Subject: Re: disable change flag on hidden fields Andrew, As others have pointed out, the 'this record has been updated' is in relation to the fact that when you hit 'save', the client checks the last modified date of the record on the screen against the last modified date on the server, if the two don't match (the one on the server is newer), it gives you that message. The 'disable change flag' is a flag used on the client only that indicates if a field is changed and you choose to close the window without saving, if the flag isn't set to 'false', then you get the prompt 'are you sure you want to navigate away from this page' (Mid-Tier) or 'do you want to close this window without saving' (client)....but the answer to your question of 'why would you want to do that'....not entirely sure, I'm sure it was an oversight on the developers part...I try to make it so that all system populated hidden fields have it set to true... From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Andrew C Goodall Sent: Thursday, September 01, 2011 5:26 PM To: [email protected] 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 <http://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"_ _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"
