What about using an SQL statement to pull this from the H table directly? -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Opela, Gary L CTR USAF AFMC 72 CS/SCBAH Sent: Friday, October 17, 2008 7:12 AM To: [email protected] Subject: Re: Escalation Action Changing Pushed Field
It's a bug. I've noticed it too. There's nothing you can do about it with your current version, and I'm not sure if it is fixed in newer actions. You could consider adding a field to your form that will basically replicate Status History.Resolved.user. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Gayford, Matthew C. Sent: Friday, October 17, 2008 8:53 AM To: [email protected] Subject: Escalation Action Changing Pushed Field ** List, I've got an escalation that pushes values from HPD:Help Desk to a staging form. One of the values I want to push is $Status History.Resolved.USER$. However, each time I select that field or type it in and press modify action, it switches it to $Status History.New.USER$. Has anyone seen this before? Any suggestions? Go home early? ARS & ITSM 7.0.01p003, MSSQL 05 Thanks, Matt Matthew C. Gayford Technology Research & Development Information Technology Systems Division University of North Carolina Wilmington (910) 962-7177 __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
