Loading...
Loading...
This error is thrown when the eligible record count is zero for the filter condition for the policy. Steps to Reproduce 1. Create a policy. 2. Add a filter condition that results in zero record count. 3. Preview in the CMDB data manager and see error thrown. This error will also be thrown if there are ACLs blocking the user previewing the policy from accessing the records being queried. Workaround 1. Ensure there is no ACL blocking the user from the records being queried in the filter condition. 2. Ensure filter condition has at least one matching record. 3. The Customer would not be able to run the policy nightly without publishing it through UI. So first customer needs to publish the policy before running it nightly. Till this defect is not fixed, the customer can use the background script to publish the policy. They can write a script to update the "status"= "Published" for the record in cmdb_data_management_policy_runtime_attributes for a given policyId. //------- script to publish policy ---- var policyId = ''; // TODO: provide sys_id of policy from cmdb_data_management_policy table var gr = new GlideRecord('cmdb_data_management_policy_runtime_attributes'); gr.addQuery('policy', policyId); gr.query(); if(gr.next()) { gr.setValue('status', 'Published'); gr.update(); } //----------- end -------------- The error is handled in Xandu release.
PRB1711486
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.