Best practice to safely disable Data Certification module (OOB) to prevent accidental triggers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hi everyone,
I am looking for advice on the best practice to safely disable or hide the legacy Data Certification module.
Recently, I encountered a situation where a user accidentally clicked the OOB UI Action "Create Certification Audit Instance" from an old record in the certification_audit_definition table. This inadvertently triggered a massive wave of certification tasks and notification emails to CI Owners.
Since this module is no longer actively used in the current process, I want to prevent this human error from happening again. What is the ServiceNow recommended approach to safely secure this OOB feature without causing skipped updates or conflicts during future family upgrades?
Should I simply set the OOB UI Action to Active = false?
- Should I deactivate the legacy records in the certification_audit_definition table?
Or is there a better practice (e.g., modifying ACLs or system properties) that I should follow?
Any advice or past experience with handling this would be highly appreciated. Thank you!