---
title: Change Management integration with ITOM Visibility
description: If your organization is subscribed to ITOM Discovery or ITOM Visibility, integration with these ITOM products is automatically enabled. With this integration, any configuration item \(CI\) with an IP address that is part of a change request process can be maintained automatically. Change request fulfillers can also manually request the discovery process for a CI.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/change-management/change-mgmt-integ-wth-Discovery.html
release: australia
product: Change Management
classification: change-management
topic_type: concept
last_updated: "2026-03-12"
reading_time_minutes: 3
breadcrumb: [Change management integrations, Reference, Change Management, IT Service Management]
---

# Change Management integration with ITOM Visibility

If your organization is subscribed to ITOM Discovery or ITOM Visibility, integration with these ITOM products is automatically enabled. With this integration, any configuration item \(CI\) with an IP address that is part of a change request process can be maintained automatically. Change request fulfillers can also manually request the discovery process for a CI.

## Enabling integration

Depending on subscriptions purchased by your organization, you must install and configure the following plugins:

-   For ITOM Discovery - the Discovery plugin \(com.snc.discovery\)
-   For ITOM Visibility - the Discovery plugin \(com.snc.discovery\) and Service Mapping plugin \(com.snc.service-mapping\)

## Integration with ITOM Discovery

When Discovery is activated, Change Management exposes three new properties within the Change Properties module \(**Change Management** > **Administration** > **Change Properties**\):

<table id="table_jh5_w4s_jdb"><thead><tr><th>

Property

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Configures how discovery is triggered for Affected CIs \(automatically, manually or off\)

</td><td>

Determines whether to trigger discovery for the affected CIs automatically, manually, both, or not at all.Type: Choice list

 Values: Off, Both, Automatic, Manual

 Default value: Off

 **Note:** If the property below is set to Both, and you trigger discovery manually, then the automatic discovery will not be triggered for that change request.

</td></tr><tr><td>

List of Change Request states \(comma-separated\) where discovery can be triggered manually

</td><td>

Defines the change request state values to allow discovery to be manually initiated. For these defined state values, the Initiate Discovery related link is available.Type: String

 Default value: Implement, Review

 **Note:** If there are multiple languages used on the instance, then this property needs to be set to the internal state value for Review.

</td></tr><tr><td>

List of Change Request states \(comma-separated\) where discovery triggers automatically. E.g. when the Change Request's state changes to Review

</td><td>

Defines the change request state values for which discovery is automatically triggered. Discovery initiates when transitioning to the state values listed.Type: String

 Default values: Review

 **Note:** If there are multiple languages used on the instance, then this property needs to be set to the internal state value for Review.

</td></tr></tbody>
</table>**Note:** For the last two properties in the above table, if there are multiple languages used on the instance, then the property needs to be set to the internal value, which is 0, for Review.

In addition to the new properties, the **Discovery State** and the **Discovery last updated** fields get added to the **Affected CI** related list. **Discovery State** provides one of five status values and a corresponding icon to reflect that status:

-   In Progress
-   Completed Successfully
-   Completed w/Warning
-   Completed w/Error
-   Cancelled

The Discovery State value is presented as a link to the corresponding Discovery log file. The **Discovery last updated** field contains a date and time stamp indicating the last time Discovery was executed.

If you have opted to manually initiate the Discovery module, or opted for both manual and automatic initiation, then the **Initiate Discovery** related link appears in the Related Links section when the state of the change request matches one of the defined states in the property. When Discovery is triggered, the values in the **Discovery State** and the **Discovery last updated** fields change.

\[Omitted image "cm-integration-discovery"\] Alt text: change management integration with discovery

## Integration with ITOM Visibility

You can view the changes in the context of application services. Service maps available in Service Mapping show changes to an application service as a whole and to the individual configuration items \(CIs\) comprising the service.

If the ServiceNow AI Platform is configured to validate changes, all changes are evaluated and rendered as valid or not. If a change is valid, its change record on the service instance map is marked as approved. For more information about configuring the platform for change validation, see [Managing proposed changes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_ProposedChanges.md).

The type of change mark depends on the nature of changes that it represents:

-   **Light gray balloon \(\[Omitted image "ChangeHistoryBalloonsLightGray.png"\] Alt text: Light grey balloon icon\)**

    Unapproved change that does not influence the service instance behavior. For example, a change in a network path or adding a node to a cluster.

-   **Dark gray balloon \(\[Omitted image "ChangeHistoryBalloonsDarkGray.png"\] Alt text: Dark gray balloon icon\)**

    Unapproved change that changes the service instance behavior.

-   **Green balloon \(\[Omitted image "ChangeHistoryBalloonsGreen.png"\] Alt text: Green balloon icon\)**

    An approved change in deployments where the ServiceNow AI Platform is configured to validate changes.

-   **Double balloon \(\[Omitted image "ChangeHistoryBalloonsDouble.png"\] Alt text: Green balloon icon\)**

    Multiple separate changes that happened a short time from each other.


**Parent Topic:**[Change management integrations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/change-mgmt-integrations.md)

**Related topics**  


[Discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-operations-management/r-discovery.md)

[View the change history of application services](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-operations-management/t_ViewCIChanges.md)

[View the change history of application services in Agent Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-operations-management/workspace-view-history-app-service.md)