ServiceNow Paris Update – A key new feature that I found interesting about the CMDB

[joelcorey]

As part of my cohort and with the soon to release Paris update for ServiceNow, we were tasked with writing a blog post about key features that caught our attention. I found one feature in particular that really caught my eye: the Multisource CMDB. The Multisource CMDB tracks the history of every update to attribute values from every discovery source.

Using the new Multisource Configuration Management Database feature you can better track how the CMDB is populated by different discovery sources per Configuration Item. Use this feature to keep a complete history of discovery sources and planned values, and when values are updated have the Identification and Reconciliation Engine (IRE) select rules to choose a discovery source for the update. Lacking this feature, it is difficult to find the source of attribute value. Multisource CMDB holds the whole history of discovery sources and planned values that take part in updates of CI attributes. What all of this means is that with Multisource CMDB enabled, records are kept of all updates to attribute values from all discovery sources. Given these records and when a multiple discovery source tries to update a CI, configuration rules (reconciliation rules) select the proper discovery source.

This feature allows for better tracking of CI attribute values, discovery sources, and error correction should a fault be found. As someone new to the ServiceNow Community and being interested in the CMDB in general, I would be excited to know your unique insights in this area.

If you are looking for an admin, developer, or just want to connect please don't hesitate to reach out here: https://www.linkedin.com/in/joelcorey/