Wednesday, May 29, 2013

Form Cum Block Level Application Triggers and their Scope


SL NONAMEPurpose
1ON-CLEAR-DETAILSFires 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.
/***********end of SL 1 *******/
2ON-CHECK-DELETE-MASTERFires when Oracle Forms attempts to delete a record in a block that is a master block in a master/detail relation.
/***********end of SL 2 *******/
3ON-CHECK-UNIQUEDuring a commit operation, the On-Check-Unique trigger fires when Oracle Forms normally checks that primary key values are unique before inserting or updating a record in a base table. It fires once for each record that has been inserted or updated.
Enter Query Mode no Usage Notes : To perform the default processing from this trigger, call the CHECK_RECORD_UNIQUENESS built-inOn Failure: No effectFires In : Check Record Uniqueness
Post and Commit Transaction
/***********end of SL 3 *******/
4ON-CLOSEFires when an operator or the application causes a query to close. By default, Oracle Forms closes a query when all of the records identified by the query criteria have been fetched, or when the operator or the application aborts the query.

The On-Close trigger augments the normal Oracle Forms "close cursor" phase of a query.
Enter Query Mode noUsage Notes : Use an On-Close trigger after using the On-Select or On-Fetch triggers, specifically, to close files, close cursors, and free memory.
The On-Close trigger fires automatically when the ABORT_QUERY built-in is called from an On-Select trigger.
On Failure :  no effect
Abort_query: Close the query
/***********end of SL 4 *******/
5ON-COLUMN-SECURITYFires when Oracle Forms would normally enforce column-level security for each block that has the Enforce Column Security block property set On.
Enter Query Mode no
Usage Notes : To perform the default processing from this trigger, call the ENFORCE_COLUMN_SECURITY built-in. On Failure : No effect
/***********end of SL 5 *******/
6ON-COUNTFires when Oracle Forms would normally perform default Count Query processing to determine the number of rows in the database that match the current query criteria. When the On-Count trigger completes execution, Oracle Forms issues the standard query hits message: FRM-40355: Query will retrieve <n> records.
Enter Query Mode yesUsage Notes :
Use an On-Count trigger to replace default Count Query processing in an application running against a non-ORACLE data source.

If you are replacing default processing, you can set the value of the Query_Hits block property to indicate the number of records in the non-ORACLE data source that match the query criteria.

Oracle Forms will display the query hits message (FRM-40355) even if the On-Count trigger fails to set the value of the Query_Hits block property. In such a case, the message reports 0 records identified.
On Failure :  No effect

/***********end of SL 6 *******/
7ON-DELETEFires during the Post and Commit Transactions process and replaces the default Oracle Forms processing for handling deleted records during transaction posting. Specifically, it fires after the Pre-Delete trigger fires and before the Post-Delete trigger fires, replacing the actual database delete of a given row. The trigger fires once for each row that is marked for deletion from the database.
/***********end of SL 7 *******/
8ON-FETCHWhen a query is first opened, fires immediately after the On-Select trigger fires, when the first records are fetched into the block. While the query remains open, fires again each time a set of rows must be fetched into the block.
Enter Query Mode noUsage Notes :
When you write an On-Fetch trigger to replace default fetch processing, the trigger must do the following:
1)Retrieve the appropriate number of records from the non-ORACLE data source, as indicated by the setting of the Records_To_Fetch property.
2)Create that number of queried records in the current block.
3)Populate the records with the retrieved data.
4)Create queried records from an On-Fetch trigger by calling the CREATE_QUERIED_RECORD built-in subprogram. While the query remains open, the On-Fetch trigger continues to fire as more records are needed in the block. This behavior continues:
1) until no queried records are created in a single execution of the trigger. Failing to create any records signals an end-of-fetch to Oracle Forms, indicating that there are no more records to be retrieved. 2)until the query is closed, either by the operator or programmatically through a call to ABORT_QUERY. 3)until the trigger raises the built-in exception FORM_TRIGGER_FAILUREDo not use an ABORT_QUERY built-in in an On-Fetch trigger. ABORT_QUERY is not valid in an On-Fetch trigger, and produces inconsistent results.
On Failure :  No effects
Fires in : Fetch  records
/***********end of SL 8 *******/
9ON-INSERTFires during the Post and Commit Transactions process when a record is inserted. Specifically, it fires after the Pre-Insert trigger fires and before the Post-Insert trigger fires, when Oracle Forms would normally insert a record in the database. It fires once for each row that is marked for insertion into the database.
Usage Notes :Use an On-Insert trigger to replace the default Oracle Forms processing for handling inserted records during transaction posting.

