What's new in the system
To learn more about what's new in the US Compliance, solution version 6.0 that provides the user interface for this app, see What's new in the user interface.
Release information
This document describes the TraceLink capabilities included in the US Compliance, version 2024.4 app release, which is available on Validation on 31 Aug 2024 and Production on 28 Sep 2024.
The following apps are impacted by this release and will be updated to the version listed:
- US Compliance, version 2024.4
Solutions supported by this app version:
- US Compliance, solution version 6.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 PDF
This Help Center is subject to change based on the successful deployment of the release. In the event of changes, the Help Center will be updated within one week of release deployment. Deployment completion can be confirmed in the TraceLink Release Notice email.
Revisions
| Date | Revision | Description |
|---|---|---|
| 02 Aug 2024 | 01 | Initial version. |
| 31 Aug 2024 | 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.
Export Single T2 Documents as PDFs
This feature includes support for the export of single T2 documents as a PDF file. For more information about the corresponding solution feature, see the US Compliance, solution version 6.0 release.
Impact analysis
The impacts for this feature are the same as the Export Single T2 Documents as PDFs feature in the US Compliance, solution version 6.0 release.
Export Product Tracing Response in JSON Format
This feature includes support to search for and download the Product Tracing - Transaction Information response in JSON format. For more information about the corresponding solution feature, see the US Compliance, solution version 6.0 release.
Impact analysis
The impacts for this feature are the same as the Export Product Tracing Response in JSON Format feature in the US Compliance, solution version 6.0 release.
View Messages for Failed Deliveries
This feature includes support for viewing failed deliveries in the results table. For more information about the corresponding solution feature, see the US Compliance, solution version 6.0 release.
Impact analysis
The impacts for this feature are the same as the View Messages for Failed Deliveries feature in the US Compliance, solution version 6.0 release.
Improve Performance and Refactoring of Code
This feature ensures that failed deliveries, T2 documents, and voided delivery messages are sent to the dead-letter queue (DLQ) after being retried. Previously, these messages were sent directly to the DLQ without any retries. Additionally, the code has been refactored to improve readability, reusability, and modularity without altering its functionality.
Impact analysis
- Interface options:
- There are no UI or API impacts.
- Business segment impacts:
- Pharmaceutical Manufacturer (both Owners and Partners)
- Repackager (both Owners and Partners)
- Wholesale Distributor (both Owners and Partners)
- Dispenser (both Owners and Partners)
Resolved issues
US Compliance, version 2024.4.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-36754: Inconsistent Behavior for DPS and RDPS Tags in T&TS and Opus PIM Shipment Notices for the Same Delivery | Processing |
For the same delivery and Portal Access Code, the EPCIS file from T&TS includes DPS tags, but the file from Opus PIM shipment notices does not. This issue is resolved. |
Known issues
US Compliance, version 2024.4.0
There are no known issues in this release.
