Type = How Tos API Reference, Courses, Developer Guides, Developer Tools, Design Guides, Explainer Videos, FAQs, Fundamentals, Troubleshooting, Use Cases, What's New,; Topic = Opus Solution Environment, Multienterprise Information Network Tower, Administration, Transforms, Link Actions, Reports and Dashboards, Track and Trace, Compliance, Supply Chain Work Management, Developer Documentation, Opus Platform,;Persona = Solution Designer, TraceLink Administrator, User, Orchestration Architect, Solution Partner, Technology Partner,; Orchestration = Manufacturing, Logistics, Commerce, Transportation, Clinical Supply,; Function = Supply Chain, IT, Operations, Regulatory Affairs, Quality, Commercial, Pharmacy, Project Management, Finance, Spare 0, Spare 1, Spare 2, Spare 3, Spare 4, Spare 5, Spare 6, Spare 7, Spare 8, Spare 9, Spare 10,
What's new in the system
Explore what's new in the US Compliance, version 2025.2.0 release. To learn more about what's new in the US Compliance, solution version 10.0.0 that provides the user interface for this app, see
Release information
This document describes the TraceLink capabilities included in the US Compliance, version 2025.2.0 app release, which is available on Validation on 13 Sep 2025 and Production on 11 Oct 2025.
The following apps are impacted by this release and will be updated to the version listed:
- US Compliance, version 2025.2.0
Solutions supported by this app version:
- US Compliance, solution version 10.0.0
The features below are in order of functional relevance (i.e. the typical order in which a user executes a function or task).
Download the PDFPatch releases
The following patches are released for this version:
- US Compliance, version 2025.2.6 is available on Validation on 08 Mar 2026 and Production on 05 Apr 2026.
- US Compliance, version 2025.2.5 is available on Validation and Production on 25 Feb 2026.
- US Compliance, version 2025.2.4 is available on Validation on 24 Jan 2026 and Production on 08 Feb 2026.
- US Compliance, version 2025.2.3 is available on Validation and Production on 17 Dec 2025.
- US Compliance, version 2025.2.2 is available on Validation and Production on 12 Dec 2025.
- US Compliance, version 2025.2.1 is available on Validation on 18 Oct 2025 and Production on 26 Oct 2025.
These patches are cumulative, and the most recent patch release includes functionality from all previous versions.
Revisions
| Date | Revision | Description |
|---|---|---|
| 14 Aug 2025 | 01 | Initial version. |
| 13 Sep 2025 | 02 | The following updates have been made since the previous revision was distributed:
|
| 18 Sep 2025 | 03 | The following updates have been made since the previous revision was distributed:
|
| 18 Oct 2025 | 04 | The following updates have been made since the previous revision was distributed:
|
| 26 Oct 2025 | 05 | The following updates have been made since the previous revision was distributed:
|
| 12 Dec 2025 | 06 | The following updates have been made since the previous revision was distributed:
|
| 17 Dec 2025 | 07 | The following updates have been made since the previous revision was distributed:
|
| 24 Jan 2026 | 08 | The following updates have been made since the previous revision was distributed:
|
| 08 Feb 2026 | 09 | The following updates have been made since the previous revision was distributed:
|
| 25 Feb 2026 | 10 | The following updates have been made since the previous revision was distributed:
|
| 08 Mar 2026 | 11 | The following updates have been made since the previous revision was distributed:
|
API features
There is no new or updated API functionality included in this release.
System features
The following new or updated system functionality is included in this release. These features are changes to the app to support another feature and do not have any impacts on their own.
Improve API Performance With Automated Query Routing
This feature enhances how the system handles API requests by automatically choosing the most efficient way to retrieve data, improving performance without changing how requests are made.
Impact analysis
- Interface options:
- There are no UI or API impacts.
- Business segment impacts:
- Pharmaceutical Manufacturer (Owners)
- Wholesale Distributor (Owners)
- Dispenser (Owners)
Improve Processing Speed by Grouping Messages
This feature improves US Compliance performance by grouping messages based on their size and type, allowing the system to process smaller and similar messages faster and reduce overall delays.
Impact analysis
- Interface options:
- There are no UI or API impacts.
- Business segment impacts:
- Pharmaceutical Manufacturer (Owners)
- Wholesale Distributor (Owners)
- Dispenser (Owners)
Resolved issues
US Compliance, version 2025.2.6
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 |
|---|---|---|
| CMCP-38892: Delivery Status Remains “Delivery Failed” After Successful Re-Delivery | Processing |
Previously, when a shipment delivery from Product Track to a downstream partner failed and was later successfully re-delivered, the delivery status could remain “Delivery Failed.” Even though the partner received the file, the existing US Delivery record and related T2 information were not updated, causing discrepancies in reported shipment status. With this fix, when a previously failed outbound EPCIS file is successfully re-delivered, the same US Delivery record is updated to “DELIVERED,” and the related B2B and T2 details reflect the latest outcome. NOTE: If a re-delivery occurs more than 30 days after the original attempt (or beyond any future configured time limit), the updated successful status will not be reflected, even if the partner receives the file. This issue is resolved. |
| CMCP-41499: Search Fails When Future End Date Is Selected In Date Filter | Processing |
Previously, when users searched by PO Number or Transaction ID in US Compliance and selected a future end date (for example, when their local time zone was ahead of UTC), the search failed with an error stating the end date could not be greater than today’s date. No results were shown, even though the file had processed successfully and the data was available in Classic Access/TTS. The system now automatically adjusts a future end date to the current UTC day and returns matching results instead of displaying an error. This issue is resolved. |
| CMCP-41500: Incorrect Error Message Displayed When Viewing Shipment Details Or Downloading Files | Processing |
In some cases, when users viewed shipment details or downloaded related files (such as serial number lists or T2 document files) for a specific delivery, the system displayed an error message from a different delivery. The error text and delivery number did not match the selected shipment, causing confusion. The system has been updated to ensure error messages and shipment details are correctly linked to the selected delivery. This issue is resolved. |
| TL-98462: ORD Report Does Not Display Inbound File Name And Processing Time | Processing |
This issue occurred when users reviewed ORD reports for US Compliance transactions. The inbound file name and processing time were missing from the report, making it difficult to identify and track files. The report has been updated to display the inbound file name and processing time as expected for US Compliance transactions. This issue is resolved. |
US Compliance, version 2025.2.5
The purpose of this patch release is to provide internal bug fixes. There are no customer-facing resolved issues in this release.
US Compliance, version 2025.2.4
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-81587: Downloaded T2 CSV Files Excluded Ship From and Ship To Location Details | Processing |
This issue occurred when users downloaded T2 documents as CSV files from the US Compliance application. While the Ship From and Ship To location details displayed correctly in the UI, these fields were not included in the downloaded CSV. As a result, the exported file did not fully reflect the on-screen data and was missing key location information. This issue is resolved. |
US Compliance, version 2025.2.3
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 |
|---|---|---|
| CMCP-41306: Delays in US Product Track Message Processing | Processing |
US Product Track messages were processed with significant delays due to an increased processing backlog. This resulted in impacts to compliance activities, reporting, and partner integrations, along with an increased risk of workflow disruptions and missed service level agreements. This issue is resolved. |
US Compliance, version 2025.2.2
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-84108: Deliveries Not Displayed When Delivery Number Exceeds 500 Characters | Processing |
Users could not view deliveries in the US Compliance application on OPUS when the delivery number was longer than 500 characters, even though Product Track processing at T&TS was successful. This issue is resolved. |
| TL-90767: Voided Records Not Visible in ORD Reports For US Delivery | Processing |
Users viewing ORD Reports for US Delivery could not see voided transactions, which resulted in incomplete report data. The issue appeared only in reports with fewer than 512 records while larger reports were not affected. This issue is resolved. |
US Compliance, version 2025.2.1
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 |
|---|---|---|
| CMCP-40228: Delivery Type Value Format Incorrect in Summary CSV Report | Web UI |
In the Summary CSV report, the Delivery Type values were displayed in all capital letters. This has been corrected to use camel case formatting for consistency. This issue is resolved. |
US Compliance, version 2025.2.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 |
|---|---|---|
| CMCP-39967: Notifications Displayed Incorrect Company Information for Partner Users | Processing |
When Partner company users triggered an export, the notification used the Owner company’s ID instead of the user’s company ID. As a result, the notifications showed the wrong company information and the View Details link did not work. This issue is resolved. |
| CMCP-40000: Targeted Recall Data Exports Failed Due to Schema Version Mismatch | Processing |
Customers experienced failures when exporting Targeted Recall data because some recall records were not aligned with the latest schema version. This caused certain recall objects to fail during export. This issue is resolved. |
Known issues
US Compliance, version 2025.2.6
There are no known issues in this release.
US Compliance, version 2025.2.5
There are no known issues in this release.
US Compliance, version 2025.2.4
There are no known issues in this release.
US Compliance, version 2025.2.3
There are no known issues in this release.
US Compliance, version 2025.2.2
There are no known issues in this release.
US Compliance, version 2025.2.1
There are no known issues in this release.
US Compliance, version 2025.2.0
The following known issues are included in this release and will be fixed in a future patch release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.
| ID | Interface | Issue Description |
|---|---|---|
| TL-81429: Partial Lot Number Search Not Working for Older US Delivery and T2 Records | Processing |
Partial keyword search for Lot Number does not work for records created before the US Compliance 2025.1.1 release in Deliveries and before the 2025.2.0 release in T2 Documents. Newer records are searchable using partial Lot Number. Workaround: Use the full Lot Number for searching older records. |
Tag end