To perform the default Oracle Forms processing from this trigger, include a call to the INSERT_RECORD built-in.
On Failure:
Oracle Forms performs the following steps when the On-Insert trigger fails.
sets the error location
rolls back to the most recent savepoint

/***********end of SL 9 *******/

10 ON-LOCK Description:
Fires whenever Oracle Forms would normally attempt to lock a row, such as when an operator presses a key to modify data in an item. The trigger fires between the keypress and the display of the modified data.
Legal Commands:
SELECT statements, unrestricted built-ins..
Enter Query Mode no 
Usage Notes :
i)Use an On-Lock trigger to replace the default Oracle Forms processing for locking rows. For example, for an application intended for use on a single-user system, use the On-Lock trigger to speed processing by bypassing all lock processing. Also, use On-Lock when accessing a non-ORACLE data source directly, not by way of Open Gateway.
ii) When the On-Lock trigger fires as a result of an operator trying to modify data, the trigger fires only the first time the operator tries to modify an item in the record. The trigger does not fire during subsequent modifications to items in the same record. In other words, for every row that is to be locked, the trigger fires once.
iii) To perform the default Oracle Forms processing from this trigger, include a call to the LOCK_RECORD built-in.
Iv)Use this trigger to lock underlying tables for non-updateable views.
Caution:
In special circumstances, you may use the LOCK TABLE DML statement in an On-Lock trigger. However, as this could result in other users being locked out of the table, please exercise caution and refer to the ORACLE RDMS Database Administrator's Guide before using LOCK TABLE.
On Failure :When the On-Lock trigger fails, the target record is not locked and Oracle Forms attempts to put the input focus on the current item. If the current item cannot be entered for some reason, Oracle Forms attempts to put the input focus on the previous navigable item.
Fires In: Lock the Row
11 ON-POPULATE-DETAILS /***********end of SL 10 *******/

Description:
Oracle Forms creates this trigger automatically when a Master/Detail relation is defined. It fires when Oracle Forms would normally need to populate the detail block in a Master/Detail relation.
Legal Commands: SELECT statements, PL/SQL, unrestricted built-ins, restricted built-ins
Enter Query Mode no
Usage Notes :
Use an On-Populate-Details trigger when you have established a Master/Detail relationship and you want to replace the default populate phase of a query.

The On-Populate-Details trigger does not fire unless an On-Clear-Details trigger is present. If you are using the default Master/Detail functionality, Oracle Forms creates the necessary triggers automatically. However, if you are writing your own Master/Detail logic, be aware that the On-Clear-Details trigger must be present, even if it contains only the NULL statement.

When Immediate coordination is set, this causes the details of the instantiated master to be populated immediately. Immediate coordination is the defaul

When Deferred coordination is set and this trigger fires, Oracle Forms marks the blocks as needing to be coordinated.

If you intend to manage block coordination yourself, you can call the SET_BLOCK_PROPERTY (COORDINATION_STATUS) built-in.

On Failure : Can cause an inconsistent state in the form.
Fires In : Master/Detail Coordination
/***********end of SL 11 *******/
12 ON-SELECT Description:
Fires when Oracle Forms would normally execute the open cursor, parse, and execute phases of a query, to identify the records in the database that match the current query criteria.
Legal Commands :
SELECT statements, PL/SQL, unrestricted built-ins.
Enter Query Mode : No
Usage Notes:  Use an On-Select trigger to open and execute the database cursor. Specifically, use this trigger when you are retrieving data from a non-ORACLE data source. The On-Select trigger can be used in conjunction with the On-Fetch trigger to replace the processing that normally occurs in the EXECUTE_QUERY built-in subprogram.

