Log-style audits

A log-style audit records data from the main form into a log form. The log form has the following key aspects:

  • Is a regular form that serves as the destination for data audited in the main form.
  • Resides on the same server as the main form.
  • Contains only audit-specific fields. 
  • Can contain data from multiple main forms.

Related topics

Auditing-data-and-approvals

AR-System-forms-overview

When you configure a main form for a log-style audit, you specify a name for the log form. When a main form is audited, AR System copies values from the main form to a text field in the log form.

Log form fields

The log form does not contain the same fields as the main form. In addition to the core fields, the log form contains the following fields.

Log form fields

 Log keys

When a log form is created, it contains special character fields named Log Key 1, Log Key 2, and Log Key 3. These fields can help in searching of log entries.

In Developer Studio, you can set a field to any of these Log Key fields. During an audit, the value of this field goes to the key that was selected.

Only three keys are available, and you cannot set two fields to the same log key. You cannot set log keys for diary and attachment fields.

Log form characteristics

Log forms have the following characteristics:

  • Have a fixed set of fields.
  • Do not belong to any application when they are created.
  • Do not belong to any lock block when they are created.

While audited main forms are imported, if the main form is audited in Log style and the Log form is not found, auditing for the main form is turned off and a warning Form not Found. ARError 303, is returned.

Watch the following video for information about how to create Log-style Audit on a form:

icon_play.pnghttps://youtu.be/NFZeSWD0mo8