Team dashboard

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Team dashboard

    The Team dashboard in ServiceNow provides a centralized interface to manage all Team Development activities within your development instance. It enables you to track, synchronize, and compare changes between your local instance and parent or peer development instances. The dashboard also helps identify and resolve version collisions, ensuring smooth collaboration across development teams.

    Show full answer Show less

    Access the dashboard by navigating to Team Development > Team Dashboard.

    Key Features

    • Control Panel Status Indicators and Actions:
      • Parent: Shows connection status to the parent instance with error messages and direct access to the remote instance record if issues arise.
      • Change: Allows changing the parent instance as needed.
      • Reconcile: Compares your development instance against the current parent instance to identify differences.
      • Ready to Pull: Displays the number of changes available on the parent instance that haven’t been pulled locally yet.
      • Pull: Initiates pulling changes from the parent instance.
      • Push: Opens a review page for local changes queued to be pushed to the parent.
      • Refresh: Updates all status indicators on the dashboard.
      • Local: Indicates the status of your last comparison with another instance and alerts to any collisions detected.
      • Collisions: Shows the count of local changes conflicting with parent changes; provides direct access to resolve these conflicts.
      • Compare to: Lets you select and compare your local instance with another development instance.
      • Ready to Push: Shows the number of local changes queued for pushing to the parent.
      • Local Changes: Lists new local changes not yet queued or ignored.
      • Ignored: Displays local changes marked to be ignored for pushes.
    • Change Tracking Lists:
      • Local Changes: Tracks all unqueued or unignored local modifications.
      • Pushes and Pulls: Shows the history of synchronization actions with details on transferred records.
      • Instance Comparisons: Logs comparisons between your local and other development instances.
      • Collisions: Lists conflicts requiring resolution before pushing or pulling further changes.
      • Ready to Push: Lists local changes staged for the next push.
      • Ignored: Lists changes excluded from pushes.

    Practical Benefits

    • Provides transparency into the status of your development instance’s synchronization with parent and peer instances.
    • Facilitates proactive conflict detection and resolution, reducing integration errors.
    • Enables controlled management of changes through queuing and ignoring options before pushing to the parent instance.
    • Supports auditing and tracking of all Team Development activities through detailed history lists.

    Next Steps

    • Use the dashboard regularly to monitor and manage your local and remote changes.
    • Resolve detected collisions promptly to maintain smooth synchronization.
    • Leverage the comparison and reconcile features to ensure your instance stays aligned with the parent or peer instances.
    • Consult related tasks such as pulling versions, pushing versions, queuing changes, and changing the parent instance for detailed operations.

    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 Team Development > Team Dashboard.

    Figure 1. Team dashboard
    Team dashboard
    The control panel in the top left provides status indicators and Team Development actions.
    • 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.
    The team dashboard includes lists for tracking local changes and viewing the history of Team Development activities.
    • 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.