Best practices in implementing Unauthorized Change capability

[Ed Laar1]

Hi,

ServiceNow Discovery is able to discover changes in the infrastructure like new CI's installed or Changes in/on already existing CI's and update the CMDB accordingly.

As every CMDB update should formally be based on an approved change request ServiceNow Discovery has the Unauthorized Change capability. In this capability a CMDB update executed by Discovery is checked against the existence of an approved change request. When this is NOT the case an Unauthorized Change is created and send to a group for post implementation approval.

Does anybody have any experience in implementing this and willing to share these experiences?

Looking forward to them,

Ed

[Ed Laar1]

Hi Carl,

I was wondering if you could help as I am still trying to find out the setup of the unauthorized change capability:

About some properties: What does the property Change request query mean? The simple explanation following the system is: Include change requests that match a certain condition.

Explanation from the docs tells: Add the query conditions to define what change requests are valid and belong to the unauthorized change category. For example, you can add a condition to view all active change requests that are in the implement or review state for the given CI. If the conditions given are not met, then the change becomes an unauthorized change.

It seems there is a contradiction here: Changes following certain criteria are evaluated and if conditions are NOT met the changes becomes an unauthorized change.

What is this exactly: If a change on a CI property is seen a check is done if a certain CHG meeting the conditions is there and if not an unauthorized change is created?

Looking forward to your idea's,

Ed