Oracle® Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework 11g Release 1 (11.1.1.7.2) Part Number B31974-15 |
|
|
PDF · Mobi · ePub |
This appendix provides a quick summary of how basic tasks performed with the most common Oracle Forms triggers are accomplished using Oracle ADF.
This appendix includes the following sections:
Table D-1 ADF Equivalents for Oracle Forms Validation and Defaulting Triggers
Forms Trigger | ADF Equivalent |
---|---|
Execute validation code at the record level |
In the custom |
Execute validation code at the field level |
In the custom |
Execute code when a row in the data block is marked for insert or update |
Override the |
Execute code to populate complex default values when a new record in the data block is created, without changing the modification status of the record |
Override the To immediately set a primary key attribute to the value of a sequence, construct an instance of the If you want to wait to assign the sequence number until the new record is saved, but still without using a database trigger, you can use this technique in an overridden If instead you want to assign the primary key from a sequence using your own |
Execute code whenever a row is removed from the data block |
Override the |
Table D-2 ADF Equivalents for Oracle Forms Query Processing Triggers
Forms Trigger | ADF Equivalent |
---|---|
Execute logic before executing a query in a data block, typically to set up values for Query-by-Example criteria in the "example record" |
Override the |
Override default behavior to count the query hits for a data block |
Override the |
Execute logic after retrieving each row from the data source for a data block. |
Generally instead of using a |
Override default behavior to attempt to acquire a lock on the current row in the data block |
Override the |
Table D-3 ADF Equivalents for Oracle Forms Database Connection Triggers
Forms Trigger | ADF Equivalent |
---|---|
Execute logic after logging into the database |
Override the |
Execute logic before logging out of the database |
Override the |
Table D-4 ADF Equivalents for Oracle Forms Transactional Triggers
Forms Trigger | ADF Equivalent |
---|---|
Execute code before commencing processing of the changed rows in all data blocks in the transaction |
Override the Note: For an overview of creating and using a custom |
Execute code before a new row in the data block is inserted into the database during "post" processing |
Override the |
Override default processing for inserting a new row into the database during "post" processing |
Override the |
Execute code after new row in the data block is inserted into the database during "post" processing |
Override the |
Execute code before a row removed from the data block is deleted from the database during "post" processing |
Override the |
Override default processing for deleting a row removed from the data block from the database during "post" processing |
Override the |
Execute code after a row removed from the data block is deleted from the database during "post" processing |
Override the |
Execute code before a row changed in the data block is updated in the database during "post" processing |
Override the |
Override default processing for updating a row changed in the data block from the database during "post" processing |
Override the |
Execute code after a row changed in the data block is updated in the database during "post" processing |
Override the |
Execute code after Forms has "posted" all necessary rows to the database, but before issuing the data commit to end the transaction |
If you want a single block of code for the whole transaction, you can override the To execute entity-specific code before commit for each affected entity in the transaction, override the |
Execute code after database transaction has been committed |
Override the |
Table D-5 ADF Equivalents for Oracle Forms Error Handling Triggers
Forms Trigger | ADF Equivalent |
---|---|
Override default behavior for handling an error |
Install a custom error handler ( |