Thanks Rob, I was thinking this is now the ITSMProblemList but apparently there are a few dinosaurs left after all... The ARS engine still rocks. Gidd
_____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Tucker, Rob Sent: Thursday, April 16, 2009 7:39 AM To: [email protected] Subject: Re: Sample application - data-driven field auditing ** This is very well thought out David. Thanks for sharing. There are still a bunch of us dinosaurs out here Gidd :) -Rob New Edge Networks _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Gidd Sent: Thursday, April 16, 2009 6:28 AM To: [email protected] Subject: OT: Sample application - data-driven field auditing ** Comments: I have indeed placed a copy of this solution in the download section of our website. >From the less then stellar responses of the ARS List it seems like we are dinosaurs and folks on the list just don't write their own code any more, pity. Nonetheless this is a well thought out solution that can save countless hours of time. For those of you that DO write your own code this is well worth a download and review. David was very thorough and even included documentation. Gidd _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of David Sanders Sent: Wednesday, April 15, 2009 10:01 AM To: [email protected] Subject: Sample application - data-driven field auditing ** Hi All Here is a link to a small free application download to demonstrate a data-driven approach to field data auditing which I hope will be of use to some of you. The sample application demonstrates how changes to field data can be recorded. Rather than creating separate filters for each field to be audited, the application uses a data-driven approach where fields can be added to or removed from the list being audited without requiring any workflow changes. The audit of data changes can either be stored in an Audit Trail (diary) field on the data record, or stored as separate change records in a Change Log form. Only changed fields are audited for each transaction, and the audit log produced includes the user who made the change, time of the change, as well as the original and changed field values. All audited changes in a single transaction are included in a single log entry, rather than a separate entry for each field being changed. The documentation provided with the sample application explains how to add this field data auditing functionality to any existing Remedy data form. http://www.westoverconsulting.co.uk/utilitiesAudit.html or http://www.buoyantsolutions.net <http://www.buoyantsolutions.net/> under the Downloads.ARS 7.x section Regards David Sanders Remedy Solution Architect Enterprise Service Suite @ Work ========================== tel +44 1494 468980 mobile +44 7710 377761 email <mailto:[email protected]> [email protected] web <http://www.westoverconsulting.co.uk/> http://www.westoverconsulting.co.uk _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
