View the change history of application services in classic Service Mapping
-
- UpdatedAug 3, 2023
- 5 minutes to read
- Vancouver
- Service Mapping
View the change history of application services in classic Service Mapping
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.
Before you begin
Role required: admin, sm_admin, sm_user, app_service_admin, or app_service_user
About this task
Details about changes to an application service and to its CIs are stored in the CMDB. Typically, these changes reflect adding or removing CIs from an application service, 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 application service as described in History Timeline.
If the Now 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 application service map is marked as approved. For more information about configuring the platform for change validation, see Managing proposed changes.

- Light gray balloon (
)
- Unapproved change that does not influence the application service behavior. For example, a change in a network path or adding a node to a cluster.
- Dark gray balloon (
)
- Unapproved change that changes the application service behavior.
- Green balloon (
)
- An approved change in deployments where the Now Platform is configured to validate changes.
- Double balloon (
)
- 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.
Procedure
Related Content
- Modify tracking changes in configuration files
Configure the system to collect information about changes in configuration files belonging to a configuration item (CI). Service Mapping uses this information to notify users that CI configuration files changed and to view actual changes to configuration files directly in the application service maps.
- View an application service map in base system
- Compare two versions of an application service in classic Service Mapping
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.
- Fine-tune tracking changes for the change history
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.