- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 06-11-2024 11:08 PM
In this video tutorial, I delve into the process of enabling audits on a table within ServiceNow. I start by explaining the concept of table audits and their importance. Table audits serve as a crucial tool for tracking changes made to data over time. This functionality is invaluable for troubleshooting issues and ensuring data integrity.
Understanding Table Audits
Table audits allow us to monitor and record any alterations made to data. This feature is essential for maintaining data accuracy and integrity, providing a transparent history of changes that can be reviewed and analyzed. Whether it's for troubleshooting errors or preventing data tampering, audits play a pivotal role in effective data management.
Step-by-Step Guide to Enabling Audits
Step 1: Navigate to the Dictionary
First, I navigate to the dictionary and locate the specific table I want to audit.
Step 2: Open the Table Record
Once the table is found, I open the table record to access its settings.
Step 3: Enable the Audit Flag
Within the table record, there's a flag labeled "audit," which is set to false by default. I enable this audit flag and save the record.
Demonstrating the Audit Feature
To illustrate the functionality, I make a change to a user record's mobile number. After saving the change, I right-click on the record and select "History" to view the audit history. This confirms that the change has been tracked as intended.
Conclusion
In conclusion, enabling audits in ServiceNow is a straightforward process that significantly enhances data management. By tracking changes, we can ensure data integrity and prevent unauthorized modifications. Audits provide a clear, documented history of all alterations, making it easier to troubleshoot issues and maintain data accuracy.
- 2,740 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
It is recommended to only audit the fields that are necessary and avoid auditing fields that are frequently (or automatically) updated. Excessive table size can lead to various performance issues or monetary subscription implications.
Explanation of how to enable/disable auditing on a table or field:
How to exclude auditing on a field:
https://docs.servicenow.com/csh?topicname=t_ExcludeAFieldFromBeingAudited.html&version=latest
How to include auditing on a table:
https://docs.servicenow.com/csh?topicname=enable-whitelist-for-table.html&version=latest
How to include auditing on a field
https://docs.servicenow.com/csh?topicname=security-whitelist-audit-field.html&version=latest
Ways to disable audit deletes
- Tables with the prefix "sys_" get skipped by default unless they are in the "glide.ui.audit_deleted_tables" property. If a table starts with "sys_" and is not on the list, it is not audited.
- Tables with the "no_audit_delete" attribute on their table element in sys_dictionary. Every other deletion gets audited by default unless it is done with setWorkflow("false") or through a direct deletion API
Additional articles about data management
- (public) Mass-Deletion and Excess Data Management Recommendations - KB0717791
- Mastering Data Management in ServiceNow: from tracking growth to efficient cleanup - KB1518213
- Demystifying table rotation, extension, and table cleaner - Community Link

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Indeed, nowadays don't just go for enabling audit by checking the checkbox only... that's how we did things 10 years ago. Go for inclusion or exclusion.
Unfortunately a topic I have seen almost no customers/implementation partners do at all 😞