CMDB Data Manager Policies not working

mpmacconnell
Tera Guru

‎05-06-2024 02:54 PM

I created a bunch of CMDB Data Manager policies in our Dev Instance using the CMDB Workspace. I then moved them up via Update Set. The first thing I noticed in our Test and Stage instances are that they do not show in the CMDB Workspace. But when I navigate to the CMDB Data Manager in the standard UI I see that they are all listed as Imported. So I go into them and save them. Once doing that they now show in the CMDB Workspace.

 

My problem now is that I am seeing all kinds of issues with these "imported" polices. When I view them I get a pop-up that says "There are multiple enforced retirement definitions that affect this policy. When the policy is evaluated the number of affected records and tasks may be different". But when I check the retirement policies, there is only one listed for that table.

 

Also, when the job runs it never generates the CMDBTask so the archive never starts. Here is what I see when I try to view the policy. But when they were created new in Development and Sandbox I never had this issue. It is only for the ones that were moved up via update set. I have tried to delete one and recreate it, but see the multiple enforce retirement definiations message.

 

mpmacconnell_0-1715032395353.png

 

Anyone have any ideas how to resolve this?

0 Helpfuls
  • 2,666 Views
3 REPLIES 3

mpmacconnell
Tera Guru

‎06-19-2024 08:27 AM

What I found is that you publish the imported policies in the standard UI, not the workspace. Doing that they work fine and show properly in the CMDB Workspace. Sees to me that the workspace is still needs some work to help with these situations. The policies are being published in Development in the workspace, but when moving them up via update sets they need to be published under the CMDB Data Manager UI instead.

 

Maybe there is a better way of moving these policies but it is not noted in the docs anywhere that I can see.

Steven B
Tera Contributor

‎10-14-2024 03:02 PM - edited ‎10-14-2024 03:03 PM

If you are still having the issue with not seeing them, it's a known error in this KB:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1647869

 

There is a related record that doesn't get captured in an update set. Per the article "The workaround is to manually export the generated cmdb_data_management_policy_runtime_attributes records and import to the destination instance."