Asset Tag automation by cloud discovery

[Ankur Khanna]

Hi,

As part of cloud discovery- we are getting VM instance, VM storage, disk, NIC & other cloud resources getting discovered with the same Server's name or prefix Server name. We do not want these cloud resources to be visible on Incident or Change form to avoid confusion. We are thinking if we can automate the process of populating the Asset tag field for our cloud resources to "Cloud Discovery", (when/after cloud discovery runs Asset Tag field for these resources should update automatically) then we can exempt them from the Incident or Change form. Please let me if this can be automated or else help me with any other way of restricting these resources from the Incident/Change form.

[CMDB Whisperer]

Do not use the Asset Tag field for this.  Asset Tag is a field that is supposed to be unique identifier for a company's financial assets, not to just hold arbitrary labels or descriptions of CIs.

It sounds like the real problem you are trying to solve here is that you are not using reference qualifiers on your incident and change forms to filter out certain classes of CIs.  You should use the "Principal Class" checkbox on the CI Class Manager to select only the CI Classes that should be allowed to be managed as CIs in your Incident and Change processes.  There is a reference qualifier available out-of-box that will automatically filter your CIs to exclude classes of CIs that you are not interested in managing as CIs for those processes.  And if that decision changes down the road, just change one check box to tell ServiceNow to include that CI Class.  To see how this works see the Script Include called TaskUtilsSNC and look for the function getConfigurationItemFilter().  To use this on a CI field on the task, change the reference qualifier on that field to: