TDX 12.3 Update Release Notes and Resources

Summary

This page provides highlights and links to TDX resources regarding the TDX 12.3 update, scheduled to go live on Oct. 10, 2026.

Body

TeamDynamix is making some user interface changes in an upcoming update. This update is scheduled to go live in October 10th, 2026. This article will provide some helpful links and resources that can help you prepare for the update release and new user interface changes.

Links and resources:

Highlights of the 12.3 Update

Delegated Approvals

Client portal users and technicians can designate a delegated approver to review and approve items on their behalf while they are unavailable, and administrators can configure delegations directly for users with unexpected absences.

  • Users with the new Delegate Approvals permission can set a delegated approver from Client Portal > Service Requests > My Approvals or TDNext > My Work > My Approvals.
  • Administrators can view, create, and edit delegations from a new TDAdmin > Users and Roles > Delegated Approvals page.
  • Feed entries note when an approval was made "on behalf of" the original approver.
  • A new Delegated Workflow Step Responsibility column is available in the Tickets and Project Requests report sources.
  • The My Work > My Approvals filter previously labeled "Service Requests" is renamed to "Tickets."

Screenshot of the My Approvals page showing approvals delegated from another user

To learn more about Delegated Approvals, see Getting Started with Delegated Approvals. 
 

Move Workflow Steps to the client portal Ticket Detail page

In the client portal, workflow step actions are moved from the separate Current Workflow Step page to the Ticket Detail page, showing in a new Current Activities side panel, matching how workflow actions display in TDNext.

  • The same information and capabilities are available in the client portal, but consolidated into one view. 
  • The Current Workflow Step page is removed; hyperlinks to it (including from existing notification emails) automatically redirect to the Ticket Detail page, including when someone clicks that link after the workflow step has been removed.
  • The default Ticket Workflow Step Assignment and Ticket Workflow Step Reminder notification templates are updated to link to the ticket details page only. If your customized version of these templates still includes both links, you may want to update them to show one link.
     

Related Tickets

Technicians create relationships between tickets separate from the parent/child hierarchy, independent of the ticket's classification.

  • A new Related Tickets tab on the ticket detail page lists tickets related to the current ticket.
  • Relationships are non-hierarchical and aren't limited by ticket classification: a relationship shows the same way on both tickets.
  • Related tickets are reportable using new Related Ticket Count and Related Tickets columns.
     

New Report Editor

The report builder page has been rewritten, with the following new capabilities: 

  • Collapsible Report Sections - Each section of the report builder starts collapsed, with the ability to open the sections you need each time you edit a report. Information badges on the section headers preview the configuration inside the section. 
  • Reorder Filters - Filters can be reordered in a report without breaking any Advanced Filtering Expression you may have configured. 
  • Change Tracking & Undo/Redo - While editing the report, the editor keeps track of what changes you have made, shows which sections have changes, and allows you to undo/redo changes made to the report in this session.
  • Inline Preview - when building a report, the preview page will show what the report will look like. 
  • Rearranged Fields - Fields in report builder related to report results or charting are now grouped together. 
     

Ticket to Project Relationships

Project managers and team members can relate tickets to a project, issue, risk, or project task, so work tracked in a ticketing application stays visible from the related project item and vice versa.

  • New tabs or project sections sections are available on tickets, projects, project requests, issues, risks and tasks that show the relationship between tickets and project items. On projects and project requests you can see all tickets related to the project/request and its component items.
  • When creating a relationship to an issue, risk, or card wall task, users can optionally enable Close on Ticket Completion so the related item closes automatically when the ticket closes.
  • New columns are added to ticket and project report sources for reporting on ticket-to-PPM relationships.
  • A new ticketing application setting "Allow tickets from this application to be added to project-related items" controls whether an application's tickets can be related to PPM items; ticketing application administrators can disable this setting if tickets should not be related to projects.

Screenshot of the related tickets tab on a project showing a ticket related to a task and a ticket converted to a task.

To learn more, see Tracking Tickets in Projects.

​​​​Day 1 Impact: This feature is enabled by default. Ticketing application administrators can disable it at the application level, blocking tickets from certain applications from being added to projects. Project application administrators can limit use of this feature using the Add/Remove Related Tickets security role permission.

 

Non-Production Environments Settings

A new Non-Production Environments page in TDAdmin > Organization Settings consolidates settings that affect Sandbox and Release Preview environments.

  • Two existing settings are moved/copied into this page:
    • The non-production warning banner setting is moved from Organization Settings > Site Settings
    • The read-only Last Sandbox Refresh property is duplicated on this page (it is still available on the Export/Import Configurations page).
  • A new setting is added:
    • Admin Service Account target environments — Administrators can restrict a Production admin service account (API key) to specific child environments (Sandbox and/or Release Preview) from TDAdmin > Security. The Non-Production Environments page includes a read-only summary of which admin service accounts are available in each environment. Existing Admin Service Accounts will continue to be available in all environments unless this setting is configured. 

​​​​​​​Screenshot of the Non-Production Environments settings page

Details

Details

Article ID: 16883
Created
Fri 10/9/26 3:10 PM
Modified
Fri 10/9/26 4:11 PM