Auditing data and approvals
Auditing requires configuration at the following levels:
- Form level—Enable auditing for a form, specify an audit style, and specify the name of the form that will contain the audited data. If the audit form does not exist, AR System creates it.
- Field level—Specify whether a field should be:
- Audited—A change to this field triggers audit processing.
- Copied—The field value is copied to the corresponding field in the audit form if the audit field is triggered. Audit fields that have not changed are not copied.
- Audited and copied—The field triggers an audit if the field is changed. If it is not changed, it is still copied.
When you configure a main form for auditing, you specify whether to perform a form-style audit or a log-style audit. Because AR System updates the audit forms for both styles, a special user named AR_AUDITOR performs the audits. This name is displayed in the Last Modified By field for all audits.
You can selectively audit entries by providing an audit qualification. If the audit qualification fails, the audit does not occur even if the values of audit fields have changed.
For more information about auditing such as configuring auditing, types of audit, and deleting audit forms, see the following topics:
Action | Reference |
---|---|
Understand how a form-style audit records data from the main form to an audit form. | |
Understand how a form-style audit records data from the main form to a log form | |
Learn about different types of audit forms, audit styles, field properties, audit processing, and so on. | |
Learn how to enable auditing on a form and specify the fields to be audited. | |
Learn how to use a flag field to refine your search and view changes to a field. | |
Learn how to delete an audit form by using the ARDeleteSchema API call. | |
Understand how Approval Server can help support any compliance audit that requires proof of signatures. |