What's new in the system
Type = What's New,; Topic = Opus Platform,;Persona = Solution Designer, TraceLink Administrator, Solution Partner,; Orchestration = Manufacturing, Logistics, Commerce, Transportation,; Function = Quality,
Explore what's new in the Extensible TraceLink Transfer, version 2025.3.0 release.To learn more about what's new in the Extensible TraceLink Transfer, solution version 7.1.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 Extensible TraceLink Transfer, version 2025.3.0 app release, which is available on Validation and Production on 17 Jul 2025.
The following apps are impacted by this release and will be updated to the version listed:
- Extensible TraceLink Transfer, version 2025.3.0
Solutions supported by this app version:
-
Extensible TraceLink Transfer, solution version 7.1.0
-
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 |
|---|---|---|
| 17 Jul 2025 | 01 |
Initial version.
|
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. This feature has changes to the app to support another feature and do not have any impacts on their own.
B2B Support for Non-EDI Batch Inbound Messages
Application Administrators can now send multiple messages (e.g. Purchase Orders and Purchase Order Acknowledgments) in a single file for batch processing by setting the to XTT_BATCH in the parent message. Sending multiple messages in a single file prevents ERP users from having to send a single file to TraceLink for each individual message. XTT supports batch processing for non-EDI file formats (e.g. .csv, .xml). For example, a sample.csv file can now contain a Purchase order IDOC, PO ACK X12, and Invoice IDOC message. Previously, each message had to be sent into TraceLink individually.
A Transform must be configured to parse and split the batch file into individual child B2B messages, which are then individually displayed on the Search B2B Messages screen. Parsing the parent batch file ensures that each individual child message is processed independently. Without a properly configured Transform, the system will treat the entire batch as a single message, preventing downstream components from executing message-specific logic such as validation, mapping, or routing.
After parsing, each child message is assigned a unique Message ID derived from the parent. For instance, if the parent Message ID is FZDFG456DG2R, a corresponding child message appears as FZDFG456DG2R:INBOUND_003.
XTT supports only inbound batch messages.
Impact analysis
- Interface options:
- Processing
- Business segment impacts:
- All business segments for both Owners and Partners.
Resolved issues
Extensible TraceLink Transfer, version 2025.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-74097:Unable to Create Outbound-only Connection for SMTP Connection Via API | Processing |
Previously, creating a connection required both inbound and outbound configurations. Now, you can configure either inbound or outbound independently. This issue is resolved. |
Known issues
Extensible TraceLink Transfer, version 2025.3.0
There are no known issues in this release.
Tag end
