Overview
This article is designed to help Purdue IT to understand how to manage the Change processes in TDX.
To better understand the processes. terminology and work flow for Change Enablement, see "What is Change Enablement (Change Enablement Quick Reference Guide).
The videos below explain how to conduct Change Enablement in the TDX tool, including how to access the Change Enablement desktop, how to create and complete and RFC, and how to review and vote on an RFC.
How-to videos
To enlarge the videos below for better viewing, click on the "full screen" arrow buttons near the bottom left corner of each video. To view these videos outside of the knowledge base article, click here to watch in Kaltura Mediaspace.
Using Change Enablement Desktops in TDX
This video describes how to use the Change Enablement desktop in Team Dynamix and is intended for viewing by Purdue IT professionals.
Creating and completing an RFC in TDX
This video provides instruction for creating and completing an RFC in Team Dynamix and is intended for use by Purdue IT professionals.
Voting and Reviewing RFCs
This video provides instructions for reviewing and voting on RFCs in Team Dynamix and is intended for Purdue IT professionals.
FAQs for RFCs
Q: Why does the RFC workflow keep crashing?
A: If you do not select an Approval Authority in the change ticket, the workflow will loop and then crash. If you edit the RFC, enter an Approval Authority, save, and restart the workflow, then you should not get this error anymore. Please note that this Authorization section will not be available unless you select a Risk Level.
Q: Who should I select for Approval Authority?
A: Each Approval Authority is a different list of people who can approve an RFC. If the person creating/editing the RFC does not select the correct Approval Authority, then incorrect people may be notified. The dropdown of available Approval Authorities (CABs, Manager Approvals, etc.) changes based on the risk level of the RFC.
If you do not know the exact authority to select, please ask your manager for further information. If they do not know the exact group but do know a person who should be approving the change workflow, you may click on the "History" or "View Progress" options under the current workflow step. "History" will give you a table of all the workflow steps, including each approval authority and its members (members will be listed under the Details column for the relevant step). You can use the Find function (CTRL+F on Windows, Command+F on Mac, or using the browser actions menu) to search the steps that the person is part of. "View Progress" will show you the entire layout of the RFC workflow and allow you to click on each step for more information.
Q: How do I request an update to an Approval Authority?
A: If people need to be removed from or added to a list/Approval Authority, that team's director can submit a ticket to our team (currently IT_SE_SERVICE_MGMT) for that request. If the director is not the submitter/requestor, then they will need to be cc'd or otherwise added to the ticket for approval before we update the list.
Q: Why did IT Service Management reject the workflow?
A: The most common reason we reject a change ticket is if you do not enter a peer reviewer for an RFC. When a change ticket is routed to our team for peer review, we add an explanatory note and reject the workflow to restart its process. If you edit the RFC, enter a peer reviewer (using the magnifying glass to search if necessary), and save, then you should not have this issue anymore. You may need to restart/reassign the workflow depending on when you make this edit.
Still need help? Click the 'Purdue IT Request' button to start a ticket.