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: …

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 …

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 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 …

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, …

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 …

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 …