---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Changesets and version control in CDM

# Changesets and version control in CDM {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
A changeset is a draft copy of an application that you can update and save as often as
needed. When you are satisfied with your changes, you can commit the changeset to apply the
changes to the application. Committing  
Important:  
Starting with the Washington D.C. release, DevOps Config is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported.

## About changesets {#cdm-changesets-version-control__section_by2_nrv_kqb}

To edit config data, you create a changeset and make changes in the changeset. You can perform the following actions:

* Create a new changeset: The changeset includes the full config dataset of the application.
* Save a changeset: The Editor panel, List view, and Preview panel refreshes to reflect the resolved state of the changeset. The system updates the changeset but does not update the application. Changes appear on the Activity tab. You must commit a changeset to update the config data for the application. After saving, you can move on to other activities and return later to edit the changeset.
* Update an existing changeset: Edit a changeset that had been saved but not committed.
* Commit a saved changeset: The system generates a snapshot of each deployable that is affected by the changes.
{#cdm-changesets-version-control__ul_xkl_tnr_spb}

## About conflicts with other changesets of the application that you are working
on {#cdm-changesets-version-control__section_tgn_bgx_kqb}

Sometimes, UserA and UserB are working at the same time on two different changesets of the
same application. If UserA commits a changeset that sets <var class="keyword varname">variableX</var> to
<kbd class="ph userinput">A</kbd> and later, UserB tries to commit a changeset with
<var class="keyword varname">variableX</var> set to <kbd class="ph userinput">B</kbd>, a conflict results.

An open changeset with conflicts is blocked---it cannot be committed. The system notifies you
of conflicts with a warning message on the page. In addition, the
State value in the header changes from Open
to Blocked.

See [Conflicts between changeset commits](https://servicenow-prod.fluidtopics.net/~B0dBjKROqD9hL~XXI0Emw "Service delivery can include multiple teams working at the same time on config data with potentially hundreds of configuration changes every day. Because changes can be in conflict with earlier changes by a different user, CDM manages commits and snapshots to block commits that conflict. You are notified of changeset conflicts to help you to resolve them.") for descriptions of the types of conflicts
that the system identifies.