---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Team Development

# Team Development {#ariaid-title1}

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

Team Development supports parallel development on multiple, non-production ServiceNow instances.  
Team Development provides the following features:

* Branching operations, including pushing and pulling record versions between instances.
* The ability to compare a development instance to other development instances.
* A central dashboard for all Team Development activities.
{#c_TeamDevelopment__ul_gmh_2x5_1q}
* **[When to use Team Development](https://www.servicenow.com/docs/Mqaj7OXmxqsW~pt2zbm2~g)**   
  Team Development allows multiple developers to work on applications.
* **[Local changes](https://www.servicenow.com/docs/ert2UWc2NtjLW4~bRCZQYA)**   
  The Local Changes table tracks which customized records have current versions that exist on the development instance but not on the parent instance.
* **[Local change lists](https://www.servicenow.com/docs/2tvWC86sQ380oZwBsFccIg)**   
  On the team dashboard, the Local Changes list shows the local changes that have not been queued for the next push or ignored for all pushes.
* **[Pull exceptions](https://www.servicenow.com/docs/yKzKNiPXZjzid_UnHYqSUQ)**   
  Pulling ignores versions when certain conditions occur.
* **[Team dashboard](https://www.servicenow.com/docs/9TnTLLXMlnsh1_a3EexQHw)**   
  The team dashboard provides a central place to manage all Team Development activities on your development instance.
* **[Approve or reject a push](https://www.servicenow.com/docs/mCFymDUskM_AARkyRx8ydQ)**   
  Code reviewers must approve or reject a push from the Team Development application.
* **[Back out a local change](https://www.servicenow.com/docs/ED2biqc0rY9CmIEkBd8Ecg)**   
  Back out all local changes and restore the last version reconciled with the parent instance.
* **[Cancel a code review request](https://www.servicenow.com/docs/Bnt3yowZdqPoYYQhl_wfSw)**   
  Developers can cancel any push they submitted that is in the Awaiting Code Review stage.
* **[Change the parent instance](https://www.servicenow.com/docs/M4GRiK88nU46q1pJ1~QK_g)**   
  If it becomes necessary to modify the instance hierarchy, you can change the parent for a development instance.
* **[Check the review status of a pushed change](https://www.servicenow.com/docs/m6bXrFYDDg2nqrlNd5SBqg)**   
  If the parent instance requires pushed changes to undergo code review, changes are placed in the Awaiting Code Review stage.
* **[Compare a pushed version to a local version](https://www.servicenow.com/docs/nQnfidZuo8kwLB6j_9IOgw)**   
  Code reviewers can compare the pushed versions to the local versions to see the potential effect of incoming changes.
* **[Compare to peer instances](https://www.servicenow.com/docs/MvYHfPHyCZyXnVXckQLcLg)**   
  You can compare the local instance to any other remote instance and commit any current versions from the remote instance on your development instance.
* **[Ignore a local change](https://www.servicenow.com/docs/dc9lh0r11kEhIPV8a9qLxA)**   
  Ignoring a local change prevents updates to a record from generating new versions in the Local Changes list.
* **[Pull a version](https://www.servicenow.com/docs/diUKUhkwnpFn2Sn5fuSv4A)**   
  Pulling retrieves versions of customized records from the parent instance and adds them on the development instance. Pulling does not retrieve any versions for changes made by system upgrades, but it retrieves all versions for changes made by users, not just the current version.
* **[Push a version](https://www.servicenow.com/docs/mwJGlSYOeysuepco8aeJTg)**   
  Pushing promotes changes from the development instance to the parent instance and commits the current version of a customized record on the development instance as the current version on the parent instance.
* **[Back out a push](https://www.servicenow.com/docs/CjqDB6kGRUSwZ5IqfgaNFg)**   
  Application developers can back out a push to remove unwanted changes.
* **[Queue a local change for a push](https://www.servicenow.com/docs/L_BB0eW_e4NsLCLlU6o7~Q)**   
  Application developers can queue a local change for a push to ensure the changes are available to other developers.
* **[Reconcile changes](https://www.servicenow.com/docs/4Rwtu23fd0TGj9Af2Id_HA)**   
  Reconciling first compares the local instance to the parent, and then generates the list of local changes and calculates the number of changes that are ready to pull from the parent.
* **[Resolve a collision in Team Development](https://www.servicenow.com/docs/rHCSjCvfuIgcZLrCC0FLlQ)**   
  A collision is detected when the pulled version and the current local version are modifications of a different version, indicating that someone else has modified the same record that you have modified. The team dashboard displays the number of collisions between the local and the parent instance.
* **[Limitations on updating records](https://www.servicenow.com/docs/y_fXYc0I80ZoMFMHxFgRRw)**   
  There are some types of records that you cannot merge while resolving differences on the Compare to Current and Resolve Collision pages.
* **[Resolve multiple collisions](https://www.servicenow.com/docs/69of0h9lzO0CXalOHternw)**   
  You can resolve multiple collisions without reviewing the differences between the local and pulled versions.