Well, since the Remedy auditing workflow stores data in Remedy forms, you could always build workflow against those audit forms to push data into your centralized form, and even reformat it there. You could then delete the original records if you didn't want them piling up in your DB.
Also, make sure you have investigated BOTH types of auditing in AR System, so that you know to what extent either might help you. Rick On 12/3/07, Durrant, Michael M. - ITSD <[EMAIL PROTECTED]> wrote: > > ** Thanks for the advice guys... I'm looking for a more generalized > solution that I can use across multiple forms. The audit filters on the > HPD:HelpDesk form in ITSM 6 do what I want, but with a filter for every > field that requires auditing. That way, I can have one Audit form with Form > Name, Field Name, Old Value, New Value, Submitter, and Create date and put > all of my auditing in one easy place. > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Rick Cook > *Sent:* Monday, December 03, 2007 12:31 PM > *To:* [email protected] > *Subject:* Re: Looping through fields > > > ** Michael, you should look into the Auditing function that's already a > part of AR System. Look in the Form Application Objects manual for v7, or > the concepts guide in 6.3. I think it will be easier to use that than to > re-invent the wheel. > > Rick > > On 12/3/07, Thad K Esser <[EMAIL PROTECTED]> wrote: > > > > ** > > Depending on your version that may already be built in to ARS, but I > > wanted to advise that if your requirement is "to detect if a field has > > changed" you want to use ('Field' != ' DB.Field'), without the TR. > > > > *Thad Esser* > > Remedy Developer > > "*Argue for your limitations, and sure enough, they're yours." *-- > > Richard Bach > > > > > > *"Durrant, Michael M. - ITSD" <[EMAIL PROTECTED] >* > > Sent by: "Action Request System discussion list(ARSList)" > > <[email protected] > > > > > > > 12/03/2007 11:07 AM Please respond to > > [email protected] > > > > To > > [email protected] cc > > Subject > > Looping through fields > > > > > > > > > > ** > > I wanted to make a Filter guide that would check which fields on a form > > had changed (DB.Field != TR.Field) and push an audit record to a > > database. I don't want to make a separate filter for every field on the > > form. > > > > Is there a way I can loop through some kind of data dictionary or? My > > intuition tells me yes, but my limited Remedy experience tells me "Huh?" > > > > Thanks, > > > > Michael > > The information contained in this email may be privileged, confidential > > or otherwise protected from disclosure. All persons are advised that they > > may face penalties under state and federal law for sharing this information > > with unauthorized individuals. If you received this email in error, please > > reply to the sender that you have received this information in error. Also, > > please delete this email after replying to the sender. > > __20060125_______________________This posting was submitted with HTML in > > it___ > > > > ***IMPORTANT NOTICE: This communication, including any attachment, > > contains information that may be confidential or privileged, and is intended > > solely for the entity or individual to whom it is addressed. If you are not > > the intended recipient, you should delete this message and are hereby > > notified that any disclosure, copying, or distribution of this message is > > strictly prohibited. Nothing in this email, including any attachment, is > > intended to be a legally binding signature.*** > > __20060125_______________________This posting was submitted with HTML in > > it___ > > > __20060125_______________________This posting was submitted with HTML in > it___ The information contained in this email may be privileged, > confidential or otherwise protected from disclosure. All persons are > advised that they may face penalties under state and federal law for sharing > this information with unauthorized individuals. If you received this email > in error, please reply to the sender that you have received this information > in error. Also, please delete this email after replying to the sender. > __20060125_______________________This posting was submitted with HTML in > it___ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
