Team dashboard
-
- UpdatedJan 30, 2025
- 3 minutes to read
- Yokohama
- Building applications
The team dashboard provides a central place to manage all Team Development activities on your development instance.
You can track local changes, pull and push changes between the local and parent instances, compare the local instance to other development instances, and resolve any collisions. You can also reconcile with the current parent instance or change the parent instance.
To access the dashboard, navigate to .
- Parent: indicates the status of the connection to the parent instance. If a problem or warning is detected, point to the indicator to view the error messages, or click the indicator to open the remote instance record.
- Change: changes the parent instance. See Changing the Parent Instance.
- Reconcile: compares the development instance to the parent instance. See Reconciling.
- Ready to Pull: indicates the number of changes on the parent that have not been pulled to the local instance.
- Pull: initiates a pull. See Pulling Versions.
- Push: opens a page that allows you to review the changes before a push. See Pushing Versions.
- Refresh: updates the status indicators on the control panel. The dashboard updates only when you reload or refresh the page.
- Local: indicates the status of the most recent comparison with another instance. If collisions are detected, click the indicator to open the list and resolve the collisions. See Resolve a collision in Team Development.
- Collisions: appears only if any local changes collide with versions pulled from the parent and indicates the number of collisions. Click the indicator to open the list and resolve the collisions. See Resolve a collision in Team Development.
- Compare to: allows you to select another development instance to compare with the local instance. See Comparing to Peer Instances.
- Ready to Push: indicates the number of local changes that are queued for the next push. See Queuing and Ignoring Local Changes.
- Local changes: indicates the number of local changes that have not been queued or ignored. Click the indicator to open a list of these changes.
- Ignored: appears only if any local changes are ignored and indicates the number of ignored changes. Click the indicator to open a list of these changes.
- Local changes: lists the local changes that have not been queued or ignored.
- Pushes and Pulls: provides a history of pushes and pulls. Expand a row to see the customized records for which versions were transferred as part of the push or pull.
- Instance Comparisons: provides a history of comparisons with other development instances.
- Collisions: lists the collisions that must be resolved before the next pull or push. You can right-click a row and select Resolve Collision. See Resolving Collisions.
- Ready to Push: lists the local changes that have been queued for the next push.
- Ignored: lists the local changes that are ignored for all pushes.
Related Content
- Using Team Development
Using team development within your instance to compare instances, push or pull record versions, or view the team development dashboard.
- 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.
- Pull exceptions
Pulling ignores versions when certain conditions occur.
- 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.
- Resolve multiple collisions
You can resolve multiple collisions without reviewing the differences between the local and pulled versions.
- 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.
- 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.
- Ignore a local change
Ignoring a local change prevents updates to a record from generating new versions in the Local Changes list.
- Back out a local change
Back out all local changes and restore the last version reconciled with the parent instance.
- 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.
- Approve or reject a push
Code reviewers must approve or reject a push from the Team Development application.
- 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.
- Cancel a code review request
Developers can cancel any push they submitted that is in the Awaiting Code Review stage.
- 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.
- Change the parent instance
If it becomes necessary to modify the instance hierarchy, you can change the parent for a development instance.
- 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.