To perform the default Oracle Forms processing from this trigger, include a call to the SELECT_RECORDS built-in.
On Failure : No effect.
Fires In : EXECUTE_QUERY ,Open The Query
/***********end of SL 12 *******/
13 ON-UPDATE Description:
Fires during the Post and Commit Transactions process while updating a record. Specifically, it fires after the Pre-Update trigger fires and before the Post-Update trigger fires, when Oracle Forms would normally update a record in the database. It fires once for each row that is marked for update in the form.
Legal Commands :
SELECT statements, DML statements (DELETE, INSERT, UPDATE), unrestricted built-ins.
Enter Query Mode no
Usage Notes :
Use an On-Update trigger to replace the default Oracle Forms processing for handling updated records during transaction posting.
To perform the default Oracle Forms processing from this trigger, include a call to the UPDATE_RECORD built-in.
On Failure : Oracle Forms performs the following steps when the On-Update trigger fails:
i) sets the error location
ii) rolls back to the most recently issued savepoint
Fires In :
Post and Commit Transactions
/***********end of SL 13 *******/
14 POST-BLOCK Description:
Fires during the Leave the Block process when the focus moves off the current block.
Legal Commands : SELECT statements, unrestricted built-ins.
Enter Query Mode no
Usage Notes:
Use a Post-Block trigger to validate the block's current record; that is, the record that had input focus when the Leave the Block event occurred.
Use this trigger to test a condition and prevent the user from leaving a block based on that condition.
On Failure:
If the trigger fails while trying to make the form the navigation unit, Oracle Forms tries to set the target to a particular block, record or item. Failing that, Oracle Forms attempts to put the cursor at a target location, but, if the target is outside of the current unit or if the operator indicates an end to the process, Oracle Forms aborts the form.
Fires In : Leave the Block
Post-Block Trigger Restrictions :
A Post-Block trigger does not fire when the Validation Unit form document property is set to Form/***********end of SL 14 *******/
15 POST-DELETE Description : Fires during the Post and Commit Transactions process, after a row is deleted. It fires once for each row that is deleted from the database during the commit process.
Legal Commands : SELECT statements, DML statements (DELETE, INSERT, UPDATE), unrestricted built-in.
Enter Query Mode no
Usage Notes : Use a Post-Delete trigger to audit transactions.
On Failure :
Oracle Forms performs the following steps when the Post-Delete trigger fails:
i) sets the error location
ii)rolls back to the most recent savepoint
Fires In : Post and Commit Transactions
/***********end of SL 15 *******/
16 POST-INSERT Description: Fires during the Post and Commit Transactions process, just after a record is inserted. It fires once for each record that is inserted into the database during the commit process.
Legal Commands : SELECT statements, DML statements (DELETE, INSERT, UPDATE), unrestricted built-ins .
Enter Query Mode no
Usage Notes : Use a Post-Insert trigger to audit transactions.
On Failure : Oracle Forms performs the following steps when the Post-Insert trigger fails:
i) sets the error location
ii) rolls back to the most recent savepoint
Fires In : Post and Commit Transactions
/***********end of SL 16 *******/
17 POST-LOGON Description:
Fires after either of the following events:
i) The successful completion of Oracle Forms default logon processing.
Ii)The successful execution of the On-Logon trigger.
Legal Commands : SELECT statements, unrestricted built-ins.
Enter Query Mode no
Usage Notes:
Use a Post-Logon trigger to provide an event point for a task such as setting up a custom environment with special variables--to initialize on an application level rather than a form-by-form basis. You might accomplish this by initializing special global variables from this trigger.
On Failure : Varies based on the following conditions:

i)If the trigger fails during the first logon process, Oracle Forms exits the form, and returns to the operating system.
ii)If the trigger fails after a successful logon, Oracle Forms raises the built-in exception FORM_TRIGGER_FAILURE .
Fires In : LOGON
Post-Logon Trigger Example :
This example calls a user exit to log the current username and time to an encrypted audit trail file on the file system, which for security reasons is outside the database.
BEGIN
User_Exit('LogCrypt '||
USER||' ' ||
TO_CHAR(SYSDATE,'YYYYMMDDHH24MISS'));
END;
/***********end of SL 17 *******/
18 POST-LOGOUT Description: Fires after either of the following events:
i) Oracle Forms successfully logs out of ORACLE.
Ii) The successful execution of the On-Logout trigger.
Legal Commands : SELECT statements, unrestricted built-ins.
Enter Query Mode no
Usage Notes :
Use a Post-Logout trigger to audit or to perform tasks on an Oracle Forms application that does not require or affect the RDBMS or other data source.

