Automation on Learn Oracle OTM

Agents - Frequently Used Actions

Fri, 05 Aug 2016 20:29:00 +0000

This page covers the most commonly used Oracle OTM agent actions, with syntax examples and usage notes for each.

DIRECT SQL UPDATE

This action is used to execute a DML statement or call a PL/SQL procedure from within an agent.

Insert Statement format:

INSERT INTO order_release_refnum (order_release_gid,
ORDER_RELEASE_REFNUM_QUAL_GID,
ORDER_RELEASE_REFNUM_VALUE,
DOMAIN_NAME)
SELECT orr.order_release_gid,
'SO_NUM',
orlr.orl_refnum_value,
orlr.domain_name
FROM order_release orr,
order_release_line orl,
order_release_line_refnum orlr
WHERE orr.order_release_gid = orl.order_release_gid
AND orl.order_release_line_gid = orlr.order_release_line_gid
AND orlr.ORDER_RELEASE_REFNUM_QUAL_GID = 'SO_NUM'
AND ROWNUM = 1
AND NOT EXISTS
(SELECT 1
FROM order_release_refnum oref
WHERE oref.order_release_gid =
orr.order_release_gid
AND oref.order_release_refnum_qual_gid =
'SO_NUM')
AND orr.order_release_gid = $gid

Update Statement format:

Agents - Sample Agent Creation Steps

Fri, 05 Aug 2016 19:33:00 +0000

Agents in OTM are workflow processes that listen to specific events happening in the system and trigger actions. They are similar to database triggers that execute code when DML events occur at the database layer.

Example Requirement: Send a notification to a specific user when a shipment is created from bulk plan with a total volume less than 100 cubic feet.

High-level steps:

Identify the business object — in this example, Shipment.
Identify the OTM event — in this example, Shipment - Created.
Identify the conditions that must be met — the shipment must be a bulk plan shipment and have volume less than 100 cubic feet.
Define the action — send a notification.
Define error handling actions.

Step 1: Create a Saved Query

Agents - Agent Event Restrictions

Mon, 15 Aug 2016 16:53:00 +0000

Agent Event Restrictions give you control over which types of transactions trigger an agent, and optionally allow you to validate inbound XML transactions before they are committed to the database.

Access this by clicking the “i” icon on the agent header screen:

The Event Restrictions panel appears:

Source Options:

INTEGRATION: Triggers the agent only when the business object (e.g., Order Release) is created by an inbound GlogXML transmission from an external system. Use this when you want agent logic to run only for XML-uploaded transactions.

INTERNAL: Triggers the agent only when the business object is created by a standard OTM internal action, such as "RELEASE ORDER BASE". Use this when the agent should respond to system-generated events, not user or integration activity.

USER: Triggers the agent only when the business object is manually entered by a user within the OTM application.

Before Persist:

Agent Gates

Sun, 15 Feb 2026 17:29:00 +0000

Agent Gates allow you to add custom saved-query conditions to standard OTM events and workflows. They operate at the domain level and can either extend or completely replace standard OTM validations. If the gate condition fails, the standard workflow is stopped.

Business Process Automation > Power Data > Event Management > Agent Gates

For example, to stop the tender workflow for specific transport modes, configure an Agent Gate with the following values:

Object Type: SHIPMENT
Status Function: WKFLW_TENDER
Functor Class: glog.server.workflow.shipment.ShipmentStatus$Tender
Saved Condition ID: Write a SQL condition with your custom business rules
Saved Condition Additive: Check this box

Business Monitors

Sun, 15 Feb 2026 18:17:00 +0000

The Business Monitor is designed to give planners and operations teams real-time visibility into critical business transactions relevant to their role. For example, a planner can configure a monitor to display all orders that failed during bulk planning, using a saved query and screen set — then attach the monitor to their user profile or role so it updates automatically.

You can launch the Business Monitor by clicking the flag icon at the top of the OTM page.

Action Checks

Thu, 20 Sep 2018 18:06:00 +0000

Action Checks allow you to add custom validations on manager layouts before data is saved to the database. This is useful when a screen has conditional mandatory fields — for example, requiring either a pre-existing location XID or a full set of address fields, but not both.

Example Scenario:

A custom manager layout allows users to enter PO details. The destination can be set by selecting an existing Location XID, or by entering a new address (address line 1, zip code, etc.) using custom attributes. The validation must ensure that at least one of these two options is populated before the record is saved.

Custom Actions & Smart Links

Fri, 21 Sep 2018 20:38:00 +0000

Custom Actions allow users to trigger an agent or perform an operation directly from the OTM UI against a selected list of transactions. Smart Links are similar but operate on a single selected record and navigate the user to related data. The example below shows how to configure a custom action that triggers an INVOICE agent when a user selects ‘Reprocess Invoice’ from the Actions menu on a list of invoices.