Ali)
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing
Sent: Thursday, December 05, 2013 4:55 PM
To: arslist@ARSLIST.ORG
Subject: Re: capturing all transactions
**
That would be 'auditing'. Turn on audit on a field and any time it
Hi Ron,
I've implemented a system of leveraging the audit form capability to
capture individual field edits to a central audit form at a couple of
sites.
With form auditing on, each time a new row is written to the forms
respective audit form the fields that have changed are stored in one field.
it can be done.
> -Original Message-
> From: LJ LongWing
> To: arslist
> Sent: Thu, Dec 5, 2013 5:54 pm
> Subject: Re: capturing all transactions
>
> **
> That would be 'auditing'. Turn on audit on a field and any time it changes a
> log will be madethi
There is also the ability to Audit the form. It is not recommended since it
stores every field on the form but it can be done.
-Original Message-
From: LJ LongWing
To: arslist
Sent: Thu, Dec 5, 2013 5:54 pm
Subject: Re: capturing all transactions
**
That would be 'auditing
That would be 'auditing'. Turn on audit on a field and any time it changes
a log will be madethis won't be in the transaction diary on the record
in question, but it'll audit the entry, which it sounds like they are
asking for.
On Thu, Dec 5, 2013 at 3:45 PM, Ron Young wrote:
> User 7.6...
User 7.6...Developer 8.1. I have been asked to capture in the transaction diary
any time anyone touches any field. I know how to do it for individual fields
but I don't know how to just make a blanket statement saying this field was
changed by A on 12.5.13 and then that field changed by B on 12
6 matches
Mail list logo