Certification & Attestation Policies are not showing in CMDB Workspace when ported to new instance

[jimmillet]

Hi, We developed 5 Certification Policies in the CMBD Workspace (we're at Yokohama release), and these were captured in update sets in Dev instance. Next we loaded the update sets into Test instance, but when we go to the CMDB Workspace and drill down into Data Manager and go to the Policies tab, these policies do not display. When we go to sn_cmdb_ws_dm_certification_polic.list we DO see the 5 certification policies. So why aren't they being displayed in CMDB Workspace?

[wojasso]

Hi @jimmillet

Certification and attestation policies that you create in Data Manager are stored in the

sn_cmdb_ws_dm_certification_policy

table and are treated as application data. Update sets only capture metadata (UI policies, scripts, etc.), so the policy records themselves are not moved when you migrate an update set.

• Verify that the CMDB Workspace Data Manager and Data Certification plugins are installed and active on your target instance. The workspace filters out records if the necessary plugins are not present.
• Use a Configuration Data or Instance Data Replication transport mechanism to move the policy records between instances. You can create a configuration data rule for the policy table and export/import XML or use instance data replication to move them; update sets alone do not capture this data.
• After import, ensure the policies are Active and associated with the correct CMDB class and task type. The Policies tab in CMDB Workspace only shows active policies relevant to the current domain.
• If the records are present but still don’t appear, rebuild the Data Manager search index by navigating to Data Manager > Settings and clicking Rebuild Data Manager Index, or run the scheduled job

sn_cmdb_ws_dm_update_search_index

. This refreshes the index used by the Policies tab.

Once the policies exist on the target instance and the Data Manager index is up to date, they will appear under the Policies tab in CMDB Workspace.

🔥 Was this answer useful? 👉 If so, click 👍 Helpful 👍 or Accept as Solution ✅ 🔎🖥️🔧🙌

[AJ-TechTrek]

Hi @jimmillet ,

As per my Understanding your Problem summary is -

* You built 5 Certification Policies → captured in update sets → moved to Test.
* In Test:
* You see the policies in the table: sn_cmdb_ws_dm_certification_polic (good sign).
* But they don’t appear in the CMDB Workspace > Data Manager > Policies UI.
This usually means:
The records exist in the DB, but the Workspace UI doesn’t show them because of missing metadata, configuration, or data dependencies that were not included in the update set.

Solution as per my Understanding :-

Step 1: Check if policies are published
* Go to sn_cmdb_ws_dm_certification_polic.list.
* Verify:
* Column active is true.
* Column published or similar (depending on release) is set to true or matches expected state.
If they’re not published/active → CMDB Workspace UI will not show them.

Step 2: Check related data: Data Sets & Configurations
Certification Policies often reference:
* Data Sets
* Data Certification Templates
* Data Certification Schedules
* Other config records
If these records weren’t part of the update set, the policies appear in the table but are filtered out in the Workspace UI (because of missing related data).
What to do:
* Identify all related records:
* Data Sets (table: sn_cmdb_ws_dm_dataset)
* Templates, etc.
* Check if they exist in Test.
* If missing → migrate them from Dev.

Step 3: Validate filter conditions in CMDB Workspace UI
Sometimes the Workspace UI filters only show:
* Active & published policies
* Policies for specific Data Domains / Classes
* Policies where the user has the right roles (like cmdb_admin or cmdb_cert_admin)
Check the UI filters / list layout to confirm.

Step 4: Cache / index refresh
* In Test instance:
* Clear the cache (cache.do).
* Rebuild application indices: scripts.do?run=true&sysparm_script=GlideCacheManager.reloadAll();
* Log out & log back in.
Sometimes after import, the Workspace UI doesn’t pick up new data until cache refresh.

Step 5: Confirm update set completeness
Update sets sometimes:
* Miss application files (like UI Policies, Catalog UI Policies, Data Manager configurations).
* Miss ACLs, module definitions, and workspace configurations.
Compare Dev vs Test:
* Navigate to sys_update_xml.list filtered by your update set.
* Check if all related records moved.
If not → export those missing items into another update set and import.

Step 6: Check CMDB Workspace config / metadata
In App Engine Studio or Workspace Experience, ensure:
* The "Policies" tab in CMDB Workspace hasn’t been customized or filtered differently in Test.

Why this happens:
* CMDB Workspace UI is a dynamic workspace → it depends on related data (datasets, templates).
* Policies without valid references aren’t shown.
* Update sets can miss references outside the scope if not explicitly added.

Final checklist before retrying:


1. Policies active & published


2. Data Sets & related templates exist


3. Clear cache / reindex


4. Compare update sets for completeness

5. Check Workspace UI filters

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
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
ServiceNow Community MVP 2025

[jimmillet · Accepted solution]

Update...................................

I had trouble with both of the above replies. I could not find the columns and the tables specified. Today I opened a Case with ServiceNow support (CS8439214), and I got a quick answer that my scenario was a known problem (PRB1556476). Here was the answer I got in the case:
Issue:
Certification & Attestation Policies are not showing in CMDB Workspace when ported to new instance

Investigation Summary:
Upon further review, I was able to identify that the issue is that when creating and publishing a policy, the update set and sys_update_xml only capture the generated cmdb_data_management_policy record, but the cmdb_data_management_policy_runtime_attributes record will be missing from the update set.

Solution Proposed:
We have a known problem PRB1556476 for this issue, and this is being addressed and will be fixed in future releases.

The workaround is to manually export the generated cmdb_data_management_policy_runtime_attributes records and import them to the destination instance.

More information on this can be found in the KB below:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1647869