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 setup Set up an instance hierarchy

    Set up an instance hierarchy

    • 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

    Set up an instance hierarchy

    Set up an instance hierarchy that best supports your development life cycle.

    About this task

    This example demonstrates how to set up an instance hierarchy where several peer sub-development instances have the same parent development instance, but a more complex configuration may be required to handle multiple project teams or other customer requirements.

    Do not use Team Development with production or test instances.
    • Do not use a test or production instance as the parent instance in Team Development.
    • Do not make any instance the parent of a production instance.
    • Production instances should never have a parent.
    When you back out a change on a Team Development instance, it backs out the change all the way back down the chain, including undoing the work on the source instance. This behavior can cause major problems on test and production instances.

    Procedure

    1. Provision a parent development instance on the same software version, such as Dublin, as the target instance, such as production.
    2. [Recommended] Clone the production instance to the parent development instance.
    3. Provision sub-development instances on the same software version as the parent development instance.
    4. (Optional) Log in to the parent development instance and clone it to the sub-development instances.
    5. On each sub-development instance:
      1. Define remote instance connections to other instances in the hierarchy that this instance needs to push and pull with.
      2. Select the parent instance.
      3. Pull all changes from the parent instance.
      4. Grant access rights to appropriate developers.
      Team development process
    Related tasks
    • Create an exclusion policy
    • Define a remote instance
    • Enable a code review
    • Select the parent instance
    Related reference
    • Access rights for developers

    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

      Set up an instance hierarchy

      • 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

      Set up an instance hierarchy

      Set up an instance hierarchy that best supports your development life cycle.

      About this task

      This example demonstrates how to set up an instance hierarchy where several peer sub-development instances have the same parent development instance, but a more complex configuration may be required to handle multiple project teams or other customer requirements.

      Do not use Team Development with production or test instances.
      • Do not use a test or production instance as the parent instance in Team Development.
      • Do not make any instance the parent of a production instance.
      • Production instances should never have a parent.
      When you back out a change on a Team Development instance, it backs out the change all the way back down the chain, including undoing the work on the source instance. This behavior can cause major problems on test and production instances.

      Procedure

      1. Provision a parent development instance on the same software version, such as Dublin, as the target instance, such as production.
      2. [Recommended] Clone the production instance to the parent development instance.
      3. Provision sub-development instances on the same software version as the parent development instance.
      4. (Optional) Log in to the parent development instance and clone it to the sub-development instances.
      5. On each sub-development instance:
        1. Define remote instance connections to other instances in the hierarchy that this instance needs to push and pull with.
        2. Select the parent instance.
        3. Pull all changes from the parent instance.
        4. Grant access rights to appropriate developers.
        Team development process
      Related tasks
      • Create an exclusion policy
      • Define a remote instance
      • Enable a code review
      • Select the parent instance
      Related reference
      • Access rights for developers

      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