Loading...
Loading...
If a user has more than 1 data manager policy, deleting the policy from the list page by using the Delete list action will sometimes delete the wrong policy.
Pre-requisites: Activate the plugin "com.snc.cmdb.csdm.activation" 1) Hop/Login to any San Diego instance and go to /cmdb_data_manager_policy_and_attributes_list.do 2) create two (2) new records using the new button with following a) ABC Policy b) XYZ Policy 3) now go back to list view, and sort by Name (A-Z). Ensure, ABC Policy appears at the top of the list and XYZ Policy at the bottom. 4) Check the checkbox for XYZ policy and click on "Delete" Expected: XYZ Policy should be deleted Actual: No action happens most of the time (XYZ Policy is not deleted) and instead ABC Policy gets deleted. Inspecting the browser debug, or ajax transaction parameters in the localhost app node logs, shows the wrong sys_id can sometimes be passed. This is the global list choice delete action that got triggered - /sys_ui_action.do?sys_id=75a1fcce0a0a0b3400d6ed99cf8a87e0
This problem has been fixed. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to. cmdb_data_manager_policy_and_attributes is actually a Database View, which Joins the CMDB Data Manager Policy and Runtime Attributes tables. It is not a Table. If you must delete a policy, then it may be safer to delete them from the individual tables that make up the policy: cmdb_data_management_policy cmdb_data_management_policy_runtime_attributes Filtering the list down to 1 record only first, and then selecting it for delete, should also avoid this problem.
PRB1609531
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.