All,

Some minor improvements and changes have been made to Build-Tracker. These changes will go live Friday morning (2/2/18).

Person Interviewed Field:

Interviews will now include a “Person Interviewed” field for situations where the person interviewed is not the customer who will  be using the machine. A checkbox has been provided to autofill this information in the event that the person interviewed is the customer.

Improved Ticket Updates:

Build steps that prompt to update the ticket will now autopopulate information where applicable. In particular, the “Checkoff Complete” template triggered by the last step in the build has been revamped to display much more information without requiring a manual ticket update. (Note: Tickets will still need to be updated from TDx for placement scheduling, etc.)

Inactive Interviews:

Interviews with a completed build will now automatically be marked as inactive and won’t display in the interview list unless the “Show Inactive” switch is enabled.

All,

An update will be pushed to Reftool tonight that changes the way ticket creation buttons are displayed. Previously, all service requests were grouped under a button labeled as “New Ticket (IT)”. This button has been changed to say “Service Requests”, with additional buttons for “Major Problem (Outage)” and “Incident”.

Additionally, a count of users non-closed tickets will be displayed to the left of the Ticket History button and will link to the TD Tickets panel (located at the bottom of the page). Note that the counter may momentarily display “0” as the users tickets are retrieved from the TeamDynamix API.

Template Hub and the Reftool Template Editor will be retired on Wednesday, December 27th. While most templates have been moved to TeamDynamix, there may be a few that still need to be moved over. Please ensure that all necessary templates are moved over prior to the retirement date. Additionally, please remove the Template Hub browser extension, as it will cease to function after this date.

Thank you!

Reftool now allows for searching a variety of mail relay mapping files. This feature replaces a similar function that used to be part of tools.nws, and should make troubleshooting a bit easier in situations where a mailbox is receiving email sent to an address that Exchange/etc. doesn’t indicate it should be sent to.

To search the relay mappings, change the search type to “Mail Routing” and enter an email address or partial email address (e.g., jane.doe@lifetime.oregonstate.edu).

The returned results will indicate which relay mapping file they are found in as well as a short description for each file.

Relay Mapping Files:

relay-recipients-exchange: Addresses that get sent to Exchange “as-is”.

relay-recipients-onid: ONID addresses generated from the Banner ONID account feed

virtualusers.google: Google virtual user mappings

virtualusers.orst: Static @orst.edu mappings

virtualusers.exchange: Mappings to Exchange that are translated to a relay address

virtualusers.lifetime: Lifetime aliases

virtualusers.other: Various other aliases