Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Normalizing business service names - Legacy

Log in to subscribe to topics and get notified when content changes.

Normalizing business service names - Legacy

The name of a business service used in an Application Profile Discovery environment or version file might not be an exact match for an existing business service name in the ServiceNowServiceNow CMDB.

For example, the creator of the environment file might define a business service as Management tools, but in the CMDB, that business service appears as Management tool (singular). This can occur if the administrators who manage profile Discovery and the CMDB fail to standardize the names. Discovery assumes that these are two separate business services and creates separate records, one for each version of the name. To eliminate duplication, normalize all business service names after running a new Application Profile Discovery.