This documentation supports the 20.02 version of BMC CMDB.

To view an earlier version, select the version from the Product version menu.

Audit types and options in classes

You can keep a history of changes to instance data, which is called auditing. You enable auditing on a per-class basis, and you select which attributes trigger an audit and which are written as a result. An audit is triggered when an instance is created or deleted or when the value of one or more selected attributes changes as the result of an instance being modified. The new value must be different from the existing value to trigger an audit. Copying the same attribute value does not trigger an audit. For example, during reconciliation, a merge activity replaces the existing 348981 value for the SerialNumber attribute with 348981. This does not change the value and does not trigger an audit.

You can specify the following types of audit when modifying a class:

  • Copy — Creates a copy of each audited instance. When you enable Copy auditing for a class, each BMC Remedy AR System form pertaining to that class is duplicated to create audit forms that hold audited instances. This includes forms from superclasses, because they hold data for instances of their subclasses.
  • Log — Creates an entry in a log form that stores all attribute values from the audited instance in one field. When you enable Log auditing for a class, you specify the name of the log form to use. If this form does not already exist, it is created automatically. You can use the same log form with multiple classes.

Note

You cannot use Log auditing above Copy auditing in the inheritance tree. This means that if you already have Copy auditing enabled for a class, you cannot enable Log auditing for any of its superclasses, and if you already have Log auditing enabled for a class you cannot enable Copy auditing for any of its subclasses. This is due to the structure of audit forms. For more information about audit forms, see Types of auditing.

 Attribute audit options in classes

Using the following attribute audit options to specify which attributes trigger an audit and which are written during an audit:

  • None — Changes to this attribute do not trigger an audit. NULL is written to this field in the audit form in a Copy audit, and nothing is written to the Log field in a Log audit. This option is the default.
  • Audit — When the value of this attribute changes, an audit is triggered and the attribute value is written to the audit form or log form. When another attribute triggers an audit, this attribute is not written.
  • Copy — Changes to this attribute do not trigger an audit, but the attribute value is written to the audit form or log form when another attribute triggers an audit.
  • Audit & Copy — When the value of this attribute changes, an audit is triggered. This attribute value is written to the audit form or log form in any audit, regardless of whether its value changed.

As long as there is at least one Audit or Audit & Copy attribute for a class, a Create or Delete operation triggers an audit regardless of the values of such attributes. AuditCopy, and Audit & Copy attributes are all written during such an audit.

Related topics

Types of auditing (for detailed information about auditing, including recommendations)

Viewing instance history in BMC Atrium Explorer

Was this page helpful? Yes No Submitting... Thank you

Comments