- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2023 03:55 AM
What exactly is Data Certification vs CI Attestation? What are the use cases for- each of them? In which scenario which feature should be used?
Solved! Go to Solution.
- 10,957 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-13-2024 10:52 AM
Data Attestation focuses on data currency. You use Attestation to verify that a CI record represents a resources that still exists in your organization. If a CI record fails attestation (e.g. the resource it represents no longer exists) then it becomes a candidate for being retired and removed from the CMDB.
Data Certification focuses on data quality. Fields in records (in CMDB or non-CMDB tables) are reviewed for accuracy and can be updated, or marked as failed and subsequently updated with accurate values.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-24-2024 03:20 PM
i couldnt find any BR rule on the field ''attested'' either

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-28-2024 11:29 AM
There's no OOB flows or policies for dealing with CIs that have had their attestation_status set to Rejected. Because it's unlikely an OOB Data Manager policy for retiring CIs that failed attestation would align with every business requirement, we don't include one.
As it is, configuring a Data Manager retire policy is straightforward and you could for example, set a filter condition where a CI whose attestation_status is Rejected and the attested_date is more than 7 days ago would be retired.
You can then use either an archive or delete policy to remove the retired CI records from the CMDB.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-31-2024 11:17 PM
Hi Tony, one question on the archive/delete policy. If delete is used then it removes it completed from ServiceNow CMDB itself?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-01-2024 08:59 AM
That's correct - Delete policies will permanently remove retired records from the CMDB. Archive policies will archive records from the CMDB and retain them for the numbers of days specified in the glide.cmdb.data_manager.default_archive_time system property (120 days by default).
The sys_id's for archived or deleted CI records are recorded in a CSV file that gets attached to the Data Manager task record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-02-2024 08:50 AM
Thanks Tony.