Table of contents
Explore what's new in the Extensible TraceLink Transfer, solution version 8.3.0 release. To learn more about the Extensible TraceLink Transfer, version 2026.2.0 app that powers the solution, see
Release information
This document describes the TraceLink capabilities included in the Extensible TraceLink Transfer, solution version 8.3.0 release, which is available on Validation and Production on 16 Jul 2026.
The following solutions are impacted by this release and will be updated to the version listed:
- Extensible TraceLink Transfer, solution version 8.3.0
Apps that support this solution version:
- Extensible TraceLink Transfer, version 2026.2.0
These release notes are subject to change based on the deployment of the release. In the event of changes, the release notes and any related documentation will be updated within one week of release deployment. Deployment completion can be confirmed in the TraceLink Release Notice email.
Patch releases
The following patch is released for this version:
- Extensible TraceLink Transfer, solution version 8.3.0 (minor release) is available on Validation and Production on 16 Jul 2026.
- Extensible TraceLink Transfer, solution version 8.2.0 (minor release) is available on Validation and Production on 19 Feb 2026.
- Extensible TraceLink Transfer, solution version 8.1.0 (minor release) is available on Validation and Production on 22 Nov 2025.
The patch is cumulative, and the most recent patch release includes functionality from all previous versions.
Revisions
| Date | Revision | Description |
|---|---|---|
| 06 Sep 2025 | 01 | Initial version.
|
| 22 Nov 2025 | 02 | The following updates have been made since the previous revision was distributed:
|
| 19 Feb 2026 | 03 | The following updates have been made since the previous revision was distributed:
|
| 16 Jul 2026 | 04 | The following updates have been made since the previous revision was distributed:
|
UI features
Extensible TraceLink Transfer, solution version 8.3.0
Delivery Confirmation for Outbound Messages via Functional Acknowledgments
Extensible TraceLink Transfer (XTT) version 2026.2.0 introduces the Wait for recipient Functional Acknowledgment before responding? option, which allows you to control when TraceLink returns the final status for an outbound message (such as a Purchase Order).
-
If the Yes option is selected (default timeout is 24 hours) – TraceLink waits for the recipient's Functional Acknowledgment before sending a response to your business application. For X12, TraceLink waits for a correlated 997, and for EDIFACT, it waits for a correlated CONTRL. During this time, the outbound message remains in the Processing state, and the corresponding Functional Acknowledgment record is displayed with the status Pending acknowledgment from the receiving partner. If a valid Functional Acknowledgment is received within this period, TraceLink returns a success response. If the acknowledgment indicates an error, the response reflects the failure. If no Functional Acknowledgment is received within 24 hours, the outbound message times out.
-
If the No option is selected – TraceLink returns a response as soon as the outbound transaction completes based on the connection's delivery confirmation, such as an AS2 MDN or successful delivery to the SFTP server, without waiting for a Functional Acknowledgment.
For more information, see and .
Impact analysis
- Interface options:
- Web UI
- Business segment impacts:
- All business segments for both Owners and Partners
Extensible TraceLink Transfer, solution version 8.2.0
Reprocess Failed or In Progress B2B Messages
The Extensible TraceLink Transfer, version 2026.1.0 introduces the Reprocess button that allow Application Administrators to reprocess failed or in progress inbound B2B messages directly from the View B2B Message screen received via AS2, SMTP, and SFTP connections.
Previously, there was no dedicated process and the reprocessing was done manually by the support team. This new feature introduces a controlled, UI- driven, and auditable way to reprocess inbound B2B messages improving traceability, reducing delays, and minimizing manual effort.
The Reprocess button will appear enabled for failed or in progress messages, and disabled for a successful message. Administrators can make multiple reprocess attempts, including for messages that were already reprocessed but failed again. If a reprocessing attempt fails, XTT treats it as a new failed execution while preserving the original failure details.
Impact analysis
- Interface options:
- Web UI
- Business segment impacts:
- All business segments for both Owners and Partners
Extensible TraceLink Transfer, solution version 8.1.0
Next Generation UI Enhancements for SMTP B2B Connection
With this release, a Next Generation User Interface (UI) has been introduced for the SMTP B2B connection. This upgrade enhances layout, navigation, and user experience to ensure a more streamlined workflow across multiple TraceLink networks and next-generation digital solutions.
As a result of these updates, the B2B connection screen has been redesigned to align with the new OPUS UI standards. While all existing functional capabilities remain intact, the interface now provides:
-
Enhanced configuration accessibility
-
Smoother integration with network-level components
Impact analysis
- Interface options:
- Web UI
- Business segment impacts:
- All business segments for both Owners and Partners.
Support Functional Acknowledgments at the Functional Group Level for X12 Choreography
A functional acknowledgment in Electronic Data Interchange (EDI) confirms the receipt and syntactic validity of an EDI transaction. In this release, during an AS2 or SFTP connection, an X12 EDI batch organizes transactions into functional groups by type. As a result of this update, a new UI element drop-down is added to support the functionality. For more information, see .
Impact analysis
- Interface options:
- Web UI
- Business segment impacts:
- All business segments for both Owners and Partners.
Enable Dynamic Data Mapping to Resolve Message Type with Transforms
This feature enables Application Owners to automatically determine the correct message type for inbound EDI documents, such as X12 850 or EDIFACT ORDERS. The Sender (Owner or Partner) of the B2B message can configure transforms that select the appropriate transaction type based on message content or Partner rules, reducing manual setup and improving transaction visibility. As a result of this update, a new UI element , Original Message Type, is added in the General section of each B2B Message. For more information, see .
Impact analysis
- Interface options:
- Web UI
- Business segment impacts:
- All business segments for both Owners and Partners.
Extensible TraceLink Transfer, solution version 8.0.0
The following new or updated functionality is included in this release.
Next Generation UI Enhancements for Extensible TraceLink Transfer
The Extensible TraceLink Transfer (XTT), solution version 8.0.0 introduces an updated UI enabled by TraceLink's OPUS Ensemble release, which provides an improved layout and navigation system that simplifies the user’s journey.
As a result of these updates, the and screens are updated. Additionally, all existing functionality is preserved, but has been updated and reconfigured to integrate with the platform capabilities enabled by the Opus Ensemble release.
Impact analysis
- Interface options:
- Web UI
- Business segment impacts:
- All business segments for both Owners and Partners.
Resolved issues
Extensible TraceLink Transfer, solution version 8.3.0
The following issues are resolved in this release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.
| ID | Interface | Issue Description |
|---|---|---|
| TL-105787: SMTP B2B Connections Update Without Creating Duplicates | Web UI | Previously, editing the name of an existing SMTP B2B connection created a duplicate connection instead of updating the original. Now, editing an existing SMTP B2B connection updates the original connection without creating duplicate entries. This issue is resolved. |
Extensible TraceLink Transfer, solution version 8.2.0
There are no resolved issues in this release.
Extensible TraceLink Transfer, solution version 8.1.0
There are no resolved issues in this release.
Extensible TraceLink Transfer, solution version 8.0.0
The following issues are resolved in this release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.
| ID | Interface | Issue Description |
|---|---|---|
| TL-61980:Inbound Delivery Option Now Displayed on B2B Message Details Screen | Web UI | Inbound delivery option is a method of delivery for the message from the sender to the receiver. This option is now displayed on the B2B Message Details screen. For more information, see . This issue is resolved. |
| TL-68900:AS2 IDs Are Case-sensitive | Web UI | AS2 IDs are case-sensitive, can include all printable ASCII characters, and must comply with the requirements in RFC 4130. This issue is resolved. |
Known issues
Extensible TraceLink Transfer, solution version 8.3.0
There are no resolved issues in this release.
Extensible TraceLink Transfer, solution version 8.2.0
There are no resolved issues in this release.
Extensible TraceLink Transfer, solution version 8.1.0
There are no resolved issues in this release.
Extensible TraceLink Transfer, solution version 8.0.0
There are no known issues in this release.