If you call certain built-ins from within one of the Logout triggers, the results are undefined. For example, you cannot call COPY from a Pre-Logout trigger because Pre-Logout fires after the Leave the Form event. Because the form is no longer accessible, a COPY operation is not possible.
On Failure :
If this trigger fails while leaving the form, there is no effect.

If this trigger fails and you have initiated a call to the LOGOUT built-in from within the trigger, FORM_FAILURE is set to TRUE.
Fires In : LOGOUT
/***********end of SL 18 *******/
19 POST-QUERY Description:
When a query is open in the block, the Post-Query trigger fires each time Oracle Forms fetches a record into a block. The trigger fires once for each record placed on the block's list of records.
Legal Commands : SELECT statements, unrestricted built-ins .
Enter Query Mode no
Usage Notes :
i)Use a Post-Query trigger to perform the following tasks
ii)calculate statistics about the records retrieved by a query
iii)calculate a running total
iv) When you use a Post-Query trigger to SELECT non-base table values into control items, Oracle Forms marks each record as CHANGED, and so fires the When-Validate-Item trigger by default. You can avoid the execution of the When-Validate-Item trigger by explicitly setting the Status property of each record to QUERY in the Post-Query trigger. To set record status programmatically, use SET_RECORD_PROPERTY .
On Failure:
Oracle Forms flushes the record from the block and attempts to fetch the next record from the database. If there are no other records in the database, Oracle Forms closes the query and waits for the next operator action.
Fires In : Fetch Records
Post-Query Trigger Examples:
This example retrieves descriptions for code fields, for display in non-database items in the current block.
DECLARE
CURSOR lookup_payplan IS SELECT Payplan_Desc
FROM Payplan
WHERE Payplan_Id = :Employee.Payplan_Id;
CURSOR lookup_area IS SELECT Area_Name
FROM Zip_Code
WHERE Zip = :Employee.Zip;
Open fetch close : Please check the example in Help Topic-CTRL+H
/***********end of SL 19 *******/ 
20 POST-RECORD Description:
Fires during the Leave the Record process. Specifically, the Post-Record trigger fires whenever the operator or the application moves the input focus from one record to another. The Leave the Record process can occur as a result of numerous operations, including INSERT_RECORD , DELETE_RECORD , NEXT_RECORD , NEXT_BLOCK , CREATE_RECORD , PREVIOUS_BLOCK , etc.
Legal Commands : SELECT statements, unrestricted built-ins.
Enter Query Mode no
Usage Notes :
Use a Post-Record trigger to perform an action whenever the operator or the application moves the input focus from one record to another. For example, to set a visual attribute for an item as the operator scrolls down through a set of records, put the code within this trigger.
On Failure : The input focus stays in the current record.
Fires In :  Leave the Record
Post-Record Trigger Restrictions : A Post-Record trigger fires only when the form is run with a validation unit of the item or record, as specified by the Validation Unit form property.
/***********end of SL 20 *******/
21 POST-SELECT The Post-Select trigger fires after the default selection phase of query processing, or after the successful execution of the On-Select trigger. It fires before any records are actually retrieved through fetch processing.
Legal Commands : SELECT statements, unrestricted built-ins
Enter Query Mode : No
Usage Note: Use the Post-Select trigger to perform an action based on the outcome of the Select phase of query processing such as an action based on the number of records that match the query criteria.
On Failure: When the populate_group Built-in fails because the record group does not exist, a NULL value will be returned.
Execute the Query
Open the Query
/***********end of SL 21 *******/
22 POST-UPDATE Description :Fires during the Post and Commit Transactions process, after a row is updated. It fires once for each row that is updated in the database during the commit process.
Legal Commands : SELECT statements, DML statements (DELETE, INSERT, UPDATE), unrestricted function codes, unrestricted built-ins
Enter Query Mode no
Usage Notes : Use a Post-Update trigger to audit transactions.
On Failure : Oracle Forms performs the following steps when the Post-Update trigger fails:
i)sets the error location
ii)rolls back to the most recent savepoint
Fires In : Post and Commit Transactions
/***********end of SL 22 *******/
23 PRE-BLOCK Description: Fires during the Enter the Block process, during navigation from one block to another.
Legal Commands : SELECT statements, unrestricted built-ins
Enter Query Mode no
Usage Notes : Use a Pre-Block trigger to:
i)allow or disallow access to a block
ii )set variable values
On Failure : Navigation fails and focus remains in the source item.
Fires In : Enter the Block
Pre-Block Trigger Restrictions  :
A Pre-Block trigger fires only when the form is run with a validation unit of the item, record, or block, as specified by the Validation Unit form property.
/***********end of SL 23 *******/
24 PRE-DELETE Description : Fires during the Post and Commit Transactions process, before a row is deleted. It fires once for each record that is marked for delete.
Note: Oracle Forms creates a Pre-Delete trigger automatically for any master-detail relation that has the Delete Record Behavior property set to Cascading.
Legal Commands : SELECT statements, Data Manipulation Language (DML) statements (i.e., DELETE, INSERT, UPDATE), unrestricted built-ins
Enter Query Mode no
Usage Notes : Use a Pre-Delete trigger to delete the detail record of a master record.
  Use a Pre-Delete trigger to prevent the deletion of a record if that record is the master record for detail records that still exist.
