CMDB Data Certification: CMDB Workspace vs Legacy

[TrishP]

Hi All,

First of all, I miss the legacy Data Certification functionality, but, we must move on with the times.

In the legacy application, I was able to easily report on Failed attributes via the cert_element table, however, even though I can locate the Certification Tasks in cmdb_data_management_task, I am unable to locate an equivalent table in the Data Management version.
Would anyone know what that table would be?
Thanking you in advance,

Patricia

[Dr Atul G- LNG]

Hi @TrishP 

It seems the cert_element table is no longer available now. You can log a case — when I checked the docs, I couldn’t find anything related to this. Please log a now support case with team.

[AJ-TechTrek]

Hi @TrishP ,

Why It Feels Different based on the latest releases .

* In the legacy app, all failed attributes per certification run were stored in cert_element (easy to report directly).
* In the new CMDB Data Management (Yokohama & later), the model is different:
* Certification tasks live in cmdb_data_management_task.
* The per-attribute results are no longer in cert_element. Instead, they are logged as findings linked to each

certification task.

Where to Look in Latest Release
1. Certification Tasks
* Table: cmdb_data_management_task
* Holds one task per CI/Policy Execution.

2. Task Findings (Attributes Results)
* Table: cmdb_data_management_task_find (in recent releases this may appear as cmdb_data_mgmt_task_find or similar).
* Each record here represents the attribute checked, its expected vs actual state, and whether it passed or failed.
* Equivalent to the old cert_element table.

3. Policy Execution Tracking
* Table: cmdb_data_management_policy_execution
* Stores execution runs and links tasks back to a policy run (Policy Execution ID).

 How to Report Failures
* To replicate your old “Failed Attributes Report”, join:
* cmdb_data_management_task → cmdb_data_management_task_find
* Filter: status=Failed or result=non_compliant.
For example, you could create a report with:
* Task Number (from cmdb_data_management_task)
* CI (task.ci)
* Field Name (from task_find.attribute)
* Failure Reason/Value (from task_find.expected vs actual)

Recommendation
* Use cmdb_data_management_task_find as the modern equivalent of cert_element.
* Build your report/dashboard off that table.
* Optionally, create a Database View joining:
* cmdb_data_management_task + cmdb_data_management_task_find + cmdb_data_management_policy_execution
This will let you slice reports by policy, run ID, CI, and failed attributes.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025