Lyle, You are 100% correct....I was basing my post off of a manual solution I've implemented in the past for reporting metrics which requires the 'all' option....very useful for things like 'how long did it sit assigned to user x'....if your audit always contains the assignee, you can run a report that aggregates the times together and give you a report of how long something sat in that state...
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Friday, December 04, 2009 10:53 AM To: arslist@ARSLIST.ORG Subject: Re: Am I not understanding auditing? LJ, doesn't that depend on what kind of auditing has been configured and on when the last time the value in question was changed? For example, if the form is configured for Log auditing, and the field in question (A) is configured simply as Audit, it will only write and entry to the audit log when it is actually changed. If you have other fields configured for auditing on that form, and they have been changed since the last time field A was changed, when you change field A again, the most recent log entry before the current one will not contain a value for A; it will contain the values for the other fields that were updated. So, it seems for what you're suggesting to work consistently, you have to make sure that you've configured your auditing in a specific way (i.e., always copy all audited values to the log so that the previous entry always contains the previous value). And, if you've got it configured in that way, your audit log is filled with a lot of noise due to recording the values of fields that haven't changed in a long time, making the audit log less useful in the end, because it becomes harder to easily see when values have actually changed. Am I missing something? Lyle -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of LJ Longwing Sent: Friday, December 04, 2009 8:49 AM To: arslist@ARSLIST.ORG Subject: Re: Am I not understanding auditing? Alan, As others pointed out, you aren't missing anything....but what you can do is have auditing turned on, this will capture the first modification of a field at submit. Then create a 'self join' of the audit form joining two subsequent entries of each other....the first entry will contain the 'old value', the second entry will contain the 'new value', and you won't need to create workflow to get this information. To create the self join you may need to use an SQL View...but the premise is basically the max(original request id) where original request id is < original request id....this gives you the last entry created for this record... -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of R. Alan Monroe Sent: Thursday, December 03, 2009 6:19 PM To: arslist@ARSLIST.ORG Subject: Am I not understanding auditing? I was experimenting with the built-in auditing for the first time on a test server, in log mode. Unless I'm missing something really obvious, it seems to just record the same thing in both the regular record and the log. For example, if I change a serial number from 123 to 123a, I see 123a recorded in both the record of the main form and the corresponding entry in the log form. This seems completely worthless to me since I very much want to record the FORMER value during audit, not the CURRENT value. What am I missing? Alan ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are" ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are" NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
