Service Portal/TeamDynamix

Information and Self-Help articles relating to the Service Portal and working with TeamDynamix.

Categories (1)

Repository category for the style guide, templates, and appendices used within the UO Service Portal Knowledge Base application.

Articles (11)

Pinned Article Getting Started with the UO Service Portal

This article is intended to guide faculty, staff, and students through the basics of how to navigate the UO Service Portal.

Creating Child Tickets

Describes the steps in creating a child ticket for Tier 2 escalation.

Managing Desktops

This article describes how to manage your Desktops in the TeamDynamix TDNext application.

Redirection to Ticket Does not Occur

Attempting to access a TeamDynamix ticket from email does not redirect to the ticket.

Removing Sensitive Data from the UO Service Portal

If sensitive data such as FERPA, HIPAA, PCI, SSN, etc. information needs to be removed from a ticket, use the process outlined here.

UO Service Portal FAQs

These are some basic FAQs regarding The UO Service Portal. We will add answers to future FAQs as they come up!

UO Service Portal Technician Code of Conduct

UO Service Portal Code of Conduct for technicians.

Using TDX and Microsoft Teams

This article describes how to use the TeamDynamix (TDX) Teams integration as an end-user.

Which tool should I use for creating and publishing documentation?

The University of Oregon offers a couple documentation/wiki tools. Use the following information to help you determine which tool would be best suited for your documentation.

Working with Ticket Tasks

This article describes the difference between a ticket and a ticket task, when to use tickets versus ticket tasks, and how to work with ticket tasks.

Working with Workflows

Tickets can be configured to implement a workflow, which is an orchestrated, repeatable pattern of activities that walk a ticket through initial creation to completion. This article describes the workflow process and technicians responsibility when they are assigned a workflow activity.