Triggers in Oracle Forms

Triggers are blocks of PL/SQL code that are written to perform tasks when a specific event occurs within an application. In effect, an  Oracle Forms trigger is an event-handler written in PL/SQL to augment (or occasionally replace) the default processing behavior. Every trigger has a name, and contains one or more PL/SQL statements. A trigger encapsulates PL/SQL code so that it can be associated with an event and executed and maintained as a distinct object.

Block Processing Triggers:

Block processing triggers fire in response to events related to record management in a block.

ñ When-Create-Record Perform an action whenever Oracle Forms attempts to create a new record in a block.

ñ When-Clear-Block Perform an action whenever Oracle Forms flushes the current block; that is, removes all records from the block.

ñ When-Database-Record Perform an action whenever Oracle Forms changes a record’s status to Insert or Update, thus indicating that the record should be processed by the next COMMIT_FORM operation.

Interface Event Triggers:

Interface event triggers fire in response to events that occur in the form interface. Some of these triggers, such as When-Button-Pressed, fire only in response to operator input or manipulation. Others, like When-Window-Activated, can fire in response to both operator input and programmatic control.

ñ When-Button-Pressed Initiate an action when an operator selects a button, either with the mouse or through keyboard selection.

ñ When-Checkbox-Changed Initiate an action when the operator toggles the state of a check box, either with the mouse or through keyboard selection.

ñ When-Image-Activated Initiate an action whenever the operator double-clicks an image item.

ñ When-Image-Pressed Initiate an action whenever an operator clicks on an image item.

ñ When-Radio-Changed Initiate an action when an operator changes the current radio button selected in a radio group item.

ñ When-Window-Activated Initiate an action whenever an operator or the application activates a window.

ñ When-Window-Closed Initiate an action whenever an operator closes a window with the window manager’s Close command.

ñ When-Window-Deactivated Initiate an action whenever a window is deactivated as a result of another window becoming the active window.

Master/Detail Triggers:

Oracle Forms generates master/detail triggers automatically when a master/detail relation is defined between blocks. The default master/detail triggers enforce coordination between records in a detail block and the master record in a master block. Unless developing custom block-coordination schemes, you do not need to define these triggers.

ñ On-Check-Delete-Master Fires when Oracle Forms attempts to delete a record in a block that is a master block in a master/detail relation.

ñ On-Clear-Details Fires when Oracle Forms needs to clear records in a block that is a detail block in a master/detail relation because those records no longer correspond to the current record in the master block.

ñ On-Populate-Details Fires when Oracle Forms needs to fetch records into a block that is the detail block in a master/detail relation so that detail records are synchronized with the current record in the master block.

Message-Handling Triggers:

Oracle Forms automatically issues appropriate error and informational messages in response to runtime events. Message handling triggers fire in response to these default messaging events.

ñ On-Error Replace a default error message with a custom error message, or to trap and recover from an error.

ñ On-Message To trap and respond to a message; for example, to replace a default message issued by Oracle Forms with a custom message.

Validation Triggers:

Validation triggers fire when Oracle Forms validates data in an item or record. Oracle Forms performs validation checks during navigation that occurs in response to operator input, programmatic control, or default processing, such as a Commit operation.

ñ When-Validate-Item

ñ When-Validate-Record

Navigational Triggers:

Navigational triggers fire in response to navigational events. Navigational triggers can be further sub-divided into two categories: Pre- and Post- triggers, and When-New-Instance triggers. Pre- and Post- Triggers fire as Oracle Forms navigates internally through different levels of the object hierarchy. When-New-Instance-Triggers fire at the end of a navigational sequence that places the input focus on a different item.

ñ Pre-Form Perform an action just before Oracle Forms navigates to the form from “outside” the form, such as at form startup.

ñ Pre-Block Perform an action before Oracle Forms navigates to the block level from the form level.

ñ Pre-Record Perform an action before Oracle Forms navigates to the record level from the block level.

ñ Pre-Text-Item Perform an action before Oracle Forms navigates to a text item from the record level.

ñ Post-Text-Item Manipulate an item when Oracle Forms leaves a text item and navigates to the record level.

ñ Post-Record Manipulate a record when Oracle Forms leaves a record and navigates to the block level.

ñ Post-Block Manipulate the current record when Oracle Forms leaves a block and navigates to the form level.

ñ Post-Form Perform an action before Oracle Forms navigates to “outside” the form, such as when exiting the form.

ñ When-New-Form-Instance Perform an action at form start-up. (Occurs after the Pre-Form trigger fires).

ñ When-New-Block-Instance Perform an action immediately after the input focus moves to an item in a block other than the block that previously had input focus.

ñ When-New-Record-Instance Perform an action immediately after the input focus moves to an item in a different record.

ñ When-New-Item-Instance Perform an action immediately after the input focus moves to a different item.  

Transactional Triggers:

Transactional triggers fire in response to a wide variety of events that occur as a form interacts with the data source.

ñ On-Delete

ñ On-Insert

ñ On-Update

ñ On-Logon

ñ On-Logout

ñ Post-Database-Commit

ñ Post-Delete

ñ Post-Insert

ñ Post-Update

ñ Pre-Commit

ñ Pre-Delete

ñ Pre-Insert

ñ Pre-Update

Query-Time Triggers:

Query-time triggers fire just before and just after the operator or the application executes a query in a block.

ñ Pre-Query Validate the current query criteria or provide additional query criteria programmatically, just before sending the SELECT statement to the database.

ñ Post-Query Perform an action after fetching a record, such as looking up values in other tables based on a value in the current record. Fires once for each record fetched into the block.