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 PDFRevisions
| 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:
|
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.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.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
