Toggled at the project level in the administrative tools window, the Enable / Disable Audit Logs commands toggle whether or not to maintain a basic textual log of all changes made to an element. These are stored in a read-only auditLog attribute on the secondary tab of the property sheet for all elements. Combined with the highly detailed attribute versioning and the project comparison reports, audit logs provide insight into the evolution of an element.
If audit logging is enabled for a project, commands at the element, category, package, and project level enable you to clear audit logs. Clearing the audit log requires element administrator privileges and enters a corresponding entry in the audit log history.
 |
Audit logging is often not appropriate at the very start of a project, but as the project matures and controlled evolution becomes appropriate, audit logging should be enabled. |
| |
Audit logs are limited to 30KB per attribute. When an audit log exceeds this size, it is automatically trimmed to 16KB. This maintains visibility into the change history of the element while balancing database growth for those project teams using automated scripts that frequently revise / rebuild database content. |