A form-style audit records data from the main form to an audit form. The audit form:

• 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 the same fields as the main form.
• Contains several audit-specific fields.

When you configure a main form for a form-style audit, you specify a name for the audit form. When the form is audited, data from the main-form fields configured for auditing is copied to corresponding fields on the audit form. If there are fields in the main form not configured for auditing, the corresponding fields on the audit form are left blank.

Audit form characteristics

Audit forms have the following characteristics.

General

• Any changes to the definitions in the main form (such as adding or deleting a data field) are applied to the audit form.
• You can change the form and view properties of the audit form.
• Only an administrator can delete entries.
• If the main form belongs to a deployable application, the audit form also belongs to the same application.
• If the main form is made "licensable," then the audit form is also made licensable.
• An audit form cannot be further audited, but it can be archived.
• Archive forms cannot be audited.

Fields

• Data fields, attachment pools, and panel holders cannot be modified or added to an audit form. All other field types, such as trim, or table, can be added or modified.
• Limit information of the fields must be the same as the corresponding fields in the main form.
• The permissions for fields on the Audit forms is read access.

Workflow

• When an audit form is created, the workflow from the main form is not copied to the audit form. You can add workflow to an audit form, but workflow cannot modify data in an audit form.

Import and export

• Data can be exported from an audit form, and data can be imported into an audit form, but existing entries in an audit form cannot be overwritten.
• While audited main forms are imported, if the main form is audited Copy style and the audit form is not found, audit for the main form is disabled and a warning (Form not Found. ARError 303 ) is returned.
• During an import in place, if the main form has fields added or deleted, those fields are also added to the audit form.
• If the main form is part of a lock block from an exported definition, the audit form is part of the same lock block. If a field in the main form is audited after locking the form, the corresponding flag field is not created. (For more information, see Using-flag-fields-to-view-changes-to-an-individual-field.)

Audit forms created by AR System

If AR System creates an audit form, it has the following additional characteristics:

• Any uniqueness constraints (indexes) that exist on the main form are removed from the audit form. You can add indexes to the audit form.
• When the audit form is created, the entry points are cleared. The administrator can add entry points.
• When the audit form is created, the disable status history form property is not copied from the main form to the audit form. The audit form has status history disabled by default.
• All other form properties are copied from the main form to the audit form. However, after the audit form is created, subsequent changes to the main form properties are not copied to it.
• The audit form by itself cannot be imported. Either the main form by itself or both the main and audit forms can be imported.
• When the audit form is created for the first time, all fields (including non-data fields) are created. After that, if non-data fields are added to the main form, they are not added to the audit form.

Audit form fields

The data fields in the main form and the audit form have identical field permissions and field limits. However, you cannot modify field permissions and limits on the audit form.

Each audit form contains the following audit-specific fields.

AR System does not create these fields as part of any view in the audit form, so you must add them to the view to use them. (In Developer Studio, open the audit form, and select Form > Add/Remove Fields On View.)

The owner of the non-core fields on the audit form (form style) is set to the owner of the audit form, not the original form.

Scenarios

The following scenarios help you understand the changes that apply to the audit form fields when the main form is modified.