Hi Alan
Attached is an earlier posting to the arslist that gives an alternative to
creating your stack of filters.
HTH
David Sanders
Remedy Solution Architect
Enterprise Service Suite @ Work
==========================
tel +44 1494 468980
mobile +44 7710 377761
email [email protected]
web http://www.westoverconsulting.co.uk
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of R. Alan Monroe
Sent: Friday, December 04, 2009 1:41 AM
To: [email protected]
Subject: Re: Am I not understanding auditing?
> No, you're not missing anything. I completely agree with you; it's a
> bit lacking in its current implementation. I think it would be much
> more useful if auditing included both the old and the new value.
> However the auditing as it is currently designed only records the
> new value. You would have to get the previous value by finding when
> it was set to the previous value in a prior log entry.
Oh well, back to writing a giant stack of filters, then.
Alan
____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
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"
--- Begin Message ---
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"_
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
--- End Message ---