On Failure : Oracle Forms performs the following steps when the Pre-Delete trigger fails:
i)sets the error location
ii)rolls back to the most recent savepoint
Fires In : Post and Commit Transactions
/***********end of SL 24 *******/
25 PRE-INSERT Description : Fires during the Post and Commit Transactions process, before a row is inserted. It fires once for each record that is marked for insert.
Legal Commands: SELECT statements, DML statements (DELETE, INSERT, UPDATE), unrestricted built-ins
Enter Query Mode no
Usage Notes : Use a Pre-Insert trigger to perform the following tasks:
i)change item values
ii) keep track of the date a record is created and store that in the record prior to committing
On Failure :
Oracle Forms performs the following steps when the Pre-Insert trigger fails:
i) sets the error location
ii)rolls back to the most recent savepoint
Fires In : Post and Commit Transactions
Refer Example CTRL+H
/***********end of SL 25 *******/
26 PRE-QUERY Description :
Fires during Execute Query or Count Query processing, just before Oracle Forms constructs and issues the SELECT statement to identify rows that match the query criteria.
Legal Commands : SELECT statements, unrestricted built-ins
Enter Query Mode no
Usage Notes : Use a Pre-Query trigger to modify the example record that determines which rows will be identified by the query.
On Failure : The query is canceled. If the operator or the application had placed the form in Enter Query mode, the form remains in Enter Query mode.
Fires In :
COUNT_QUERY
EXECUTE_QUERY
Open the Query
Prepare the Query
/***********end of SL 26 *******/
27 PRE-RECORD Description : Fires during the Enter the Record process, during navigation to a different record.
Legal Commands : SELECT statements, unrestricted built-ins
Enter Query Mode no
Usage Notes : Use a Pre-Record trigger to keep a running total.
On Failure : Navigation fails and focus remains in the current item.
Fires In : Enter the Record
Pre-Record Trigger Restrictions : A Pre-Record trigger fires only when the form is run with a validation unit of the item or record, as specified by the Validation Unit form property.
Pre-Record Trigger Example: The following trigger prevents the user from entering a new record given some dynamic condition and the status of SYSTEM.RECORD_STATUS evaluating to NEW.
IF (( dynamic-condition)
AND :System.Record_Status = 'NEW') THEN
RAISE Form_Trigger_Failure;
END IF;
/***********end of SL 27 *******/
28 PRE-SELECT Description :
Fires during Execute Query and Count Query processing, after Oracle Forms constructs the SELECT statement to be issued, but before the statement is actually issued. Note that the SELECT statement can be examined in a Pre-Select trigger by reading the value of the system variable SYSTEM.LAST_QUERY .
Legal Commands : Legal Commands
Enter Query Mode no
Usage Notes : Use a Pre-Select trigger to prepare a query prior to execution against a non-ORACLE data source.
On Failure : No effect. The current query fetched no records from the table. The table is empty, or it contains no records that meet the query's search criteria.
Fires In :
EXECUTE_QUERY
Open the Query
Prepare the Query
/***********end of SL 28 *******/
29 PRE-UPDATE Description :
Fires during the Post and Commit Transactions process, before a row is updated. It fires once for each record that is marked for update.
Legal Commands : Legal Commands
SELECT statements, DML statements (DELETE, INSERT, UPDATE), unrestricted built-ins
Enter Query Mode no
Usage Notes : Use a Pre-Update trigger to audit transactions.
On Failure: Oracle Forms performs the following steps when the Pre-Update trigger fails:
sets the error location
rolls back to the most recent savepoint
Fires In : Post and Commit Transactions
/***********end of SL 29 *******/
30 WHEN-BUTTON-PRESSED Description : Fires when an operator selects a button, by clicking with a mouse, or using the keyboard.
Legal Commands : SELECT statements, unrestricted built-ins, restricted built-ins
Enter Query Mode yes
Usage Notes : Use a When-Button-Pressed trigger to perform navigation, to calculate text item values, or for other item, block, or form level functionality.
On Failure :  no effect
When-Button-Pressed Trigger Example
This example executes a COMMIT_FORM if there are changes in the form.
BEGIN
IF :System.Form_Status = 'CHANGED' THEN
Commit_Form;
/*
** If the Form_Status is not back to 'QUERY'
** following a commit, then the commit was ** not successful.
*/
IF :System.Form_Status <> 'QUERY' THEN
Message('Unable to commit order to database...');
RAISE Form_Trigger_Failure;
END IF;
END IF;
END;
/***********end of SL 30 *******/
31 WHEN-CHECKBOX-CHANGED Description :
Fires when an operator changes the state of a check box, either by clicking with the mouse, or using the keyboard.
Legal Commands : SELECT statements, unrestricted built-ins, restricted built-ins
Enter Query Mode yes
Usage Notes:
Use a When-Checkbox-Changed trigger to initiate a task dependent upon the state of a check box.
When an operator clicks in a check box, the internal value of that item does not change until navigation is completed successfully. Thus, the When-Checkbox-Changed trigger is the first trigger to register the changed value of a check box item. So for all navigation triggers that fire before the When-Checkbox-Changed trigger, the value of the check box item remains as it was before the operator navigated to it.
On Failure :no effect /***********end of SL 31 *******/
32 WHEN-CLEAR-BLOCK Description :
Fires just before Oracle Forms clears the data from the current block.
Note that the When-Clear-Block trigger does not fire when Oracle Forms clears the current block during the CLEAR_FORM event.
Legal Commands : SELECT statements, unrestricted built-ins
Enter Query Mode yes
Usage Notes :
Use a When-Clear-Block trigger to perform an action every time Oracle Forms flushes the current block. For example, you might want to perform an automatic commit whenever this condition occurs.

