Considerations for auditing forms

View and vendor forms

When vendor or view forms have form-style auditing, the audit form created is a regular form, which includes core fields. Therefore, you might have to provide default values for the Short Description and Submitter fields because they are required fields (for example, if you have workflow configured for the audit form).

Join forms

Both form-style and log-style auditing are available for join forms. An audit of a join form is triggered if the join form contains audit fields from the base forms and the audit qualification (if present) is TRUE.

Form style

For a form-style audit, the join forms' underlying forms must also be configured for form-style audit and must be enabled. BMC Remedy AR System creates the join forms' audit form as a join form of the underlying forms' audit forms and use the Audit Join Key fields in the join criteria, as shown in the following figure.

How a join audit form is created

After BMC Remedy AR System creates the audit join form, you can modify the join criteria for the audit form to add more qualifications.

The following figure illustrates how join-form audits work in join forms. If Join Form 2 satisfies the join audit criteria, an audit occurs for Forms A, B, and C (irrespective of A, B, and C's audit qualification), and audit records are visible by way of Audit Join Form 2.

If Join Form 2 fails the join audit criteria but Join Form 1 satisfies the audit criteria, an audit occurs for Forms A and B, and audit records are visible by way of Audit Join Form 1, but not Audit Join Form 2. If Form C has audit enabled, Form C is audited, and Audit Form C has entries, but audit data cannot be viewed from Audit Join Form 2.

In summary, for the first audited join form that passes the join audit criteria, BMC Remedy AR System generates a unique GUID and uses this GUID to update the Audit Join Key fields in this join form's underlying audit forms. Because the audit join form has a join criteria based on the Audit Join Key, the audit join form displays only data entered or modified in the corresponding audited join form. If the base forms of the join are modified directly, these base forms are audited, but the audit join form does not display the modifications because the value of the Audit Join Key fields is empty.

How a join form audit-style works with joins

Log style

For a log-style audit, a regular form is created and contains the special log-style audit fields.

Important

Data entered in the join form is copied to the log form regardless of whether any of that data is pushed to the underlying base forms. This means that the data captured in a log-style audit form might not reflect the content of the main form or its underlying base forms.

Changing field properties on the main form

When you modify the following properties of character fields on the main form, the BMC Remedy AR System server updates the audit form:

Attributes
Field limits
Help text

When you modify the following properties, the audit form is unchanged:

Entry mode
Display properties
Index for FTS
Permissions

Fields on audit forms are always read-only.

Distributed Server Option and audit forms

Important

The Distributed Server Option (DSO) is available only for on-premises deployments.

Distributed Server Option (DSO) works on audit and log forms, but the Transfer and Update flags are not updated.