Contents Now Platform Custom Business Applications Previous Topic Next Topic Team Development setup Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Team Development setup To enable parallel development on multiple non-production instances, administrators can set up the Team Development instance hierarchy and grant access rights for developers. Access rights for developersTo use Team Development, application developers must have a set of credentials for each instance in the Team Development hierarchy.Create an exclusion policyApplication developers can create an exclusion policy to prevent pushes or pulls to particular instances in the team development hierarchy.Define a remote instanceFor each instance, define other instances in the hierarchy as remote instances.Enable a code reviewYou can require a code review of all changes pushed to an instance.Select the parent instanceAn instance can have multiple peer instances but only one parent instance.Set up an instance hierarchySet up an instance hierarchy that best supports your development life cycle.Related tasksTeam Development processRelated conceptsTeam Development overviewCode reviewsCode review notificationsCode review workflowExclusion policiesInstance hierarchiesPulls and pushesTeam Development rolesVersionsVersions and local changes On this page Send Feedback Previous Topic Next Topic
Team Development setup To enable parallel development on multiple non-production instances, administrators can set up the Team Development instance hierarchy and grant access rights for developers. Access rights for developersTo use Team Development, application developers must have a set of credentials for each instance in the Team Development hierarchy.Create an exclusion policyApplication developers can create an exclusion policy to prevent pushes or pulls to particular instances in the team development hierarchy.Define a remote instanceFor each instance, define other instances in the hierarchy as remote instances.Enable a code reviewYou can require a code review of all changes pushed to an instance.Select the parent instanceAn instance can have multiple peer instances but only one parent instance.Set up an instance hierarchySet up an instance hierarchy that best supports your development life cycle.Related tasksTeam Development processRelated conceptsTeam Development overviewCode reviewsCode review notificationsCode review workflowExclusion policiesInstance hierarchiesPulls and pushesTeam Development rolesVersionsVersions and local changes
Team Development setup To enable parallel development on multiple non-production instances, administrators can set up the Team Development instance hierarchy and grant access rights for developers. Access rights for developersTo use Team Development, application developers must have a set of credentials for each instance in the Team Development hierarchy.Create an exclusion policyApplication developers can create an exclusion policy to prevent pushes or pulls to particular instances in the team development hierarchy.Define a remote instanceFor each instance, define other instances in the hierarchy as remote instances.Enable a code reviewYou can require a code review of all changes pushed to an instance.Select the parent instanceAn instance can have multiple peer instances but only one parent instance.Set up an instance hierarchySet up an instance hierarchy that best supports your development life cycle.Related tasksTeam Development processRelated conceptsTeam Development overviewCode reviewsCode review notificationsCode review workflowExclusion policiesInstance hierarchiesPulls and pushesTeam Development rolesVersionsVersions and local changes
