Rick, You may be right but that's not the way I think of an ARtask. I thought it was a genuine shortcut that's just an alternative way to launch a given form, not unlike double-clicking on a table field entry.
Bruce -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Thursday, October 25, 2007 10:30 AM To: [email protected] Subject: Re: BMC Remedy Client 7.1.00 and caching issue I don't think that's a new thing, Bruce. Haven't Artasks always been a snapshot of the form? Rick -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Hendershot,Bruce D. Sent: Thursday, October 25, 2007 7:00 AM To: [email protected] Subject: Re: BMC Remedy Client 7.1.00 and caching issue We have discovered this issue also and can provide some detail. When the admin makes changes to a form or workflow, the user will not see the changes if they open the form from an artask shortcut or by drilling down into a table field to open the form. If the user opens the form via File-Open or the Open clipboard icon, it pulls the changes to the client. Also, deleting the users .arf and .arv files will also cause the new changes to be pulled to the client. Bruce Hendershot Air Products and Chemicals, Inc. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Wednesday, October 24, 2007 8:11 PM To: [email protected] Subject: Re: BMC Remedy Client 7.1.00 and caching issue Can you elaborate on the issue? Thanks, Axton Grams On 10/24/07, Nguyen, Tai D <[EMAIL PROTECTED]> wrote: > List, > > FYI to those who have upgraded their BMC Remedy Client to 7.1.00 > (8/22/07 release date). There is a caching issue with this client. > BMC Tech support has created a software defect number SW00276623. > > Thanks > > Tai > > > > > ********************************************************************** > ** > *********************************** > > Sorry for the delay to respond on this issue. We have checked at our > end and able to reproduce the problem. > > I have created a defect SW00276623 for this issue. > > We are closing the issue that is open with Support and will leave the > defect in an open status pending action from Development. Please note > that the closing of the issue with Support has no bearing on the status > of the defect. For your convenience, you can monitor the status of > your defect by going to the support website and then follow these > instructions: > > Select - View/Update under Issue Management > > Select - Defect/RFE/CAR tab > > Select - Search > > Finally, please note that going forward that all issues with defects > will be closed from the support end and the defect # will be what you > will need to use to track the status of the defect. If you have any > concerns about this or questions, please feel free to respond to this > email. > > Thank you for bringing this problem to our attention. > > Regards, > Santosh Nair > BMC Remedy Technical Support > > ********************************************************************** > ** > ************************************** > > ______________________________________________________________________ > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > ARSlist:"Where the Answers Are" > ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ________________________________________________________________________ ____ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
