Oracle Forms Developer – Form Builder Reference, Volume 1

Master/Detail triggers
Form Builder 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. Instead, simply create a relation object, and let Form Builder
generate the triggers required to manage coordination between the master and detail blocks in the
relation.
trigger Typical Usage
On-Check-Delete-Master Fires when Form Builder attempts to delete a record
in a block that is a master block in a master/detail
relation.
On-Clear-Details Fires when Form Builder 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 Form Builder 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
Form Builder automatically issues appropriate error and informational messages in response to runtime
events. Message handling triggers fire in response to these default messaging events.
trigger Typical Usage
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 Form Builder with a
custom message.
Navigational triggers
Navigational triggers fire in response to navigational events. For instance, when the operator clicks on a
text item in another block, navigational events occur as Form Builder moves the input focus from the
current item to the target item.
420