Agent Set to Trigger on Appointment Change is Triggered on Shipment Actual Arrival Event.
(Doc ID 748612.1)
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Transportation Management - Version: 5.5.04
This problem can occur on any platform.
-- Problem Statement:
You have an agent set to be triggered when an appointment is updated. However, when the arrival time of a Shipment is entered as an Event and where the appointment will not need to be updated, the agent is still triggering.
Expect the agent to trigger only when the Appointment is updated.
-- Steps To Reproduce:
1 - Log on to OTM.
2 - Create a new Agent with the ID APPOINTMENT_SCHEDULED (for this example).
3 - This agent is set to listen for event shipment - 'appointment scheduled'. (The action is to set an external status).
4 - Check for an Order Release that is planned onto a shipment that already has appointments.
5 - Navigate to the Related Shipment.
6 - Check that Secure Resources have previously been tendered.
7 - Right click and used View Appointments from Smart Links.
8 - Ensure there is an existing Appointment for the destination location and note the appointment times.
9 - Return to the Shipment.
10 - Add an event.
Actions > Events > Add Shipment Event
Arrived at Delivery Location with an event date/time.
11 - The agent SHIPMENT EVENT TRACKER was triggered.
12 - The agent APPOINTMENT_SCHEDULED is then triggered.
13 - Return to the Shipment and use Smart Links to see Related Appointments, the Appointment is for the same times as before, the Appointment time has not been changed, therefore the Agent
APPOINTMENT_SCHEDULED should not have been triggered.
The agent APPOINTMENT_SCHEDULED should not have been triggered.
At no point during these steps was the Appointment made or changed. The agent is expected to be triggered only when the event 'appointment scheduled' arises.
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