Unintended Creation of Empty CI When "CI Not Listed" is Selected in Change Form
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago
Hi Folks,
We have identified an issue within the Change Management process where selecting "CI Not Listed" on the Change form triggers the expected task creation for the ServiceNow team. However, it also automatically creates a new Configuration Item (CI) named "Empty" with no associated information or attributes.
As part of our investigation, we have reviewed the relevant Business Rules, Client Scripts, UI Policies, Script Includes, and other configured scripts, but have not been able to identify the root cause responsible for the creation of this empty CI record.
Observed Behavior:
1.User selects "CI Not Listed" on a Change Request.
2.An unintended CI record named "Empty" is automatically created in the CMDB with no meaningful data.
Thanks in advance!