One scenario I can think of is the case where you need to do a push to that form to trigger some other change (Think of it like walking a table field when you don't want to put a table on a form).
I use this method for custom notifications. I have a form that defines the selection criteria and the message. On submit I do a push to the notification definition form modifying all matching records (all I set on the notification form is a display only temp field with the ticket id of the source). Workflow on the definition form then does a push to send the messages. If the disable change flag on the temp field was not set to false then the workflow to actually send the message would never fire. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Andrew C Goodall Sent: Thursday, September 01, 2011 6: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 though 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 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
