Outbound Duplicate Detection Criteria
Note: For asynchronous and synchronous responses, outbound duplicate detection is not supported (only inbound duplicate detection is supported).
The following fields from the private process are used to calculate the message digest for duplicate detection for outbound requests:
TransactionID
received from the user
Note: When the outbound File Poller initiates a transaction, the
transactionID
element is used for calculating the message digest.
- Payload:
plainRequest, binaryRequest, inputFileName
(file content) - Trading partner host name
- Operation ID
- Host name