Agent Events

This page is accessed via Business Process Automation > Power Data > Event Management > Agent Events.

Oracle Transportation Management includes a collection of events that you can choose from during the process of creating an agent. However, if public Oracle Transportation Management events are not appropriate for the purposes of your agent, you can create your own agent event to suit your individual business needs.

Use custom agent events whenever you need to string together a collection of processes or changes to a business object in a way that would otherwise become time-consuming. Using agent events automates this process by allowing you to raise a custom agent event as a part of an agent, which will in turn trigger another agent to complete a process.

At a minimum, you need to create at least two agents to use an agent event properly: one agent that raises the event, then another agent that listens for the event. In most situations, you use the raising of custom events to raise other agent types (order release, invoice, etc.). For example, you can create a shipment agent that changes the shipment status, and raises a custom event that triggers an order release agent. With this example, you can do both the listening and status change from the same shipment agent. You can also use the data query process to raise custom events for a group of business objects at one time.

Note: Using agent events to create complex agents can possibly cause adverse effects on Oracle Transportation Management performance. Because all the agents connected by agent events should be turned on in order to work properly (in most cases), it may be preferable to use more complex saved conditions within an agent, instead of using agent events, to create the same result. This may combat possible performance problems caused by having too many agents active within a given time period.

You must still use the Event Notification page in the Communication Manager to search for and configure Oracle Transportation Management event notifications.

When viewing an existing agent event, all agents that listen for this event are displayed in the Agents section. Similar information is displayed in the Agent Actions, UI Actions, and Audit Actions sections.

Adding Agent Events

Note: Customs Shipment and Customs Shipment Line have been renamed as Declaration and Declaration Line, respectively. However, this change will not impact the Data Query Type drop-down list. "GTM Shipment", "GTM Shipment Document", and "GTM Shipment Line" will continue to be displayed as options in this list.

1. Enter a unique identifier in the Agent Event ID field.
2. Select a Data Query Type.
3. Select a domain in which this agent event will be active from the Domain Name drop-down list.
4. Enter a Contact Notification ID.
5. Select the Modification Event check box if this is a modification event. Selecting this check box enables the Agent Event Table Mappings section.
6. Enter an Agent Event Parent.
7. If desired, enter a Description.

Agent Event Table Mappings

This section only appears if the Modification Event check box is selected.

1. Click the New Agent Event Table Mapping button. When you map tables with an agent event, the agent event is raised when data is the mapped tables is updated. For example, if you map to the Shipment table, the event would be raised when information on a shipment is changed.
2. Click Finished.