---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Fine-tune tracking changes for the change history

# Fine-tune tracking changes for the change history {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Define CI fields for which the system reflects changes in the change history for
application services. The change history view shows changes to CIs making up application
services as well as changes to application services themselves.

## Before you begin

Role required: admin

## About this task

Details about changes to a service instance and to its CIs are stored in the CMDB. Typically, these changes reflect adding or removing CIs from a service instance, upgrading or updating CIs, or modifying CI
configuration files. The system gathers this data by querying CMDB tables and then creating the change history view. In deployments where Service Mapping is activated, the type of change information Service Mapping queries depends on discovery patterns that Service Mapping uses to discover CIs.

Changes to configuration files are associated with CIs to which these files belong. Maps show configuration file changes as changes to related CIs.

## Procedure

1. Navigate to AllConfigurationExclusion List.  
   The Exclusion Lists list opens displaying records that the system uses to exclude changes from the change history view.
2. To make the system ignore changes to an extra field:
   1. Click New.
   2. Enter the CI class name in the Table Name field.  
      For example, enter <kbd class="ph userinput">cmdb_ci</kbd> for the Configuration Item \[cmdb_ci\] class.  
      Note:  
      The Service Mapping user interface refers to CI classes as CI types.
   3. Enter the name of the field you want to exclude in the Field Name field.  
      For example, enter <kbd class="ph userinput">work_notes</kbd> to exclude changes to the item work notes from the change history view.
   4. Select Submit.
   {#exclude-changes-from-change-history__substeps_zyf_3t5_d4b}
3. To make the system include previously ignored changes in the change history:
   1. Select the check boxes next to the relevant records.
   2. Select Delete from the Actions on selected rows list.
   {#exclude-changes-from-change-history__substeps_cwj_q2v_d4b}
**Related tasks**   

* [View the change history of application services in legacy Agent Workspace](https://servicenow-prod.fluidtopics.net/flIgBz_v8hUK7eTfNrNIaA "View changes made to a service instance and to the individual configuration items (CIs) comprising the service in Agent Workspace. You can also compare the service status before and after a certain change or problem. The change history is useful for maintenance, planning, or troubleshooting procedures.")
* [View the change history of application services in classic Service Mapping](https://servicenow-prod.fluidtopics.net/7KUinl4tyc2YyKqLg0fVSw "You can view the changes made to an application service as a whole and to the individual configuration items (CIs) comprising the service. Change history is useful for maintenance, planning, or troubleshooting procedures.")

*[\>]: and then