Attestation Status showing as a line item in “Audit History (sys_history_line)“ of every CI

vamshi2 · 4 weeks ago

Please help me to understand Attestation Status showing as a line item in “Audit History (sys_history_line)“ of every CI ( Showing as Not yet reviewed)

lpruit2 · 4 weeks ago

Greetings,

Can you elaborate further on your question? At a high level, this field should be speaking to ServiceNow's CI Attestation functionality. If you navigate to the CMDB Workspace and have the necessary Role, you can create an Attestation Data Management policy. These Data Management policies generate CMDBTASK records for CI records. Once these CMDBTASK records are assigned, the assigned individual will "attest" to whether the CI record actually exists / still needed or not. If the CI is "Attested" the Attestation status is updated to "Attested". If the CI is "Rejected", the Attestation status is updated to "Rejected". I believe the default value is Not Yet Reviewed. I'll include some helpful links to ServiceNow documentation. I hope this information helps but please let me know if you have any additional questions.

Application service form

CIs attestation

View solution in original post

lpruit2 · 4 weeks ago

Greetings,

Can you elaborate further on your question? At a high level, this field should be speaking to ServiceNow's CI Attestation functionality. If you navigate to the CMDB Workspace and have the necessary Role, you can create an Attestation Data Management policy. These Data Management policies generate CMDBTASK records for CI records. Once these CMDBTASK records are assigned, the assigned individual will "attest" to whether the CI record actually exists / still needed or not. If the CI is "Attested" the Attestation status is updated to "Attested". If the CI is "Rejected", the Attestation status is updated to "Rejected". I believe the default value is Not Yet Reviewed. I'll include some helpful links to ServiceNow documentation. I hope this information helps but please let me know if you have any additional questions.

Application service form

CIs attestation

Me Being Mustaq · 4 weeks ago

Hi @vamshi2 ,

The Attestation Status showing as "Not yet reviewed" in the “Audit History (sys_history_line)” for every Configuration Item (CI) indicates that the attestation task for that CI has been created but not yet acted on by a responsible reviewer or owner. This status is part of ServiceNow CMDB’s attestation process, which helps validate that a CI exists and its data is accurate.

What Does "Not Yet Reviewed" Mean?

When CMDB Data Manager creates attestation tasks, it assigns CIs to users or groups for verification (attestation).
All CIs initially appear with the status Not yet reviewed, meaning no one has confirmed (attested), rejected, or excluded them yet.
As users process attestation tasks, the status changes to:
- Attested (confirmed)
- Rejected (cannot confirm existence/accuracy)
- Excluded (removed from attestation scope).
These transitions are recorded in the CMDB activity stream and the sys_history_line audit table for traceability. The line item helps you audit when and by whom each CI was reviewed, improving CMDB accountability.

Why Is It in sys_history_line?

The sys_history_line table shows when key CI fields change, including the Attestation Status field.
This helps you track governance and compliance, as you can see whether each CI was properly reviewed or remains pending.

Actions to Take

CIs with "Not yet reviewed" require user action in CMDB Workspace (My Work > Attestation Tasks).
Attest, reject, or exclude the CI based on its validity. The status will update and future history lines will show these changes for full audit tracking.
Periodic checks and completion of attestation tasks help maintain CMDB data quality.

In summary:
"Not yet reviewed" in Audit History means the CI is awaiting attestation by someone responsible, and serves as an audit record for CMDB governance.

You may find below thread helpful:

If it is helpful, please hit the thumbs button please mark the answer as correct based on the impact!!

Kind Regards,

Shaik Mohammed Mustaq

vamshi2 · 3 weeks ago

Hi @Me Being Mustaq Thanks for response

cmdb_data_management_task

i have verified above mentioned table but table is empty but still i can see Attestation status on each CI

so please could you explain briefly or could you please how can we replicate in PDI this will helpful much

thanks

Me Being Mustaq · 3 weeks ago

Hi @vamshi2 ,

The cmdb_data_management_task table stores CMDB Data Management tasks such as Attestation tasks, but if this table is empty in your instance, yet you still see Attestation Status on each CI, it indicates one of the following:

Why Attestation Status Shows Without Tasks in cmdb_data_management_task

Attestation Task Cleanup:
- Attestation tasks in cmdb_data_management_task are created for review and once completed or closed, they may be deleted or archived automatically based on cleanup jobs or retention policies.
- This means the table may be empty currently because tasks were completed in the past.
Attestation Status Field on CI:
- The Attestation Status on each CI is a field storing the latest attestation state (e.g., Not yet reviewed, Attested) but does not require an active task to display this status.
- The status is synced or updated as per attestation jobs and historical task records.
Background Jobs / Scheduled Jobs:
- Attestation process runs via scheduled jobs (like Data Manager run jobs) that create, assign, and update attestation tasks but do not keep them indefinitely.

To replicate attestation and see the functionality in PDI:

Activate Necessary Plugins:
- Ensure CMDB Data Manager and related Attestation plugins are activated (for example, com.snc.cmdb.datamanager).
Run Data Manager and Attestation Jobs:
- Go to Scheduled Jobs and find CMDB Data Manager run or Attestation Scheduler jobs and run them manually to trigger creation of attestation tasks.
Configure Attestation Setup:
- Set up attestation rules inside CMDB Data Manager > Attestation modules. Create policies or scopes defining which CIs need attestation and to whom they’re assigned.
Verify Attestation Tasks Creation:
- After running the jobs, check the cmdb_data_management_task table again for new attestation tasks assigned to users.
Use CMDB Workspace to Process Tasks:
- Navigate to CMDB Workspace > My Work > Attestation Tasks to see and process attestation tasks.

