Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform App Engine
Table of Contents
Choose your release version
    Home Orlando Now Platform App Engine Now Platform App Engine Application tools Team Development Team Development overview

    Team Development overview

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Team Development overview

    Team Development allows developers to work on separate development instances while sharing code and resolving collisions throughout the development process.

    After setting up the instance hierarchy, you can develop changes on your local development instance. Use the team dashboard to manage Team Development activities, such as:
    • Tracking local changes and determining which changes to promote to the parent development instance.
    • Pulling changes from the parent instance and resolving any collisions with local changes.
    • Comparing your instance with other development instances and resolving any collisions with other development projects.
    • Pushing changes when a feature is tested and ready to promote to the parent development instance.

    Developers with admin access to their development instance and the parent instance can use team development. For alternative access settings, see Granting access rights to developers.

    • When to use Team Development

      Team Development allows multiple developers to work on applications.

    • Local changes

      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

      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

      Pulling ignores versions when certain conditions occur.

    • Team dashboard

      The team dashboard provides a central place to manage all Team Development activities on your development instance.

    • Approve or reject a push

      Code reviewers must approve or reject a push from the Team Development application.

    • Back out a local change

      Back out all local changes and restore the last version reconciled with the parent instance.

    • Cancel a code review request

      Developers can cancel any push they submitted that is in the Awaiting Code Review stage.

    • Change the parent instance

      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

      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

      Code reviewers can compare the pushed versions to the local versions to see the potential effect of incoming changes.

    • Compare to peer instances

      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

      Ignoring a local change prevents updates to a record from generating new versions in the Local Changes list.

    • Pull a version

      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

      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

      Application developers can back out a push to remove unwanted changes.

    • Queue a local change for a push

      Application developers can queue a local change for a push to ensure the changes are available to other developers.

    • Reconcile changes

      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

      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

      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

      You can resolve multiple collisions without reviewing the differences between the local and pulled versions.

    Related tasks
    • Team Development process
    • Set up an instance hierarchy
    Related concepts
    • Team Development setup
    • Code reviews
    • Code review notifications
    • Code review workflow
    • Exclusion policies
    • Instance hierarchies
    • Pulls and pushes
    • Team Development roles
    • Versions
    • Versions and local changes

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Team Development overview

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Team Development overview

      Team Development allows developers to work on separate development instances while sharing code and resolving collisions throughout the development process.

      After setting up the instance hierarchy, you can develop changes on your local development instance. Use the team dashboard to manage Team Development activities, such as:
      • Tracking local changes and determining which changes to promote to the parent development instance.
      • Pulling changes from the parent instance and resolving any collisions with local changes.
      • Comparing your instance with other development instances and resolving any collisions with other development projects.
      • Pushing changes when a feature is tested and ready to promote to the parent development instance.

      Developers with admin access to their development instance and the parent instance can use team development. For alternative access settings, see Granting access rights to developers.

      • When to use Team Development

        Team Development allows multiple developers to work on applications.

      • Local changes

        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

        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

        Pulling ignores versions when certain conditions occur.

      • Team dashboard

        The team dashboard provides a central place to manage all Team Development activities on your development instance.

      • Approve or reject a push

        Code reviewers must approve or reject a push from the Team Development application.

      • Back out a local change

        Back out all local changes and restore the last version reconciled with the parent instance.

      • Cancel a code review request

        Developers can cancel any push they submitted that is in the Awaiting Code Review stage.

      • Change the parent instance

        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

        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

        Code reviewers can compare the pushed versions to the local versions to see the potential effect of incoming changes.

      • Compare to peer instances

        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

        Ignoring a local change prevents updates to a record from generating new versions in the Local Changes list.

      • Pull a version

        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

        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

        Application developers can back out a push to remove unwanted changes.

      • Queue a local change for a push

        Application developers can queue a local change for a push to ensure the changes are available to other developers.

      • Reconcile changes

        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

        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

        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

        You can resolve multiple collisions without reviewing the differences between the local and pulled versions.

      Related tasks
      • Team Development process
      • Set up an instance hierarchy
      Related concepts
      • Team Development setup
      • Code reviews
      • Code review notifications
      • Code review workflow
      • Exclusion policies
      • Instance hierarchies
      • Pulls and pushes
      • Team Development roles
      • Versions
      • Versions and local changes

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login