In a When-Clear-Block trigger, the value of SYSTEM.RECORD_STATUS is unreliable because there is no current record. An alternative is to use GET_RECORD_PROPERTY to obtain the record status. Because GET_RECORD_PROPERTY requires reference to a specific record, its value is always accurate.
On Failure : no effect on the clearing of the block
Fires In :
CLEAR_BLOCK
COUNT_QUERY
ENTER_QUERY
Open the Query
/***********end of SL 32 *******/
33 WHEN-CREATE-RECORD Description :
Fires when Oracle Forms creates a new record. For example, when the operator presses the [Insert] key, or navigates to the last record in a set while scrolling down, Oracle Forms fires this trigger.
Legal Commands: SELECT statements, unrestricted built-ins
Enter Query Mode no
Usage Notes:
Use a When-Create-Record trigger to perform an action every time Oracle Forms attempts to create a new record. This trigger also is useful for setting complex, calculated, or data-driven default values that must be specified at runtime, rather than at design-time.
On Failure : Prevents the new record from being created. Returns to the previous location, if possible.
Fires In : CREATE_RECORD
When-Create-Record Trigger Examples:
Example
This example assigns data-driven or calculated default values without marking the record as changed
DECLARE
CURSOR ship_dflt IS SELECT val
FROM cust_pref
WHERE Custid = :Customer.Custid
AND pref = 'SHIP';
BEGIN
/*
** Default Invoice Due Date based on Customer's
** Net Days Allowed value from the Customer block.
*/
:Invoice.Due_Date := SYSDATE + :Customer.Net_Days_Allowed;
/*
** Default the shipping method based on this customers
** preference, stored in a preference table. We could
** use SELECT...INTO, but explicit cursor is more
** efficient.
*/ OPEN ship_dflt;
FETCH ship_dflt INTO :Invoice.Ship_Method;
CLOSE ship_dflt;
END;
/***********end of SL 33 *******/
34 WHEN-CUSTOM-ITEM-EVENT Description : Fires whenever a JavaBean custom component in the form causes the occurrence of an event.
Legal Commands: unrestricted built-ins, restricted built-ins
Enter Query Mode:  yes
Usage Notes  :
Use a When-Custom-Item-Event trigger to respond to a selection or change of value of a custom component. The system variable SYSTEM.CUSTOM_ITEM_EVENT_PARAMETERS stores a parameter name that contains the supplementary arguments for an event that is fired by a custom control. Control event names are case sensitive
On Failure:no effect 
When-Custom-Item-Event Trigger JavaBeans Example : Ref _OTN
35 WHEN-DATABASE-RECORD /***********end of SL 34 *******/
Description:
Fires when Oracle Forms first marks a record as an insert or an update. That is, the trigger fires as soon as Oracle Forms determines through validation that the record should be processed by the next post or commit as an insert or update. This generally occurs only when the operator modifies the first item in a record, and after the operator attempts to navigate out of the item.
Legal Commands : SELECT statements, unrestricted built-ins
Enter Query Mode no
Usage Notes : Use a When-Database-Record trigger to perform an action every time a record is first marked as an insert or an update.
On Failure : no effect
/***********end of SL 35 *******/
36 WHEN-IMAGE-ACTIVATED Description:
Fires when an operator uses the mouse to
single-click on an image item
double-click on an image item
Note that When-Image-Pressed also fires on a double-click.
Legal Commands : SELECT statements, unrestricted built-ins
Enter Query Mode no
On Failure : no effect
/***********end of SL 36 *******/
37 WHEN-IMAGE-PRESSED Description :
Fires when an operator uses the mouse to:
single-click on an image item
double-click on an image item
Note that When-Image-Activated also fires on a double-click
Legal Commands : SELECT statements, unrestricted built-ins, restricted built-ins
Enter Query Mode yes
Usage Notes : Use a When-Image-Pressed trigger to perform an action when an operator clicks or double-clicks on an image item.
On Failure : no effect
/***********end of SL 37 *******/
38 WHEN-LIST-ACTIVATED Description:Fires when an operator double-clicks on an element in a list item that is displayed as a T-list.
Legal Commands : SELECT statements, unrestricted built-ins, restricted built-ins
Enter Query Mode yes
Usage Notes : A When-List-Activated trigger fires only for T-list style list items, not for drop-down lists or combo box style list items. The display style of a list item is determined by the List Style property.
On Failure : no effect
/***********end of SL 38 *******/
39 WHEN-LIST-CHANGED Description: Fires when an end user selects a different element in a list item or de-selects the currently selected element. In addition, if a When-List-Changed trigger is attached to a combo box style list item, it fires each time the end user enters or modifies entered text.
Legal Commands : SELECT statements, unrestricted built-ins, restricted built-ins
Enter Query Mode yes
Usage Notes :
Use a When-List-Changed trigger to initiate an action when the value of the list is changed directly by the end user. The When-List-Changed trigger is not fired if the value of the list is changed programmatically such as by using the DUPLICATE_ITEM Built-in, or if the end user causes a procedure to be invoked which changes the value. For example, the When-List-Changed trigger will not fire if an end user duplicates the item using a key mapped to the DUPLICATE_ITEM built-in.
On Failure : no effect
/***********end of SL 39 *******/
40 WHEN-NEW-BLOCK-INSTANCE Description :
Fires when the input focus moves to an item in a different block. Specifically, it fires after navigation to an item, when Oracle Forms is ready to accept input in a block that is different than the block that previously had the input focus.
In a multiple-form application, this trigger does not fire when focus changes from one form to another.
Legal Commands : SELECT statements, unrestricted built-ins, restricted built-ins
Enter Query Mode no
On Failure : no effect
Fires In : Return for Input
/***********end of SL 40 *******/
41 WHEN-NEW-RECORD-INSTANCE Description:
Fires when the input focus moves to an item in a record that is different than the record that previously had input focus. Specifically, it fires after navigation to an item in a record, when Oracle Forms is ready to accept input in a record that is different than the record that previously had input focus. This trigger fires whenever Oracle Forms instantiates a new record.