In short, Attestation Status on CIs is maintained independently and data management tasks are transient, created and cleared by scheduled jobs. For replication in PDI, activate plugins and run scheduled jobs to generate tasks and trigger attestation workflows properly

Attestation Status showing as a line item in “Audit History (sys_history_line)“ of every CI

Hi @vamshi2 ,

What Does "Not Yet Reviewed" Mean?

When CMDB Data Manager creates attestation tasks, it assigns CIs to users or groups for verification (attestation).​

All CIs initially appear with the status Not yet reviewed, meaning no one has confirmed (attested), rejected, or excluded them yet.​

As users process attestation tasks, the status changes to:

Attested (confirmed)

Rejected (cannot confirm existence/accuracy)

Excluded (removed from attestation scope).​

These transitions are recorded in the CMDB activity stream and the sys_history_line audit table for traceability. The line item helps you audit when and by whom each CI was reviewed, improving CMDB accountability.​

Why Is It in sys_history_line?

The sys_history_line table shows when key CI fields change, including the Attestation Status field.​

This helps you track governance and compliance, as you can see whether each CI was properly reviewed or remains pending.​

Actions to Take

CIs with "Not yet reviewed" require user action in CMDB Workspace (My Work > Attestation Tasks).​

Attest, reject, or exclude the CI based on its validity. The status will update and future history lines will show these changes for full audit tracking.

Periodic checks and completion of attestation tasks help maintain CMDB data quality.​

In summary:"Not yet reviewed" in Audit History means the CI is awaiting attestation by someone responsible, and serves as an audit record for CMDB governance.

You may find below thread helpful:

https://www.servicenow.com/community/itsm-forum/what-is-sys-history-line-will-contain/m-p/772195

https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/configuration-managem...

https://www.linkedin.com/pulse/mastering-cmdb-data-quality-servicenow-utility-telecom-mack-islam-2ps...

If it is helpful, please hit the thumbs button please mark the answer as correct based on the impact!!

Kind Regards,

Shaik Mohammed Mustaq

Hi @vamshi2 ,

The cmdb_data_management_task table stores CMDB Data Management tasks such as Attestation tasks, but if this table is empty in your instance, yet you still see Attestation Status on each CI, it indicates one of the following:

Why Attestation Status Shows Without Tasks in cmdb_data_management_task

Attestation Task Cleanup:

Attestation tasks in cmdb_data_management_task are created for review and once completed or closed, they may be deleted or archived automatically based on cleanup jobs or retention policies.

This means the table may be empty currently because tasks were completed in the past.

Attestation Status Field on CI:

The Attestation Status on each CI is a field storing the latest attestation state (e.g., Not yet reviewed, Attested) but does not require an active task to display this status.

The status is synced or updated as per attestation jobs and historical task records.

Background Jobs / Scheduled Jobs:

Attestation process runs via scheduled jobs (like Data Manager run jobs) that create, assign, and update attestation tasks but do not keep them indefinitely.​

To replicate attestation and see the functionality in PDI:

Activate Necessary Plugins:

Ensure CMDB Data Manager and related Attestation plugins are activated (for example, com.snc.cmdb.datamanager).

Run Data Manager and Attestation Jobs:

Go to Scheduled Jobs and find CMDB Data Manager run or Attestation Scheduler jobs and run them manually to trigger creation of attestation tasks.​

Configure Attestation Setup:

Set up attestation rules inside CMDB Data Manager > Attestation modules. Create policies or scopes defining which CIs need attestation and to whom they’re assigned.

Verify Attestation Tasks Creation:

After running the jobs, check the cmdb_data_management_task table again for new attestation tasks assigned to users.

Use CMDB Workspace to Process Tasks:

Navigate to CMDB Workspace > My Work > Attestation Tasks to see and process attestation tasks.

In short, Attestation Status on CIs is maintained independently and data management tasks are transient, created and cleared by scheduled jobs. For replication in PDI, activate plugins and run scheduled jobs to generate tasks and trigger attestation workflows properly

You may find below thread helpful:

https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/configuration-managem...

https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/configuration-manag...

If it is helpful, please hit the thumbs button please mark the answer as correct based on the impact!!

Kind Regards,

Shaik Mohammed Mustaq

When CMDB Data Manager creates attestation tasks, it assigns CIs to users or groups for verification (attestation).

All CIs initially appear with the status Not yet reviewed, meaning no one has confirmed (attested), rejected, or excluded them yet.

Excluded (removed from attestation scope).

These transitions are recorded in the CMDB activity stream and the sys_history_line audit table for traceability. The line item helps you audit when and by whom each CI was reviewed, improving CMDB accountability.

The sys_history_line table shows when key CI fields change, including the Attestation Status field.

This helps you track governance and compliance, as you can see whether each CI was properly reviewed or remains pending.

CIs with "Not yet reviewed" require user action in CMDB Workspace (My Work > Attestation Tasks).

Periodic checks and completion of attestation tasks help maintain CMDB data quality.

In summary:
"Not yet reviewed" in Audit History means the CI is awaiting attestation by someone responsible, and serves as an audit record for CMDB governance.

Attestation process runs via scheduled jobs (like Data Manager run jobs) that create, assign, and update attestation tasks but do not keep them indefinitely.

Go to Scheduled Jobs and find CMDB Data Manager run or Attestation Scheduler jobs and run them manually to trigger creation of attestation tasks.