Actually, folks were updating the record and saving it (ignoring that msg) which caused some issues with various fields that were updated by the approval / rejection. It was either that or close the screen down (I'm on 7.6.03 and users access system strictly via web client) and they didn't like the idea of closing the screen. I find that in most cases, by the time they clear the initial (warning) message that says 'your approval / rejection has been sent to the server for processing' the approval has been processed. The 30 second limit was only put in for the event that the approval is tied up for some reason - haven't seen it actually hit that limit in production.
Kind of surprised BMC didn't put something like that in out of the box. I also had to do some work on the approval 're-assignments'. With the web client it was returning to a search screen (lost the CR for some reason). Set that up to return to the CR and refresh the approval window. ----- Original Message ----- From: "Andrew C Goodall" <[email protected]> To: [email protected] Sent: Friday, September 2, 2011 10:13:02 AM Subject: Re: disable change flag on hidden fields Genius - love that idea. Did you do this specifically because of the "This record has been updated by another user since you retrieved it..." received when attempting to approve or reject the change request? Regards, Andrew Goodall Software Engineer 2 | Development Services | jcpenney . www.jcp.com -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of pritch Sent: Friday, September 02, 2011 9:04 AM To: [email protected] Subject: Re: disable change flag on hidden fields Yes - I actually had to put in some workflow for my client that has a 'processing, please wait ..." message, go into a loop to detect that the record has been updated by the application service and then refresh the screen for them. If after about 30 seconds it doesn't detect it, I put an alternate message up that the approval will be processed momentarily, please refresh your screen before making any additional changes. ----- Original Message ----- From: "Mike Roper" <[email protected]> To: [email protected] Sent: Friday, September 2, 2011 2:19:37 AM Subject: Re: disable change flag on hidden fields While I haven't looked at this particular workflow in a while, I've seen that issue with CHG as well. As far as I can tell there may be a few things going on. The first is that the approval process updates the change and the second is that if you have SLAs attached it's going to update some additional fields. I *think* the only reason they do that is to immediately reflect the current approval or SLA status on the change. Take this scenario... I open the change request and go to the approvals tab and approve my change. My approval happens to move the change into "Completed" because it's a close down approval. This could trigger an SLA to update the ticket. So, if you have the ticket open while workflow fires in the background, you'll get the "record has been updated" warning if you make any other changes to the record. There are a lot of things going on in background and really makes debugging a challenge. Alternatively, if you have the change open during the approval process and someone approves through approval central, you can can get the record updated warning as well. I think it's just a shortcoming in the design because when you offer multiple entry points to update a record, toes are going to be stepped on at some point. Regards, Mike Roper ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 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" 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. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 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"
