Data Type Association Used In Agent Is Using Document Gid And Not Shipment GID In A Saved Condition.
(Doc ID 2608207.1)
Last updated on FEBRUARY 06, 2020
Applies to:
Oracle Transportation Management Cloud Service - Version 19.3 and laterInformation in this document applies to any platform.
Symptoms
Saved condition is incorrectly using the Document GID instead of the Shipment GID in a saved condition. This is causing this condition to fail. This issue is occurring when a saved condition in an agent action is triggered by another agent which is using a data type association.
Example:
Customer created 2 agents:
Agent 1: Document Type Agent
Event: DOCUMENT - ATTACHED
Action: Raises custom event with a data type association of Document to Shipment.
Agent 2: Shipment Type Agent
Custom Event
Action:
IF: Saved Condition (uses shipment GID)
NOTIFY CONTACT
When you trigger Agent 1 you will not receive a notification email and in the sql logs you will see that the Document GID is used to validate the IF saved condition instead of the shipment GID, which is expected.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |