---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# View the change history of application services in classic Service Mapping

# View the change history of application services in classic
Service Mapping {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 Minuten Lesedauer

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.

## Vorbereitungen

Role required: sn_cmdb_admin, admin, service_mapping_admin, service_mapping_user, app_service_admin, or app_service_user

## Warum und wann dieser Vorgang ausgeführt wird

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.

While you can see change records for a specific CI in the context of application
services, you can also see detailed history of a specific CI separate from its service instance as described in [History Timeline](https://www.servicenow.com/docs/access?context=c_HistoryTimeline&version=australia&pubname=australia-platform-security&ft:locale=en-US).

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://servicenow-prod.fluidtopics.net/gXqx~p9109u4kWYJWlr1aQ#c_ProposedChanges "The proposed changes feature allows you to pre-configure changes to configuration items and their associated relationships. These pre-configured changes are prepared to be implemented, but do not actually happen until they are applied at a later time.").  
Changes to the service instance appear on the history timeline.   

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

Light gray balloon (![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 (![Dark gray balloon icon]())
:   Unapproved change that changes the service instance behavior.

Green balloon (![Green balloon icon]())
:   An approved change in deployments where the ServiceNow AI Platform is configured to validate changes.

Double balloon (![Green balloon icon]())
:   Multiple separate changes that happened a short time from each other.

You can mark times on the history scale by creating baselines to quickly return to
the marked view.

## Prozedur

1. Open the service instance map.
   1. Navigate to AllCSDMManage Technology Management ServicesService Instance. {#t_ViewCIChanges__NavigateCSDMManageTechServiceAppService}
   2. Select the needed service instance.
   3. On the service instance page, select View Map.
   {#t_ViewCIChanges__substeps_xxr_jpz_dmb} {#t_ViewCIChanges__Cmd_NavigateToAppServicesSM}
2. Review change records created for this service instance on the Changes tab at the bottom of the page.  
   If Service Mapping is deployed, then in Edit mode, the
   Discovery Messages section appears below the map.
3. On the history timeline, set the time range of changes that you want to view.

   | Option | Action |
   | To set the time range of the history timeline | Click the hour, day, week, or month icons. |
   | To increase or decrease the time range | Click the zoom in and zoom out icons. |
   | To change the upper limit on your history range | Click the history scale. ![Click the history scale to mark the time which serves as the upper limit.]() The time that serves as the upper limit appears above the history timeline. Hinweis: You cannot set the lower limit on your history range to a time before this service instance was created. This time is marked with the IT Service Created event on the history timeline. <br /> |
   |-|-|

   {#t_ViewCIChanges__choicetable_dnx_mtk_51b}  
   The map shows the history view of the service instance for the time you selected.  
   Hinweis:  
   The Change tab shows all change records, even the ones which are filtered out of the history view.
4. To mark a time on the time scale, set a baseline:
   1. Click the Compare icon.  

      <br />

   2. Navigate to the time you want to mark as a baseline on the history scale.
   3. Click Set baseline.  

      <br />

   4. Enter the name of the baseline and click OK.  
      The new baseline appears as a button above the history scale and as a blue flag on the history scale.  

      <br />

   {#t_ViewCIChanges__substeps_fl5_znh_nt}
5. View the change history.

   | Option | Action |
   | To see the CI responsible for a change record | Select a change record on the Changes tab. The related CI is marked yellow in the map. <br /> <br /> |
   | To see only change records related to a CI | Select the required CI or the connection on the map. The Changes tab displays only change records related to the selected CI or connection. <br /> <br /> |
   | To see the configuration file at the selected moment in the past | 1. Set the time on the history scale. 2. In the Properties pane, scroll to Tracked Configuration Files, and click the file name. The new tab opens displaying the content of the tracked configuration file at the selected time. {#t_ViewCIChanges__ol_czk_zfv_my} |
   | To see the network at the selected moment in the past | 1. Set the time on the history scale. 2. Right-click the connection and select Show network path. The new tab opens displaying the network or storage path map for the time you selected. {#t_ViewCIChanges__ol_hyq_c5q_s5} Hinweis: You cannot view the network path for connections marked as boundaries to this service instance. |
   |-|-|

   {#t_ViewCIChanges__choicetable_ky8_b2k_s5}
6. To exit the history view and see the current status of the service instance, click the current icon.  

   <br />

**Zugehörige Tasks**   

* [View an application service map in base system](https://servicenow-prod.fluidtopics.net/xv49RUA4MgEFgBbZxxA7tw "An application service map provides a visualization of data for the CIs comprising an application service, and the relationships and connections between these CIs.")
* [Compare two versions of an application service in classic Service Mapping](https://servicenow-prod.fluidtopics.net/xGPoEIanJ2iTiFML91mGpg "You can see a summary of application service changes at a glance by comparing two versions of an application service. This feature is useful for checking the application service status before and after a certain change or problem.")  
**Zugehörige Informationen**   

* [Modify tracking changes in configuration files](https://www.servicenow.com/docs/access?context=track-configuration-files&version=australia&pubname=australia-it-operations-management&ft:locale=en-US)
* [Fine-tune tracking changes for the change history](https://www.servicenow.com/docs/access?context=exclude-changes-from-change-history&version=australia&pubname=australia-it-operations-management&ft:locale=en-US)

