Audit rules may keep track of activity in TeamConnect by logging information in history records. You may apply these rules to user actions that are relevant for record keeping or monitoring changes, such as when a user updates one or more system or custom fields in a record. Audit rules provide you with a way to define business rules through Designer rather than developing and testing custom code to record user activity.

Audit rules may create history records that include the name of the user performing an action and how the record was affected. For example, you may create an audit rule to track when a contact record's Social Security Number field is updated. When the rule is triggered, it records the old value, new value, and the user who made the change.

Recording information in history records allows you to control what is recorded and how it appears. For example, you may create a custom description for the event that triggers the audit rule, record information in custom fields, and export data for reporting purposes.

Points To Remember

Keep the following points in mind when creating audit rules:

•You may use audit rules to track modifications to data, and the creation or deletion of records.

•When an audit rule is triggered and its qualifiers are met, it creates one history record. To define audit rules that are triggered on Update, define qualifiers that only capture information when appropriate. Otherwise, a history record will be created whenever a user updates any part of a record.

•Rules with multiple triggers have the potential to execute more than once for a single event. If this happens with an audit rule, then multiple history records will be created.

•TeamConnect executes audit rules after all other business rules are applied. That way, operations that are prevented because of another rule will not cause the creation of an audit history record.

•The current user's access rights do not affect the creation of an audit history record. For example, even if the current user does not have rights to create related records in matters, the audit rule may still create a history record for the current matter record.

•If an audit rule is triggered but a history record cannot be created, for whatever reason, no additional information is logged, and no error is given to the user.

For information about the specific settings available in audit rules, see Defining Actions for Audit Rules.