ChannelManagerClient.trackDialogue is used to write the initial message — that is, the first business document in a conversation — to message tracking. To write subsequent messages in the same conversation, the trackDialogueAction operation is used.
Table 3–14 Input Containers for ChannelManagerClient.trackDialogue|
Name |
Description |
|---|---|
|
tpNetworkId |
eXchange-generated unique ID identifying the trading partner. |
|
dialogueID |
Database-assigned unique ID identifying the business conversation. |
|
dialogueIdentifier |
Dialog ID in the message. |
|
serviceName |
Name of the messaging service or business service being used to handle the message. |
|
activeFlag |
A value of Y signifies that the business conversation is active. |
|
Status |
Status of the business conversation. |
|
startDate |
Timestamp recording when the business conversation initiated. |
|
endDate |
Timestamp recording when the business conversation terminated. |
|
protocol |
Name of the protocol being used to handle the message. |
|
hostNetworkId |
eXchange-generated unique ID identifying the B2B host. |
|
isResponse |
A value of true signifies that the message is a response to a previous message. |
Table 3–15 Output Containers for ChannelManagerClient.trackDialogue
|
Name |
Description |
|---|---|
|
tpNetworkId |
eXchange-generated unique ID identifying the trading partner. |
|
dialogueID |
Database-assigned unique ID identifying the business conversation. |
|
dialogueIdentifier |
Dialog ID in the message. |
|
serviceName |
Name of the messaging service or business service being used to handle the message. |