In a multiple-form application, this trigger does not fire when focus changes from one form to another.
Legal Commands : SELECT statements, unrestricted built-ins, restricted built-ins
Enter Query Mode yes
On Failure : no effect
Fires In  : Return for Input
/***********end of SL 41 *******/
42 WHEN-RADIO-CHANGED Description :
Fires when an operator selects a different radio button in a radio group, or de-selects the currently selected radio button, either by clicking with the mouse, or using the keyboard.
Legal Commands : SELECT statements, unrestricted built-ins, restricted built-ins
Enter Query Mode yes
Usage Notes :
Use a When-Radio-Changed trigger to perform an action depending on the state of a radio group. (De-selecting a radio button in a radio group sets the radio group value to NULL; operators use this technique in Enter Query mode to exclude a radio group from a query.)

When an operator clicks an item in a radio group, the internal value of that item does not change until navigation is completed successfully. Thus, the When-Radio-Changed trigger is the first trigger to register the changed value of a radio group. For all navigation triggers that fire before the When-Radio-Changed trigger, the value of the radio group remains as it was before the operator navigated to it.

On Failure : no effect
/***********end of SL 42 *******/
43 WHEN-REMOVE-RECORD Description : Fires whenever the operator or the application clears or deletes a record.
Legal Commands : SELECT statements, unrestricted Built-ins
Enter Query Mode no
Usage Notes : Use a When-Remove-Record trigger to perform an action every time Oracle Forms clears or deletes a record.
On Failure : Oracle Forms navigates to the block level with or without validation depending on the current operation, and puts the cursor at the target block.
Fires In :
CLEAR_RECORD
DELETE_RECORD
/***********end of SL 43 *******/
44 WHEN-TREE-NODE-ACTIVATED Description : Fires when an operator double-clicks a node or presses Enter when a node is selected.
Legal Commands : SELECT statements, unrestricted built-ins, restricted built-ins
Enter Query Mode yes
Usage Notes :
SYSTEM.TRIGGER_NODE is the node the user clicked on. SYSTEM.TRIGGER_NODE returns a value of type NODE.
No programmatic action will cause the When-Tree-Node-Activated trigger to fire. Only end-user action will generate an event.
On Failure : no effect
/***********end of SL 44 *******/
45 WHEN-TREE-NODE-EXPANDED Description : Fires when a node is expanded or collapsed.
Legal Commands : SELECT statements, unrestricted built-ins, restricted built-ins
Enter Query Mode yes
Usage Notes :
SYSTEM.TRIGGER_NODE is the node the user clicked on. SYSTEM.TRIGGER_NODE returns a value of type NODE.
No programmatic action will cause the When-Tree-Node-Espanded trigger to fire. Only end-user action will generate an event.
On Failure : no effect
/***********end of SL 45 *******/
46 WHEN-TREE-NODE-SELECTED Description : Fires when a node is selected or deselected.
Legal Commands : SELECT statements, unrestricted built-ins, restricted built-ins
Enter Query Mode yes
Usage Notes :
SYSTEM.TRIGGER_NODE is the node the user clicked on. SYSTEM.TRIGGER_NODE returns a value of type NODE.
No programmatic action will cause the When-Tree-Node-Selected trigger to fire. Only end-user action will generate an event.
On Failure : no effect
/***********end of SL 46 *******/
47 WHEN-VALIDATE-RECORD Description :
Fires during the Validate the Record process. Specifically, it fires as the last part of record validation for records with the New or Changed validation status.
Legal Commands : SELECT statements, unrestricted built-ins
Enter Query Mode no
Usage Notes :
Use a When-Validate-Record trigger to supplement Oracle Forms default record validation processing.

Note that it is possible to write a When-Validate-Record trigger that changes the value of an item in the record that Oracle Forms is validating. If validation succeeds, Oracle Forms marks the record and all of the fields as Valid and does not re-validate. While this behavior is necessary to avoid validation loops, it does make it possible for your application to commit an invalid value to the database.

On Failure : If fired as part of validation initiated by navigation, navigation fails, and the focus remains on the original item.

Fires In : Validate the Record
/***********end of SL 47 *******/
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)