Business Process Automation

Event Restrictions

The event restrictions may be created from the Agent Header tab on the Agent Manager page (which is accessed via Agents and Milestones > Automation Agent).

Use the Event Parameters page to define restrictions on when events occur. Click the Restrictions Information icon icon next to the Restrictions field (if it appears adjacent to the Event field) in order to configure the following parameters. The fields that appear vary depending on the event entered.

Source

An event source identifies the way in which an event takes place. For example, an Order Base - Created event can be initiated by a user adding an order in Order Manager (User) or imported via the Oracle Transportation Management Integration system (Integration). An event my also be triggered by an Oracle Transportation Management internal event (Internal). Events may be initiated by the following sources.

  • Integration: the event occurs as a result of an XML document that is imported into Oracle Transportation Management via the integration system.
  • Internal: the event is caused by standard Oracle Transportation Management workflow processing.
  • Migration: The source of the data that is created through the Promote To Production import process. For example, if you import a Location the lifetime event available for triggering an agent will have a DataSource of MIGRATION (i.e. rather than INTEGRATION).
  • User: the event occurs as a result of a person using the Oracle Transportation Management user interface.

By default, events are configured for no source (Source parameter is NONE) but you can restrict the interest to one or more sources. If you leave the default, the agent will not execute, even if it is marked active.

The following conditional operators appear for the Source field:

  • Same As: allows you to choose one event source from the list.
  • One Of: allows you to select more than one event source from the list (hold down the CTRL key to select multiples.)

Before Persist

Use this parameter when you want to use the Persist/Don't Persist actions. Oracle Transportation Management filters the new data in staging tables and takes the actions that you have defined. The actions you can use for events configured with the Before Persist parameter are restricted based on the Agent Type you selected.

Child Event Set

If you selected an event that has sub-events such as Order Base Modified, you can choose a sub-event as an additional restriction; for example, order base status changes only.

Status Type and Status Value

You can use these parameters for Status-related events such as Order Release - Status Changed, etc., to limit the event to records with a specific Status Type or Value.

Shipment Status - Received

For the event Shipment Status - Received, you can specify which shipment event group the shipment status should be included.

Document Restrictions

For any lifetime event involving a Document Requested or a Document Received event, you can specify which Document Type should be included.

Related Topics