Shik Mahamood Ali Forms

1

Definition Forms used for presenting and manipulating data can be developed. It is GUI used for developing client server database application. .FMB .FMT .FMX Form Module Binary Form Module Text Form Module Executable

COMPONENTS OF FORMS 1.Form Builder It is used to create a form. The design and layout of data entry screens the creations of event driven PL/SQL code used for data validation and navigate can be done via form builder. 2.Form Compiler It is required to compile the file created in form builder and create a binary file, which can be executable form runtime. 3.Form Runtime It is used to run the complied code created by forms compiler. COMPONENTS OF FORM BUILDER 1. Object Navigator It is hierarchical browsing and editing interface that enables you locate and manipulate application objects quickly and easily. 2.Property Palette It is used set and modify the properties for all objects in form modules. 3.Layout Editor It is graphical design facility for creating and arranging interface items and graphical objects in your application. 4.PL / SQL Editor It is the integrated functionality of oracle procedure builder that exists with in form builder. It provides: Development of Trigger, Procedures, Functions and Packages Development of libraries to hold PL/SQL program unit. FORM MODULE TYPES 1.Form Module It is a collection of objectives such as block, canvas, items and event based PL/SQL code blocks called trigger . 2.Menu Module It is a collection of menu items. It can be main menu or sub menu. 3.PL / SQL Libraries The library module is a collection of PL/SQL function and package stored ion a single library file. This library file is the attached to form / menu modules. All other objects in the form or menu can now access share the collection of PL/SQL functions and procedures. 4.Object Libraries

Shik Mahamood Ali 2 It is a collection of form objects that you can use in other modules. You can create it to store, maintain and distribute standard objects that can be reuse across the entire development organization. 5. Object Group (Form Builder) An object group is a container for a group of objects. You define an object group when you want to package related objects so you can copy or subclass them in another module. OBJECTS OF FORMS 1.Blocks Block is logical owner of items. It provides a mechanism for grouping related items into a functional unit for storing, displaying and manipulating records. 2.Items These are interface objects that present data values to the user or enable the user to interact with the form. 3. Canvas A canvas is the background object upon which interface items appear. 4. Frames Frames are used to arrange items with in a block. 5. Windows Windows contains for all visual objects that make up a form builder application. 6. PL/SQL Code Block It is used for event driven code. That code automatically executes when a specific event occurs. Form Built - ins 1.CLEAR_FORM Causes Form Builder to remove all records from, or flush, the current form, and puts the input focus in the first item of the first block. 2.COMMIT_FORM Causes Form Builder to update data in the database to match data in the form. Form Builder first validates the form, then, for each block in the form, deletes, inserts, and updates to the database, and performs a database commit. As a result of the database commit, the database releases all row and table locks. 3.DEBUG_MODE Toggles debug mode on and off in a menu. When debug mode is on in a menu, Form Builder issues an appropriate message when a menu item command executes. 4. ENTER Validates data in the current validation unit. (The default validation unit is Item.)

5.ERASE Removes an indicated global variable, so that it no longer exists, and releases the memory associated with the global variable. Global always allocate 255 bytes of storage. To ensure

Shik Mahamood Ali 3 that performance is not impacted more than necessary, always erase any global variable when it is no longer needs 6. EXECUTE_TRIGGER EXECUTE_TRIGGER executes an indicated trigger. 7. EXIT_FORM Provides a means to exit a form, confirming commits and specifying rollback action. 8.FIND_FORM Searches the list of forms and returns a form module ID when it finds a valid form with the given name. You must define an appropriately typed variable to accept the return value. Define the variable with a type of Form module. 9. FORM_FAILURE Returns a value that indicates the outcome of the action most recently performed during the current Runform session. Use FORM_FAILURE to test the outcome of a built–in to determine further processing within any trigger. To get the correct results, you must perform the test immediately after the action executes. That is, another action should not occur prior to the test. Example: /* ** Built–in: FORM_FAILURE ** Example: Determine if the most recently executed built–in ** failed. */ BEGIN GO_BLOCK(’Success_Factor’); /* ** If some validation failed and prevented us from leaving ** the current block, then stop executing this trigger. ** ** Generally it is recommended to test ** IF NOT Form_Success THEN ... ** Rather than explicitly testing for FORM_FAILURE */ IF Form_Failure THEN RAISE Form_Trigger_Failure; END IF; END; FORM_FATAL Returns the outcome of the action most recently performed during the current Runform session.

Use FORM_FATAL to test the outcome of a built–in to determine further processing within any trigger. To get the correct results, you must perform the test immediately after the action executes. That is, another action should not occur prior to the test. Example: /* ** Built–in: FORM_FATAL

Shik Mahamood Ali 4 ** Example: Check whether the most–recently executed built–in had a fatal error.*/ BEGIN User_Exit(’Calculate_Line_Integral control.start control.stop’); /* ** If the user exit code returned a fatal error, print a ** message and stop executing this trigger. ** ** Generally it is recommended to test ** ** IF NOT FORM_SUCCESS THEN ... ** ** Rather than explicitly testing for FORM_FATAL IF Form_Fatal THEN Message(’Cannot calculate the Line Integral due to internal error.’); RAISE Form_Trigger_Failure; END IF;

END;

FORM_SUCCESS Returns the outcome of the action most recently performed during the current Runform session. Use FORM_SUCCESS to test the outcome of a built–in to determine further processing within any trigger. To get the correct results, you must perform the test immediately after the action executes. That is, another action should not occur prior to the test. Note: FORM_SUCCESS should not be used to test whether a COMMIT_FORM or POST built–in has succeeded. Because COMMIT_FORM may cause many other triggers to fire, when you evaluate FORM_SUCCESS it may not reflect the status of COMMIT_FORM but of some other, more recently executed built–in. A more accurate technique is to check that the SYSTEM.FORM_STATUS variable is set to ’QUERY’ after the operation is done. Example: /* ** Built–in: FORM_SUCCESS ** Example: Check whether the most–recently executed built–in ** succeeded. BEGIN /* ** Force validation to occur*/ Enter; /* ** If the validation succeeded, then Commit the data. ** */ IF Form_Success THEN Commit; IF :System.Form_Status <> ’QUERY’ THEN Message(’Error prevented Commit’); RAISE Form_Trigger_Failure; END IF; END IF; END; FORMS_DDL FORMS_DDL( statement); Issues dynamic SQL statements at runtime, including server–side PL/SQL and DDL.

IF NOT Form_Success THEN Message (’Table Creation Failed’). Do not end the PL/SQL block with a slash. END LOOP..Shik Mahamood Ali 5 Note: All DDL operations issue an implicit COMMIT and will end the current transaction without allowing Oracle Forms to process any pending changes. ** Create a table with n Number columns. ELSE Message (’Table Created’). use FORMS_DDL to execute a single DML or DDL statement: Example 1: /* ** Built–in: FORMS_DDL ** Example: The expression can be a string literal. COL2.. Enclose the PL/SQL block in a valid BEGIN/END block structure. Line breaks. END IF.. If you • • • • • If you use FORMS_DDL to execute a valid PL/SQL block: Use semicolons where appropriate. END IF. /* ** Now... create the table. BEGIN my_stmt := ’create table tmp(COL1 NUMBER’. ELSE Message (’Table Created’). */ DECLARE procname VARCHAR2(30). Example 2: /* ** Built–in: FORMS_DDL ** Example: The string can be an expression or variable. BEGIN . . my_stmt := my_stmt||’)’. END. Example 3: /* ** Built–in: FORMS_DDL ** Example: The statement parameter can be a block ** of dynamically created PL/SQL code. */ PROCEDURE Create_N_Column_Number_Table (n NUMBER) IS my_stmt VARCHAR2(2000). FOR I in 2. ** TEMP(COL1. COLn). */ Forms_DDL(my_stmt). END.N LOOP my_stmt := my_stmt||’.COL’||TO_CHAR(i)||’ NUMBER’.*/ BEGIN Forms_DDL(’create table temp(n NUMBER)’).. while permitted. are not required. IF NOT Form_Success THEN Message (’Table Creation Failed’).

END IF. BEGIN IF stmt IS NULL THEN Message (’DO_SQL: Passed a null statement. as well as about the current. ELSE procname := ’Update_New_Employer’. Forms_DDL(’Begin ’|| procname ||’. ** and return a number representing the outcome of ** executing the SQL statement.flag = ’TRUE’ THEN procname := ’Assign_New_Employer’. */ FUNCTION Do_Sql (stmt VARCHAR2. ID_NULL Returns a BOOLEAN value that indicates whether the object ID is available. NEW_FORM . IF Form_Success THEN RETURN SQL_SUCCESS. END.’). Forms_DDL(stmt). END IF.’). or called form. RETURN SQL_SUCCESS. check_for_locks BOOLEAN := TRUE) RETURN NUMBER IS SQL_SUCCESS CONSTANT NUMBER := 0.’). Example 4: /* ** Built–in: FORMS_DDL ** Example: Issue the SQL statement passed in as an argument. IF Check_For_Locks AND :System. If your application is a multi-form application. END IF. ELSE RETURN Dbms_Error_Code. ELSE Message (’Employee Maintenance Successful’). End. IF NOT Form_Success THEN Message (’Employee Maintenance Failed’).Form_Status = ’CHANGED’ THEN Message (’DO_SQL: Form has outstanding locks pending. END IF. GET_FORM_PROPERTY Returns information about the given form. END. then you can call this built-in to return information about the calling form.Shik Mahamood Ali 6 IF :global. ** A result of zero represents success. RETURN SQL_SUCCESS. END IF .

updates. The data type of the name is CHAR. rollback_mode TO_SAVEPOINT Oracle Forms rolls back all uncommitted changes (including posted changes) to the current form’s savepoint. QUERY_ONLY Runs the indicated form as a query–only form.data_mode. The data type of the ID is PARAMLIST.Shik Mahamood Ali 7 Exits the current form and enters the indicated form. Oracle Forms releases memory (such as database cursors) that the terminated form was using. The calling form is terminated as the parent form. and deletes in the form. A parameter list passed to a form via NEW_FORM cannot contain parameters of type DATA_PARAMETER (a pointer to record group). Oracle Forms runs the new form with the same options as the parent form. paramlist_name . You can leave the top level form without performing a rollback. To avoid losing the locks issued by the calling form. Oracle Forms prevents any commit processing in the called form. Specify a parameter list when you want to pass parameters from the calling form to the new form. NO_ROLLBACK Oracle Forms exits the current form without rolling back to a savepoint.paramlist_name ) formmodule_name Specifies the formmodule name of the called form.) query_mode Takes one of the following constants as an argument: NO_QUERY_ONLY Runs the indicated form normally. paramlist_id Specifies the unique ID Oracle Forms assigns when it creates the parameter list.query_mode. The locks are still in effect when you regain control from Oracle Forms. which means that you retain any locks across a NEW_FORM operation. (Post–only mode can occur when your form issues a call to another form while unposted records exist in the calling form. Oracle Forms keeps the higher call active and treats it as a call to the new form. allowing the operator to perform inserts. The name must be enclosed in single quotes. These locks can also occur when invoking Oracle Forms from an external 3GL program. If the parent form was a called form. You cannot specify a FULL_ROLLBACK from a form that is running in post–only mode. Oracle Forms runs the new form with the same Runform options as the parent form. If the calling form had been called by a higher form. rollback_mode. NEW_FORM (formmodule_name VARCHAR2. FULL_ROLLBACK Oracle Forms rolls back all uncommitted changes (including posted changes) that were made during the current Runform session.

paramlist_name VARCHAR2). query_mode Takes one of the following constants as an argument: NO_QUERY_ONLY Causes Oracle Forms to run the indicated form in normal mode. HIDE is the default parameter. Oracle Forms runs the called form with the same Runform preferences as the parent form. The data type of the name is CHAR. updates. but not to insert. The name must be enclosed in single quotes. allowing the operator to perform inserts. allowing the operator to query. QUERY_ONLY Causes Oracle Forms to run the indicated form in Query Only mode. A parameter list passed to a form via NEW_FORM cannot contain parameters of type DATA_PARAMETER (a pointer to record group). and deletes from within the called form.Shik Mahamood Ali 8 The name you gave the parameter list object when you defined it. The data type of the name is CHAR. update. CALL_FORM. display NUMBER. query_mode NUMBER. CALL_FORM (formmodule_name VARCHAR2. switch_menu NUMBER. paramlist_id . Parameters: formmodule_name Specifies the formmodule name of the called form. NO_HIDE Causes Oracle Forms to display the called form without clearing the calling form from the screen. data_mode NUMBER. or delete records. When the called form is exited Oracle Forms processing resumes in the calling form at the point from which you initiated the call to CALL_FORM. switch_menu Takes one of the following constants as an argument: NO_REPLACE Causes Oracle Forms to keep the default menu application of the calling form active for the called form. Runs an indicated form while keeping the parent form active. display Specify one of the following constants as an argument: HIDE Causes Oracle Forms to clear the calling form from the screen before drawing the called form. DO_REPLACE Causes Oracle Forms to replace the default menu application of the calling form with the default menu application of the called form.

form_name. form_name. session_mode NO_SESSION Specifies that the opened form should share the same database session as the current form. paramlist_id Specifies the unique ID that Oracle Forms assigns to the parameter list at the time it is created. activate_mode ACTIVATE Sets focus to the form to make it the active form in the application. paramlist_name The name you gave the parameter list object when you defined it. separate database session should be created for the opened form. You can optionally include a parameter list as initial input to the called form. data_mode NUMBER. The data type of the name is CHAR. The current form remains current.paramlist_name).QUERY_ONLY).activate_mode.Shik Mahamood Ali 9 Specifies the unique ID Oracle Forms assigns when it creates the parameter list.activate_mode. Use the GET_PARAMETER_LIST function to return the ID to a variable of type PARAMLIST.activate_mode). activate_mode NUMBER. session_mode NUMBER.NO_HIDE.session_mode. A COMMIT operation in any form will cause validation and commit processing to occur for all forms running in the same session. Call OPEN_FORM to create multiple–form applications. paramlist_id PARAMLIST). The data type of the ID is PARAMLIST. .DO_REPLACE. form_name. Call_Form(’lookcust’.activate_mode. NO_ACTIVATE Opens the form but does not set focus to the form. OPEN_FORM( OPEN_FORM( OPEN_FORM( OPEN_FORM( OPEN_FORM( REPLACE_MENU form_name). form_name Specifies the CHAR name of the form to open.paramlist_id). OPEN_FORM Opens the indicated form. OPEN_FORM (form_name VARCHAR2.session_mode). that is. paramlist_name Specifies the CHAR name of a parameter list to be passed to the opened form. form_name.session_mode. applications that open more than one form at the same time. SESSION Specifies that a new.

Form. tm_name := Get_Application_Property(TIMER_NAME). END. the_password IN OUT VARCHAR2. Description: The GET_APPLICATION_PROPERTY built–in returns information about the current Oracle Forms application. NEW QUERY IF :System. */ PROCEDURE Get_Connect_Info( the_username IN OUT VARCHAR2. the_connect := Get_Application_Property(CONNECT_STRING).FORM_STATUS represents the status of the current form. the_password := Get_Application_Property(PASSWORD). SET_FORM_PROPERTY Sets a property of the given form. REPLACE_MENU also allows you to change the way the menu displays and the role. property. Syntax: SET_FORM_PROPERTY( formmodule_id. . END.Form_Status = ’CHANGED’THEN Commit_Form. value).Calling_Form := :System. The value can be one of three character strings: CHANGED Indicates that the form contains at least one block with a Changed record. SYSTEM. the_connect IN OUT VARCHAR2) IS BEGIN the_username := Get_Application_Property(USERNAME). value). Indicates that a query is open. SET_FORM_PROPERTY( formmodule_name.SYSTEM.Shik Mahamood Ali 10 Replaces the current menu with the specified menu. Indicates that the form contains only New records.System Variables 1. PROCEDURE STORE_FORMNAME IS BEGIN :GLOBAL. Example 2: /* ** Built–in: GET_APPLICATION_PROPERTY ** Example: Capture the username and password of the ** currently logged–on user. but does not make the new menu active.Current_Form. The value is always a character string. The form contains at least one block with QUERY records and no blocks with CHANGED records. 2. property. You must call this built–in once for each value you want to retrieve.FORM_STATUS SYSTEM.FORM_STATUS becomes CHANGED only after at least one record in the form has been changed and the associated navigation unit has also changed.CURRENT_FORM SYSTEM. for use in calling ** another Tool. The value of SYSTEM.CURRENT_FORM represents the name of the form that Form Builder is executing.

or transactional triggers.Shik Mahamood Ali END IF. QUERY Indicates that the form is currently in fetch processing mode. A multi-record block displays more than one record at a time. /* ** When–New–Item–Instance Trigger */ BEGIN IF :System. and the items in a control block do not relate to table columns within a database. SYSTEM. ENTER-QUERY Indicates that the form is currently in Enter Query mode.Cursor_Item = ’EMP. END IF. displaying and manipulating records. procedures.MODE indicates whether the form is in Normal. . In addition. The value is always a character string. By default. a data block can also be a master or detail block: Master block displays a master record associated with detail records displayed in a detail block. 3. meaning that a query is currently being processed. Enter Query. A detail block displays detail records associated with a master record displayed in master block.EMPNO’ and :System. or Fetch Processing mode. END. Clear_Form. Data blocks can be based on database tables. BLOCKS Block is logical owner of items. End if. All blocks are either single-record or multi-record blocks: A single-record block displays one record at a time. It provides a mechanism for grouping related items into a functional unit for storing.Mode = ’ENTER–QUERY’ THEN IF NOT Show_Lov(’my_lov’) THEN RAISE Form_Trigger_Failure. and delete rows within a database. MODE 11 SYSTEM. update. Data Blocks Data blocks are associated with data (table columns) within a database. Types of Blocks 1. insert. 2. the association between a data block and the database allows operators to automatically query. NORMAL Indicates that the form is currently in normal processing mode. The following trigger accomplishes that operation. Example: Assume that you want Oracle Forms to display an LOV when the operator enters query mode and the input focus is in a particular text item. views. Control Blocks A control block is not associated with the database.

and flushes the current block without prompting the end user. You must define an appropriately typed variable to accept the return value. GET_BLOCK_PROPERTY Returns information about a specified block.Cursor_Block.Cursor_Block <> prev_blk THEN Message(’You successfully navigated to a new block!’). IF :System. NO_COMMIT Form Builder validates the changes and flushes the current block without performing a commit or prompting the end user. Syntax: GET_BLOCK_PROPERTY( block_id." the current block. DO_COMMIT Form Builder validates the changes. Define the variable with a type of Block. GET_BLOCK_PROPERTY( block_name. END. or "flush. or prompting the end user. performs a commit. property). . Clear_Block(No_Validate). */ DECLARE prev_blk VARCHAR2(40) := :System. 3. 2.ins 1. You must issue a call to the built-in once for each property value you want to retrieve.Shik Mahamood Ali Block Built . committing the changes. and prints a message if ** the user chooses a new block out of the list to ** which to navigate. Form Builder sets the input focus to the first enterable item in the block you select from the LOV. COMMIT_MODE The optional action parameter takes the following possible constants as arguments: ASK_COMMIT Form Builder prompts the end user to commit the changes during CLEAR_BLOCK processing. 4. BEGIN BLOCK_MENU. END IF. Example: /* ** Built–in: BLOCK_MENU ** Example: Calls up the list of blocks in the form when the ** user clicks a button. CLEAR_BLOCK built-in Causes Form Builder to remove all records from. NO_VALIDATE Form Builder flushes the current block without validating the changes. BLOCK_MENU built-in 12 Displays a list of values (LOV) containing the sequence number and names of valid blocks in your form. FIND_BLOCK Searches the list of valid blocks and returns a unique block ID. property).

*/ cur_rec := Get_Block_Property( bk_id. Set_Block_Property(blk_id. BEGIN /* Lookup the block’s internal ID */ blk_id := Find_Block(blk_name).PROPERTY_FALSE). Set_Block_Property(blk_id. Otherwise signal ** an error. */ IF NOT Id_Null(blk_id) THEN Set_Block_Property(blk_id. */ PROCEDURE Make_Block_Query_Only( blk_name IN VARCHAR2 ) IS blk_id Block. /* ** If the block exists (ie the ID is Not NULL) then set ** the three properties for this block.SET_BLOCK_PROPERTY Sets the given block characteristic of the given block. ID_NULL Returns a BOOLEAN value that indicates whether the object ID is available.DELETE_ALLOWED. property.Shik Mahamood Ali 13 ** Determine the (1) Current Record the cursor is in. and deletes to ** queried records in the block whose name is ** passed as an argument to this procedure. Example: /* ** Built–in: SET_BLOCK_PROPERTY ** Example: Prevent future inserts. value). an error occurs.PREVIOUS_BLOCK Navigates to the first navigable item in the previous enterable block in the navigation sequence 9. property. top_rec := Get_Block_Property( bk_id. TOP_RECORD). SET_BLOCK_PROPERTY( block_name. GO_BLOCK GO_BLOCK navigates to an indicated block. value). ELSE . 6.INSERT_ALLOWED. 5. ** (2) Current Record which is visible at the ** first (top) line of the multirecord ** block. 7. updates. NEXT_BLOCK Navigates to the first navigable item in the next enterable block in the navigation sequence 8.PROPERTY_FALSE).PROPERTY_FALSE).UPDATE_ALLOWED. Syntax: SET_BLOCK_PROPERTY( block_id. CURRENT_RECORD). If the target block is non-enterable .

and Post. the value of SYSTEM. the value of SYSTEM. . Record.CURSOR_BLOCK system variable represents depends on the current navigation unit: If the current navigation unit is the block.CURSOR_BLOCK The value that the SYSTEM.and Post. The value can be one of three character strings: CHANGED NEW QUERY Indicates that the block contains at least one Changed record. If the current navigation unit is the form (as in the Pre.Shik Mahamood Ali 14 Message(’Block ’||blk_name||’ does not exist. The following Key–CLRBLK trigger performs this function.’). record. the value of SYSTEM.System Variables 1. The value is always a character string.BLOCK_STATUS represents the status of a Data block where the cursor is located. Indicates that the block contains only Valid records that have been retrieved from the database.CURSOR_BLOCK is the name of the block where the cursor is located.CURRENT_BLOCK is the name of the block that Form Builder is processing or that the cursor is in. Block . the value of SYSTEM. 2.SYSTEM. 3.CURRENT_BLOCK is NULL. or item (as in the Pre.SYSTEM.SYSTEM.Item.CURRENT_BLOCK system variable represents depends on the current navigation unit: If the current navigation unit is the block.and Post-Form triggers). Indicates that the block contains only New records. END IF.Item.CURSOR_BLOCK is NULL. Clear_Block.CURRENT_BLOCK The value that the SYSTEM. and Block triggers). IF :System. or the current data block during trigger processing.Block_Status = ’CHANGED’ THEN Commit_Form.and Post-Form triggers). RAISE Form_Trigger_Failure. END. or item (as in the Pre. Record. If the current navigation unit is the form (as in the Pre.BLOCK_STATUS SYSTEM. and Block triggers). record. END IF. Example: Assume that you want to create a trigger that performs a commit before clearing a block if there are changes to commit within that block.

Go_Block(Name_In(’System. The following statement performs this function.Cursor_Block. END. Block – Based Triggers [Block Processing Trigger] When-Create-Record.MASTER_BLOCK This system variable works with its companion SYSTEM. What Is a Relation? . 5. When-Clear-Block. 4. using :SYSTEM. When-Remove-Record MASTER-DETAIL RELATIONSHIP A master-detail relationship is an association between two data blocks that reflects a primaryforeign key relationship between the database tables on which the two data blocks are based. When-Database-Record. The value is NULL if the current trigger is a Pre.Shik Mahamood Ali Example: 15 Assume that you want to create a Key–NXTBLK trigger at the form level that navigates depending on what the current block is. ELSIF curblk = ’ITEMS’ THEN Go_Block(’CUSTOMERS’).Trigger_Block’)). ELSIF curblk = ’CUSTOMERS’ THEN Go_Block(’ORDERS’).TRIGGER_BLOCK SYSTEM. A master-detail relationship equates to the one-tomany relationship in the entity relationship diagram.or Post-Form trigger. END IF.TRIGGER_BLOCK represents the name of the block where the cursor was located when the current trigger initially fired. SYSTEM. and the detail data block is based on the table with the foreign key. A Detail Block Can Be a Master You can create block relationships in which the detail of one master-detail link is the master for another link.CURSOR_BLOCK stored in a local variable. BEGIN curblk := :System. IF curblk = ’ORDERS’ THEN Go_Block(’ITEMS’). DECLARE curblk VARCHAR2(30).COORDINATION_OPERATION to help an On-Clear-Details trigger determine what type of coordination-causing operation fired the trigger. SYSTEM. The master data block is based on the table with the primary key. Example: Assume that you want to write a form–level procedure that navigates to the block where the cursor was when the current trigger initially fired. The following trigger performs this function. The value is always a character string. and on which master block of a master/detail relation.

Explicit Relations If a relation is not established when default blocks are created. S_ORD_S_ITEM. propagate.Delete trigger. PL/SQL program units and triggers are created automatically when you explicitly create a relation.Shik Mahamood Ali 16 A relation is a Form Builder object that handles the relationship between two associated blocks. you can delete all corresponding line items when an order is deleted. This relation is named masterblock_detailblock. Changing the Master Deletes property from the default of Non-Isolated to Isolated results in the removal of the On-Check-Delete-Master trigger. You can create a relation either: • Implicitly with a master-detail form module • Explicitly in the Object Navigator Implicit Relations When you create a master-detail form module. MASTER DELETES PROPERTY RESULTING TRIGGERS Non-Isolated (the default) On-Check-Delete-Master On-Clear-Details On-Populate-Details Cascading On-Clear-Details On-Populate-Details Pre-Delete Isolated On-Clear-Details On-Populate-Details . or isolate deletion of a record in a master block when corresponding records exist in the detail block by setting the Master Deletes property. you can create your own by setting the properties in the New Relation dialog box. Master Deletes You can prevent. a relation is automatically created. for example. For example. Like implicitly created relations. Property Use    Non-Isolated Cascading Isolated Prevents the deletion of the master record when the detail records exist Deletes the detail records when a master record is deleted Deletes only the master record What Happens When You Modify a Relation? • • Changing the Master Deletes property from the default of Non-Isolated to Cascading replaces the On-Check-Delete-Master trigger with the Pre.

To fetch the detail records. Prevent Masterless Operation Ensures that the detail data block cannot be queried or used to insert records when a master record is not currently displayed. Non-query record group A non-query record group is a group that does not have an associated query. The columns in a query record group derive their default names. and lengths from the database columns referenced in the SELECT statement. When a coordination-causing event occurs. On-Populate-Details. On-Clear-Details RECORD GROUP This object represents an internal Form Builder data structure that has a column/row framework similar to a database table. the operator must navigate to the detail data block and explicitly execute a query. the detail records are fetched immediately. The records in a query record group are the rows retrieved by the query associated with that record group. Deferred Without Auto Query When coordination-causing event occurs. Query record groups can be created and modified at design time or at runtime. (Deferred False. For example.Shik Mahamood Ali Coordination 17 You can control how the detail records are displayed when a master block is queried by setting the coordination property. Oracle Forms does not automatically fetch the detail records. Join Condition Use to: • • • • • Create links between blocks using SQL Alter links between blocks using SQL Define using: Usual SQL equi-join condition syntax Block names instead of the base table names Item names that exist in the form module instead of base table column names  Master-detail triggers On-Check-Delete-Master. Default [Immediate] The default setting. Auto-Query False) Deferred with Auto Query Oracle Forms defers fetching the associated detail records until the operator navigates to the detail data block. but whose structure and values can be modified programmatically at runtime. you can defer querying the line items for an order until the operator navigates to the item block. Static record group . data types. Non-query record groups can be created and modified only at runtime. Query record group A query record group is a record group that has an associated SELECT statement.

row_number Adds a row to the given record group. groupcolumn_name VARCHAR2. NUMBER). the appropriate memory is freed and available to Form Builder. . Form Builder automatically decrements the row numbers of all rows that follow a deleted row. Static record groups can be created and modified only at design time.Shik Mahamood Ali 18 A static record group is not associated with a query. Populating Groups: POPULATE_GROUP (recordgroup_id RecordGroup). Executes the query associated with the given record group and returns a number indicating success or failure of the query.column_type NUMBER. query VARCHAR2) Populates a record group with the given query. The record group has columns representing each column you include in the select list of the query C] DELETE_GROUP (recordgroup_name VARCHAR2).cell_value VARCHAR2) Sets the value for the record group cell identified by the given row and column. array_fetch_size NUMBER). instead. POPULATE_GROUP returns a 0 (zero). Creates a record group with the given name. An unsuccessful query generates an ORACLE error number that corresponds to the particular SELECT statement failure. scope NUMBER. DELETE_GROUP_ROW (recordgroup_id RecordGroup. cell_value DATE). SET_GROUP_DATE_CELL (groupcolumn_id GroupColumn.row_number NUMBER. The rows that are retrieved as a result of a successful query replace any rows that exist in the group. Modifying a group's structure: ADD_GROUP_COLUMN (recordgroup_name VARCHAR2. Upon a successful query. row_number NUMBER) Deletes the indicated row or all rows of the given record group. The record group is cleared and rows that are fetched replace any existing rows in the record group. you define its structure and row values at design time. Deletes a programmatically created record group. scope NUMBER. Sets the value for the record group cell identified by the given row and column. When rows are deleted. Record Group built-in subprograms Creating and deleting groups: A] CREATE_GROUP (recordgroup_name VARCHAR2. and they remain fixed at runtime. ADD_GROUP_ROW (recordgroup_name VARCHAR2. SET_GROUP_CHAR_CELL(groupcolumn_id GroupColumn. POPULATE_GROUP_WITH_QUERY (recordgroup_id RecordGroup. array_fetch_size NUMBER) Creates a non-query record group with the given name B] CREATE_GROUP_FROM_QUERY (recordgroup_name VARCHAR2. query VARCHAR2. row_number NUMBER. column_width NUMBER) Adds a column of the specified type to the given record group.

Shik Mahamood Ali 19 SET_GROUP_NUMBER_CELL(groupcolumn_id GroupColumn. GET_GROUP_DATE_CELL (function) GET_GROUP_NUMBER_CELL (function) Processing rows: GET_GROUP_ROW_COUNT (function) GET_GROUP_SELECTION_COUNT (function) GET_GROUP_SELECTION (function) RESET_GROUP_SELECTION (procedure) SET_GROUP_SELECTION (procedure) UNSET_GROUP_SELECTION (procedure) Object ID functions: FUNCTION FIND_GROUP (recordgroup_name VARCHAR2). gc_id := Add_Group_Column(rg_id.cell_value NUMBER). errcode NUMBER. /* ** If it does not exist. row_number NUMBER. BEGIN /* ** Make sure the record group does not already exist. END IF.*/ DECLARE rg_name VARCHAR2(40) := ’Salary_Range’. create it and add the two ** necessary columns to it. FIND_COLUMN (function) Example: /* ** Built–in: CREATE_GROUP ** Example: Creates a record group and populates its values ** from a query. Getting cell values: GET_GROUP_CHAR_CELL (groupcolumn_id GroupColumn. You must define an appropriately typed variable to accept the return value. */ rg_id := Find_Group(rg_name). A cell is an intersection of a row and column. Searches the list of record groups and returns a record group ID when it finds a valid group with the given name. */ IF Id_Null(rg_id) THEN rg_id := Create_Group(rg_name). /* Add two number columns to the record group */ gc_id := Add_Group_Column(rg_id. NUMBER_COLUMN). Define the variable with a type of RecordGroup. ’Emps_In_Range’. Sets the value for the record group cell identified by the given row and column. rg_id RecordGroup. Returns the VARCHAR2 or LONG value for a record group cell identified by the given row and column. gc_id GroupColumn. ’Base_Sal_Range’. row_number NUMBER). /* ** Populate group with a query . NUMBER_COLUMN).

SHOW_LOV( lov_name). and returns TRUE if the operator selects a value from the list. Default Key for LOV – F9 LOVs provide the following functionality:  LOVs can be displayed by end user request (when an LOV is available). independent of any specific text item. ’SELECT SAL–MOD(SAL. SHOW_LOV( lov_id. and FALSE if the operator Cancels and dismisses the list. x. END IF. y). The list of values remains displayed until the operator dismisses the LOV or selects a value.COUNT(EMPNO) ’ ||’FROM EMP ’ ||’GROUP BY SAL–MOD(SAL. as long as the input focus is in a text item that has an attached LOV. RAISE Form_Trigger_Failure.Shik Mahamood Ali 20 */ errcode := Populate_Group_With_Query( rg_id. Bell.   At design time.’). SHOW_LOV( lov_name.1000). IF NOT a_value_chosen THEN Message(’You have not selected a value. LOV [ LIST OF VALUES ] An LOV is a scrollable popup window that provides the end user with either a single or multi-column selection list. BEGIN a_value_chosen := Show_Lov(’my_employee_status_lov’). or programmatically. LOV values are derived from record groups.LIST_VALUES LIST_VALUES displays the list of values for the current item. Example: /* ** Built–in: SHOW_LOV ** Example: Display a named List of Values (LOV) */ DECLARE a_value_chosen BOOLEAN.1000) ’ ||’ORDER BY 1’).SHOW_LOV Displays a list of values (LOV) window at the given coordinates.  LOV values that are selected by the end user can be assigned to form items according to the return items you designate.  LOV auto-reduction and search features allow end users to locate specific values. y). LOV Built-in subprograms 1. x. END. SHOW_LOV( lov_id). an LOV can be attached to one or more text items in the form. LOV Properties . 2. when the end user navigates to a text item with an associated LOV.

>If it is not specified then value from Lov cannot assigned to the block. SET_LOV_PROPERTY(lov_id LOV. value NUMBER). the LOV remains displayed. LOV.Automatic Display property Specifies whether Form Builder displays the LOV automatically when the operator or the application navigates into a text item to which the LOV is attached. property 5. In this dialog box any value can be entered. GET_LOV_PROPERTY (lov_id. Long List It is used to append a ‘ where clause ‘ to the select statement.'new_group'). 4. the LOV is dismissed automatically and column values from the single row are assigned to their corresponding return items. SET_LOV_COLUMN_PROPERTY (lov_id NUMBER.Automatic Select property Specifies what happens when an LOV has been invoked and the user reduces the list to a single choice when using auto-reduction or searching: When Automatic Confirm is set to Yes. When this property is true a dialog box appear. property LOV). 12. giving the operator the option to explicitly select the remaining choice or dismiss the LOV.Shik Mahamood Ali 21 1. When Automatic Confirm is set to No. Sets the given LOV property for the given LOV. 11. 3. 6. 9. property NUMBER. 8.GROUP_NAME Specifies the name of the record group on which an LOV is based. When Automatic Skip is set to No.Automatic Refresh property Determines whether Form Builder re-executes the query to populate an LOV that is based on a query record group. 2. . 7. the focus remains in the text item after the operator makes a selection from the LOV. SET_LOV_COLUMN_PROPERTY Sets the given LOV property for the given LOV.Title property Specifies the title to be displayed for the object. 10.GROUP_NAME.Column Mapping This property is used to specify the return item. Set_LOV_Property('my_lov'.colnum NUMBER.Validation from Lov to text item. Automatic Skip (LOV) property Moves the cursor to the next navigable item when the operator makes a selection from an LOV to a text item. LOV for Validation [ Yes / No ] If it is true so that the system check value entered with the list of values Validation from LOV – text item property . from this value entered the where clause constructed.value VARCHAR2). Returns information about a specified list of values (LOV).

or the VARCHAR2 name of the parameter list. key VARCHAR2. Types 1. PARAMETER LIST List of Parameter or list that contains parameter names and their values Input values required for a form as startup are provided by parameters. ADD_PARAMETER (list VARCHAR2. Returns the current value and type of an indicated parameter in an indicated parameter list. DELETE_PARAMETER (list VARCHAR2. list or name Specifies the parameter list. paramtype NUMBER. and an associated value. its type. is of little value since it merely duplicates default Form Builder functionality.PROCEDURE DESTROY_PARAMETER_LIST (list VARCHAR2) Deletes a dynamically created parameter list and all parameters it contains. Data Parameter It is name of the record group present in the current form.Shik Mahamood Ali 22 Key-LISTVAL Trigger: List_Values. GET_PARAMETER_ATTR (list VARCHAR2. but before Form Builder returns to the normal event sequence. 2. an IF statement is added to the previous trigger: Key-LISTVAL Trigger: List_Values. Data type – char – 2555 char maximum Global variables are visible across multiple forms Parameter values are not visible across multiple forms. . Each parameter consists of a key. 2. It is passed between oracle products.id IS NULL THEN Go_Item ('customer. key VARCHAR2. either by list ID or name.CREATE_PARAMETER_LIST (name VARCHAR2). as written. The value of the text parameter is a character string. 3. In the following example. Parameter – Built Ins 1. But not between forms. key 4. 5. using a Key-LISTVAL trigger allows you to add subsequent PL/SQL statements that execute after the LOV is displayed. key VARCHAR2) Deletes the parameter with the given key from the parameter list. However.value VARCHAR2). Adds parameters to a parameter list. IF :customer. VARCHAR2). The name of the parameter. Text Parameter It is passed between forms.id'). Creates a parameter list with the given name. This trigger. It can also passed between different oracle products. paramtype VARCHAR2. The actual parameter can be either a parameter list ID of type PARAMLIST. END IF. The data type of the key is VARCHAR2.

Form Builder returns a message to the end user. REPORTS specifies Oracle Reports. product Specifies a numeric constant for the Oracle product you want to invoke: FORMS specifies a Runform session. key VARCHAR2. The actual parameter you supply must be a variable of type NUMBER. RUN_PRODUCT( product. execmode.SET_PARAMETER_ATTR (list PARAMLIST. If the parameter is a data type parameter. The actual parameter can be either a parameter list ID of type PARAMLIST. the value is the name of a record group. SYNCHRONOUS specifies that control returns to Oracle Forms only after the called product has been exited.Shik Mahamood Ali 23 list or name Specifies the parameter list to which the parameter is assigned. The operator cannot work in the form while the called product is running. Oracle Graphics display. execmode. display). ASYNCHRONOUS specifies that control returns to the calling application immediately.list. Valid values are the name of a form module. Syntax: RUN_PRODUCT( product. If the called product is unavailable at the time of the call. location. TEXT_PARAMETER Indicates that the parameter's value is an actual data value. location. Valid numeric constants for this parameter are SYNCHRONOUS and ASYNCHRONOUS. GRAPHICS specifies Oracle Graphics. Paramtype An OUT parameter of type NUMBER. report. Executing the parameter sets the value of the variable to one of the following numeric constants: DATA_PARAMETER Indicates that the parameter's value is the name of a record group.name. and cannot be an expression. or Oracle Book document. display). paramtype NUMBER) Sets the type and value of an indicated parameter in an indicated parameter list. BOOK specifies Oracle Book. or the VARCHAR2 name of the parameter list. RUN_PRODUCT built-in Invokes one of the supported Oracle tools products and specifies the name of the module or module to be run. document. The application looks for the module or document in the default paths defined for the called product. even if the called application has not completed its display. the value is an actual text parameter. document Specifies the CHAR name of the document or module to be executed by the called product. commmode Specifies the communication mode to be used when running the called product. Value An OUT parameter of type VARCHAR2. commmode. document. If the parameter is a text parameter. commmode. Key The VARCHAR2 name of the parameter. . 6.

) Note: You can pass text parameters to called products in both SYNCHRONOUS and ASYNCHRONOUS mode. When you run Oracle Reports and Oracle Graphics. Example: /* ** Built–in: RUN_PRODUCT ** Example: Call an Oracle Reports 2. then delete it before we create it again in ** case it contains parameters that are not useful for our ** purposes here. use a variable of type PARAMLIST. or NULL.Shik Mahamood Ali execmode 24 Specifies the execution mode to be used when running the called product. the ID of the parameter list. (SYNCHRONOUS mode is required when invoking Oracle Graphics to return an Oracle Graphics display that will be displayed in a form chart item. Note: You cannot pass a DATA_PARAMETER to a child query in Oracle Reports. The name of the chart item must be specified in the format block_name.item_name. Valid numeric constants for this parameter are BATCH and RUNTIME. */ . When you run Oracle Forms. (This parameter is only required when you are using an Oracle Graphics chart item in a form. Valid values for this parameter are the CHAR name of the parameter list.) Note: You can prevent Oracle Graphics from logging on by passing a parameter list that includes a parameter with key set to LOGON and value set to NO.5 report. location Specifies the location of the document or module you want the called product to execute. either the file system or the database. or graph) generated by Oracle Graphics. list or name Specifies the parameter list to be passed to the called product. Data passing is supported only for master queries. always set execmode to RUNTIME. ** Presumes the Emp_Recs record group already ** exists and has the same column/data type ** structure as the report’s Emp_Query query. To specify a parameter list ID. execmode can be either BATCH or RUNTIME. bar chart. parameter lists that contain parameters of type DATA_PARAMETER (pointers to record groups) can only be passed to Oracle Reports and Oracle Graphics in SYNCHRONOUS mode. display Specifies the CHAR name of the Oracle Forms chart item that will contain the display (such as a pie chart. passing the ** data in record group ’EMP_RECS’ to substitute ** for the report’s query named ’EMP_QUERY’. However. /* ** If it does. */ pl_id := Get_Parameter_List(’tmpdata’). BEGIN /* ** Check to see if the ’tmpdata’ parameter list exists. Valid constants for this property are FILESYSTEM and DB. */ PROCEDURE Run_Emp_Report IS pl_id ParamList.

IF Id_Null(pl_id) THEN pl_id := Create_Parameter_List(pl_name).TEXT_PARAMETER. passing the parameter list */ Run_Product(REPORTS. pl_name VARCHAR2(10) := ’tempdata’. DATA_PARAMETER.FILEYSTEM.DATA_PARAMETER. RUNTIME. First ** make sure the list does not already exist. and the record group named ** ’EMP_RECS’ in the form. Example: /* ** Built–in: ADD_PARAMETER ** Example: Add a value parameter to an existing Parameter ** List ’TEMPDATA’. RAISE Form_Trigger_Failure. /* ** Create the ’tmpdata’ parameter list afresh. then ** attempt to create a new list.’19’). pl_id. NULL).’number_of_copies’. Add_Parameter(pl_id. /* ** Run the report synchronously. ELSE Message(’Parameter list ’||pl_name||’ already exists!’). ’empreport’. BEGIN pl_id := Get_Parameter_List(pl_name). Example: /* ** Built–in: CREATE_PARAMETER_LIST ** Example: Create a parameter list named ’TEMPDATA’. Example: /* ** Built–in: DELETE_PARAMETER ** Example: Remove the ’NUMBER_OF_COPIES’ parameter from the ** already existing ’TEMPDATA’ parameter list. */ DECLARE pl_id ParamList. END. */ pl_id := Create_Parameter_List(’tmpdata’). ’dept_recordgroup’).’EMP_RECS’). . BEGIN pl_id := Get_Parameter_List(’tempdata’).’EMP_QUERY’. END IF. END IF. /* ** Add a data parameter to this parameter list that will ** establish the relationship between the named query ** ’EMP_QUERY’ in the report. END. END IF. IF Id_Null(pl_id) THEN Message(’Error creating parameter list ’||pl_name). END IF. Signal an error ** if the list already exists or if creating the ** list fails. then add a data parameter to ** the list to associate named query ’DEPT_QUERY’ ** with record group ’DEPT_RECORDGROUP’.Shik Mahamood Ali 25 IF NOT Id_Null(pl_id) THEN Destroy_Parameter_List( pl_id ). RAISE Form_Trigger_Failure. */ DECLARE pl_id ParamList. SYNCHRONOUS. */ Add_Parameter(pl_id. ’dept_query’. END. IF NOT Id_Null(pl_id) THEN Add_Parameter(pl_id.

rdf’. */ Run_Product(REPORTS. BEGIN pl_id := Get_Parameter_List(’tempdata’). –– pl ). Example 2: PROCEDURE Run_Report_For_Last_Query IS pl ParamList. –– /* Delete the parameter list */ Destroy_Parameter_List(pl). IF NOT Id_Null(pl_id) THEN Destroy_Parameter_List(pl_id). /* ** Get the Where Clause from the Last Query ** using a user–defined function */ wc := Last_Where_Clause. ’the_Where_Clause’. In this case the report definition has ** a parameter named ’the_Where_Clause’ that ** it’s expecting. The The The The The The Product to call name of the report definition communications mode Execution Mode Location of the reports document Handle to the parameter list –– –– –– –– –– Handle to the ParamList Name of Parameter in the Report Type of Parameter String Value for Parameter END. wc ). End. passing parameters in the ** parameter list. –– The Where Clause to Pass BEGIN /* ** Create a parameter list for parameter passing */ pl := Create_Parameter_List(’tmp’). END IF. –– BATCH. . –– ’rep0058. /* ** Launch the report. –– FILESYSTEM. END IF. –– SYNCHRONOUS.’number_of_copies’). */ IF wc IS NOT NULL THEN Add_Parameter(pl. add a text parameter to the parameter ** list to specify the parameter name and its ** value. END. wc VARCHAR2(2000). Example: /* ** Built–in: DESTROY_PARAMETER_LIST ** Example: Remove the parameter list ’tempdata’ after first ** checking to see if it exists */ DECLARE pl_id ParamList.Shik Mahamood Ali 26 */ BEGIN Delete_Parameter(’tempdata’. TEXT_PARAMETER. /* ** If there is a Non–NULL Last Where clause to ** pass.

and PostItem. SYSTEM. or item (as in the Pre. and on which master block of a master/detail relation.Shik Mahamood Ali 27 Referencing Form Builder items indirectly 1.BLOCK_STATUS SYSTEM. the value of SYSTEM.COORDINATION_OPERATION This system variable works with its companion SYSTEM. COPY(NAME_IN(source).SYSTEM.direct reference IF NAME_IN('emp. Record. 'Emp. erase(‘global.CURRENT_BLOCK s The value that the SYSTEM. destination).a’). IF :emp. and Block triggers). 1. or the current data block during trigger processing.CURRENT_BLOCK system variable represents depends on the current navigation unit: If the current navigation unit is the block.BLOCK_STATUS represents the status of a Data block where the cursor is located.MASTER_BLOCK to help an OnClear-Details trigger determine what type of coordination-causing operation fired the trigger. cur_val VARCHAR2(40). Copy( cur_val.NAME_IN The NAME_IN function returns the contents of an indicated variable or item. Use the NAME_IN function to get the value of an item without referring to the item directly. Destroy global variable System Variable 1.Local Variables The local variable is PL/SQL variable whose value is only accessible with in the trigger or user named sub Programs 2.ename = 'smith' -. 2. that the block contains only New records. .COPY built-in Copies a value from one item or variable into another item or global variable.System Variable It is used to track of runtime status condition. record.ename') = 'smith' -. SYSTEM.Global Variable Whose value is accessible to trigger and subprograms in any modules – limit – 255 char length 3. The value can be one of three character strings: CHANGED NEW QUERY Indicates Indicates Indicates retrieved that the block contains at least one Changed record. that the block contains only Valid records that have been from the database.Empno' ).CURRENT_BLOCK is the name of the block that Form Builder is processing or that the cursor is in.indirect reference 2. 3. VARIABLES It is used to store values from form items.

FORM_STATUS becomes CHANGED only after at least one record in the form has been changed and the associated navigation unit has also changed. SYSTEM. and on which master block of a master/detail relation. The value is always a character string. 7. Indicates that a query is open. The value is a CHAR string in the following format: DD-MON-YYYY HH24:MM:SS 5.CURSOR_ITEM SYSTEM. or Fetch Processing mode.FORM_STATUS SYSTEM. The value is always a character string. Enter Query. block. the value of SYSTEM. The value is always a character string.CURRENT_FORM represents the name of the form that Form Builder is executing. 11. SYSTEM. item. The value can be one of three character strings: CHANGED Indicates that the form contains at least one block with a Changed record.CURRENT_DATETIME is a variable representing the operating system date.CURRENT_DATETIME SYSTEM. where the input focus (cursor) is located. Indicates that the form contains only New records. The value is always a character string. SYSTEM.COORDINATION_OPERATION to help an On-Clear.LAST_QUERY SYSTEM. SYSTEM.LAST_QUERY represents the query SELECT statement that Form Builder most recently used to populate a block during the current Runform session.CURSOR_ITEM represents the name of the block and item.Shik Mahamood Ali 28 If the current navigation unit is the form (as in the Pre.CURRENT_FORM SYSTEM. 6. 12.CURSOR_VALUE SYSTEM. SYSTEM. 9. The value is always a character string. SYSTEM.MODE s SYSTEM. 4.and Post-Form triggers).CURSOR_VALUE represents the value of the item where the cursor is located.MASTER_BLOCK This system variable works with its companion SYSTEM.Details trigger determine what type of coordination-causing operation fired the trigger. SYSTEM. This number represents the record's current physical order in the block's list of records. The value is always a character string. 8. SYSTEM.MODE indicates whether the form is in Normal. The form contains at least one block with QUERY records and no blocks with CHANGED records.CURRENT_BLOCK is NULL. SYSTEM.FORM_STATUS represents the status of the current form.CURSOR_RECORD SYSTEM. NEW QUERY 10.CURSOR_RECORD represents the number of the record where the cursor is located. . The value of SYSTEM.

MOUSE_ITEM represents the name of that item as a CHAR value. 13. SYSTEM. The value is always a character string.or Post-Form trigger. Indicates that the form is currently in fetch processing mode. 16. 15. The Property Palette is where you set the properties of objects you create in form and menu modules. SYSTEM.TRIGGER_BLOCK SYSTEM.Shik Mahamood Ali NORMAL ENTER-QUERY QUERY 29 Indicates that the form is currently in normal processing mode. SYSTEM. Indicates that the form is currently in Enter Query mode. When referenced in a key trigger.MOUSE_ITEM If the mouse is in an item.MOUSE_ITEM is :BLOCK2.    14. For example. The value is always a character string. SYSTEM. the value for SYSTEM. Indicates that the record's validation status is Valid and that it was retrieved from the database. Indicates that the record's validation status is Changed and that the record does not exist in the database. if the mouse is in Item1 in Block2. Indicates that the record's validation status is New. then moves the mouse the platform is not a GUI platform. Once you create a property class you can base other objects on it. VISUAL ATTRIBUTES . SYSTEM. The value can be one of four character strings: CHANGED INSERT NEW QUERY Indicates that a queried record's validation status is Changed.ITEM1.TRIGGER_BLOCK represents the name of the block where the cursor was located when the current trigger initially fired. SYSTEM.ITEM) in the scope for which the trigger is currently firing. b.RECORD_STATUS represents the status of the record where the cursor is located.MOUSE_ITEM is NULL if: the mouse is not in an item the operator presses the left mouse button. The value is NULL if the current trigger is a Pre.RECORD_STATUS SYSTEM. There are 2 ways to creating property class a.TRIGGER_ITEM SYSTEM. Object Navigator method.TRIGGER_ITEM represents the item (BLOCK. it represents the item where the cursor was located when the trigger began. An object based on a property class can inherit the settings of any property in the class that is appropriate for that object. PROPERTY CLASS This object is a named object that contains a list of properties and their associated settings. Property Window method Property class can not be change programmatically. meaning that a query is currently being processed.

EXE 2. 2. much like styles in a word processing program. and pattern properties that you set for form and menu objects that appear in your application's interface. 3. system editor. pattern. The actual settings are determined by a combination of factors. Visual attributes can include the following properties: Font properties: Font Name. A named visual attribute is a separate object in a form or menu module that defines a collection of visual attribute properties. Font Size. refer to the Form Builder documentation for your operating system. the individual attribute settings reflect the current system defaults. you can apply it to any object in the same module. color. 1. When Visual Attribute Group is set to Default. Default Setting the Visual Attribute Group property to Default specifies that that the object should be displayed with default color. Named Setting the Visual Attribute Group property to a named visual attribute defined in the same module specifies that the object should use the attribute settings defined for the named visual attribute. Once you create a named visual attribute. Visual Attribute Types 1. The editor specified must use the ASCII text format. You create a user-named editor when you want to display the editor programmatically with SHOW_EDITOR. Background Color Fill Pattern. Default Editor Default editor is invoked at runtime. or when you want to specify custom editor attributes such as scroll bar and title. Font Weight Color and pattern properties: Foreground Color. For information on environment variables and system editor availability. Charmode Logical Attribute. White on Black It can be changed dynamically.’v1’). the resource file in use. There are three types of editor objects: default editor. they are custom VAT 3. Font Style. and font settings. Font Width. including the type of object. FORMS60_EDITOR = C:\WINDOWS\NOTEPAD. EDITOR This object enables the operator to edit text.Shik Mahamood Ali 30 Visual attributes are the font. Form Builder determines its display size and position dynamically based on the size and position of the text item from which the editor was invoked. Visual attribute name is connected to an object by setting visual attribute name property Set_item_property(‘text1’. System Editor The system editor to be used is defined by the FORMS60_EDITOR environment variable. User-Named Editor A user-named editor has the same text editing functionality as the default editor. Custom When the attribute of an objects are changed at design tome. and user-named editor. and the window manager.current_record_attribute. .

ed_ok BOOLEAN. END IF. message_in. y. */ DECLARE itm_x_pos NUMBER. x. Example: /* ** Built–in: SHOW_EDITOR ** Example: Accept input from the operator in a user–defined ** editor. Pass the contents of the :emp. */ DECLARE ed_id Editor. height).Cursor_Item. a user-named editor. 10. or the current system editor). y. Example: /* ** Built–in: EDIT_TEXTITEM ** Example: Determine the x–position of the current item ** then bring up the editor either on the left ** side or right side of the screen so as to not ** cover the item on the screen. Use the system editor if the user has ** checked the ”System_Editor” menu item under the ** ”Preferences” menu in our custom menu module.CHECKED) = ’TRUE’ THEN ed_name := ’system_editor’. val. message_out. val VARCHAR2(32000).SYSTEM_EDITOR’). */ val := :emp. IF Get_Menu_Item_Property(mi_id. The EDIT_TEXTITEM procedure invokes the editor associated with the current text item in the form (the default editor.Shik Mahamood Ali 31 SHOW_EDITOR(editor_name. BEGIN mi_id := Find_Menu_Item(’PREFERENCES. result). width.comments item ** into the editor and reassign the edited contents if ** ’ed_ok’ returns boolean TRUE.X_POS). IF itm_x_pos > 40 THEN .14) on the ** screen. val. IF ed_ok THEN :emp. END IF. SHOW_EDITOR takes message_in and message_out parameters that allow you to pass a text string in to the editor and to get the edited text string back when the operator accepts the editor. Show_Editor( ed_id. ed_name VARCHAR2(40).comments.14. BEGIN itm_x_pos := Get_Item_Property(:System. ed_ok). /* ** Show the appropriate editor at position (10.comments := val. Edit_Textitem(x. mi_id MenuItem. END. ELSE ed_name := ’my_editor1’. The SHOW_EDITOR procedure displays a user-named editor at the specified display coordinates. ed_id := Find_Editor( ed_name ).

8). Dialog .Content Canvas The most common canvas type is the content canvas (the default type).1.Toolbar Canvas A toolbar canvas often is used to create toolbars for individual windows.Tab Canvas A tab canvas—made up of one or more tab pages —allows you to group and display a large amount of related information on a single dynamic Form Builder canvas object. including canvases. HIDE_VIEW('a_stack').8). property_true). WINDOW A window is a container for all visual objects that make up a Form Builder application. partly obscuring it.20. such as check boxes. You can display more than one stacked canvas in a window at the same time. and often are shown and hidden programmatically. A content canvas is the "base" view that occupies the entire content pane of the window in which it is displayed. You can create two types of toolbar canvases: horizontal or vertical. radio groups. and text items. tab canvases are displayed on top of a content canvas. 3. or SET_VIEW_PROPERTY('a_stack'. You must define at least one content canvas for each window you create. There are two window styles: Document Document Windows Document windows typically display the main canvases and work areas of your application where most data entry. While every new form automatically includes a default window named WINDOW1. Showing and hiding a canvas programmatically SHOW_VIEW('a_stack'). CANVAS 32 Edit_TextItem(1. property_false).Shik Mahamood Ali ELSE END. or SET_VIEW_PROPERTY('a_stack'. 2.20. and data retrieval is performed. Horizontal toolbar canvases are displayed at the top of a window. Like stacked canvases. Stacked canvases obscure some part of the underlying content canvas. A single form can include any number of windows.Stacked Canvas A stacked canvas is displayed atop—or stacked on—the content canvas assigned to the current window. Horizontal Toolbar. Stacked. just under its menu bar. 1. while vertical toolbars are displayed along the far left edge of a window. 4. you can create additional windows as needed by inserting them under the Windows node in the Object Navigator. This object represents a background entity on which you place interface items. Edit_TextItem(60. visible.1. END IF. There are four types of canvas objects: Content. Tab pages (that collectively comprise the tab canvas) each display a subset of the information displayed on the entire tab canvas. and Vertical Toolbar. visible.

Shik Mahamood Ali 33 Dialog Windows Dialog windows are free-floating.Modal Windows Modal windows are usually used as dialogs. Use alerts to advise operators of unusual situations or to warn operators who are about to perform an action that might have undesirable or unexpected consequences. end users cannot resize. When-Window-Closed . 2. Trigger . Hide on Exit property For a modeless window. ** Built-in: REPLACE_CONTENT_VIEW ** Example: Replace the 'salary' view with the 'history' ** view in the 'employee_status' window.Windows When-Window-Activated Window-Resized ALERT An alert is a modal window that displays a message notifying the operator of some application condition. All other windows in the application are either document windows or dialog windows. Modal windows are often displayed with a platformspecific border unique to modal windows. REPLACE_CONTENT_VIEW (window_name VARCHAR2. MDI and SDI windows 1. Window Modality 1. containers typically used for modal dialogs that require immediate user interaction. Modeless Windows You can display multiple modeless windows at the same time. When-Window-Deactivated . */ BEGIN Replace_Content_View('employee_status'. On some platforms. and end users can navigate freely among them (provided your application logic allows it). Single Document Interface Although MDI is the default system of window management during Forms Runtime. When- . . Multiple Document Interface MDI applications display a default parent window.'history'). you can layer modeless windows so that they appear either in front of or behind other windows. scroll. and have restricted functionality compared to modeless windows.Document windows always are displayed within the MDI application window frame. REPLACE_CONTENT_VIEW built-in Replaces the content canvas currently displayed in the indicated window with a different content canvas. determines whether Form Builder hides the window automatically when the end user navigates to an item in another window. 2. view_name VARCHAR2). for example. modal windows are "always-on-top" windows that cannot be layered behind modeless windows. On some platforms. called the application window. On most GUI platforms. END. Form Builder also provides support for an SDI root window on Microsoft Windows. or iconify a modal window.

and returns a numeric value when the operator selects one of three alert buttons. Caution. the subprogram returns an alert ID. Define the variable with a type of Alert. Message severity is represented visually by a unique icon that displays in the alert window. OBJECT GROUPS An object group is a container for a group of objects. al_id Alert. message SHOW_ALERT (alert_id Alert). You can use object groups to bundle numerous objects into higher-level building blocks that you can use again in another application. BEGIN al_id := Find_Alert('My_Error_Alert'). ** Trigger: On-Error */ DECLARE err_txt VARCHAR2(80) := Error_Text. FIND_ALERT (alert_name VARCHAR2). You define an object group when you want to package related objects for copying or sub classing in another module. Changes the message text for an existing alert. al_button Number. alert_message_text. SET_ALERT_PROPERTY (alert_id ALERT. VARCHAR2). SET_ALERT_BUTTON_PROPERTY(alert_id ALERT.property VARCHAR2. and Note. ID_NULL (Alert BOOLEAN). al_button := Show_Alert( al_id ). You must return the ID to an appropriately typed variable. value VARCHAR2). Object groups provide a way to bundle objects into higher-level building blocks that can be used in other parts of an application and in subsequent development projects. END.Shik Mahamood Ali 34 There are three styles of alerts: Stop. ** Built-in: SET_ALERT_PROPERTY ** Example: Places the error message into a user-defined alert ** named 'My_Error_Alert' and displays the alert. Searches the list of valid alerts in Form Builder. Changes the label on one of the buttons in an alert. Returns a BOOLEAN value that indicates whether the object ID is available. When the given alert is located. err_txt ). Set_Alert_Property(al_id. property NUMBER. Displays the given alert. Using Object Groups • Blocks include: Items Item-level triggers Block-level triggers Relations • Object groups cannot include other object groups .button NUMBER. Each style denotes a different level of message severity. You define an object group when you want to package related objects so you can copy or subclass them in another module.

Use copying to export the definition of an object to another module. and personal standards. for a consistent look and feel • Reuse complex objects such as a Navigator Benefits of the Object Library • Simplifies the sharing and reuse of objects • Provides control and enforcement of standards • Eliminates the need to maintain multiple referenced forms SMARTCLASS . store. and distribute standard and reusable objects.Shik Mahamood Ali 35 • Deleting: An object group does not affect the objects An object affects the object group Copying an Object Copying an object creates a separate. Object libraries simplify the sharing of reusable components. maintain. such as buttons and items. They simplify reuse in complex environments. you can rapidly create applications by dragging and dropping predefined objects to your form. but they are protected against change in the library. property classes. Reusing components enables you to: • Apply standards to simple objects. by using Object Libraries. unique version of that object in the target module. You can use the Object Library to create. An object library can contain simple objects. project. and they support corporate. Any objects owned by the copied object are also copied. In addition. Objects can be used as standards (classes) for other objects. • • • • Is a convenient container of objects for reuse Simplifies reuse in complex environments Supports corporate. Subclassing Subclassing is an object-oriented term that refers to the following capabilities: • Inheriting the characteristics of a base class (Inheritance) • Overriding properties of the base class (Specialization) OBJECT LIBRARY This object provides an easy method of reusing objects and enforcing standards across the entire development organization. object groups. project. • Changes made to a copied object in the source module do not affect the copied object in the target module. and program units. and personal standards Simplifies the sharing of reusable components Object libraries are convenient containers of objects for reuse.

A library:  Is produced as a separate module and stored in either a file or the database  Provides a convenient means of storing client-side code and sharing it among applications  Means that a single copy of program units can be used by many form. you can mark them as SmartClasses by selecting each object in the object library and choosing Object—>SmartClass. A single library can contain many program units that can be shared among the Oracle Developer modules and applications that need to use them. including procedures.PLD . Object Library members which are not SmartClasses can only be used to create new objects in form modules into which they are added. If you frequently use certain objects as standards.PLX PL/SQL Library Module Binary PL/SQL Library Module Text PL/SQL Library Module Executable . BEGIN SELECT ename INTO v_ename FROM emp WHERE empno = bind_value. report. or graphic modules  Supports dynamic loading of program units FUNCTION locate_emp(bind_value IN NUMBER) RETURN VARCHAR2 IS v_ename VARCHAR2(15). You can mark many different objects that are spread across multiple object libraries as SmartClasses.MMT Menu Module Text .MMX Menu Module Executable Form Builder Built-in Package .Shik Mahamood Ali 36 A SmartClass is a special member of an Object Library. and packages. • Is an object in an object library that is frequently used as a class • Can be applied easily and rapidly to existing objects • Can be defined in many object libraries You can have many SmartClasses of a given object PL/SQL Libraries A library is a collection of PL/SQL program units. Unlike other Object Library members. END. date items.MMB Menu Module Binary . RETURN(v_ename).menu. and alerts. such as standard buttons.PLL . it can be used to subclass existing objects in a form using the SmartClass option from the right mouse button popup menu. functions. Reasons to share objects and code:  Increased productivity  Increased modularity  Decreased maintenance  Maintaining standards .

Shik Mahamood Ali

37

EXEC_SQL Provides built-ins for executing dynamic SQL within PL/SQL procedures

VBX Provides built-ins for controlling and interacting with VBX controls; this package works only in a 16-bit environment and is provided for backward compatibility WEB Provides built-ins for the Web environment OLE2 Provides a PL/SQL API for creating, manipulating, and accessing attributes of OLE2 automation objects SUBPROGRAM A subprogram can be either a procedure or a function. Built-in subprograms are therefore called in two distinct ways: • Built-in procedures: Called as a complete statement in a trigger or program unit with mandatory arguments. • Built-in functions: Called as part of a statement, in a trigger or program unit, at a position where the function’s return value will be used. Again, the function call must include any mandatory arguments. TRIGGER Triggers are blocks of PL/SQL code that are written to perform tasks when a specific event occurs within an application. In effect, a Form Builder 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.

Trigger Scope

1.Form Level The trigger belongs to the form and can fire due to events across the entire form. 2.Block Level The trigger belongs to a block and can only fire when this block is the current block. 3.Item Level The trigger belongs to an individual item and can only fore when this item is the current item. Trigger Properties
Execution Style

Execution Hierarchy property Specifies how the current trigger code should execute if there is a trigger with the same name defined at a higher level in the object hierarchy.

Shik Mahamood Ali The following settings are valid for this property:

38

Override Specifies that the current trigger fire instead of any trigger by the same name at any higher scope. This is known as "override parent" behavior. Before Specifies that the current trigger fire before firing the same trigger at the next-higher scope. This is known as "fire before parent" behavior. After Specifies that the current trigger fire after firing the same trigger at the next-higher scope. This is known as "fire after parent" behavior.

What are triggers used for?
           Validate data entry Protect the database from operator errors Limit operator access to specified forms Display related field data by performing table lookups Compare values between fields in the form Calculate field values and display the results of those calculations Perform complex transactions, such as verifying totals Display customized error and information messages to the operator Alter default navigation Display alert boxes Create, initialize, and increment timers

Groups of triggers
GROUP FUNCTION

When-triggers On-triggers Pre- and Post-triggers Key-trigger

Execute in addition to default processing Replace default processing Add processing before or after an event Change default processing assigned to a specific key

Trigger Categories  Block-processing triggers o When-Create-Record o When-Clear-Block o When-Database-Record o When-Remove-Record

Shik Mahamood Ali  Interface event triggers o When-Button-Pressed o When-Checkbox-Changed o When-Image-Activated o When-Image-Pressed o When-Radio-Changed o When-Timer-Expired o When –List-Changed o When –List-Activated o When –Tree-Note-Activated o When –Tree-Note-Expanded o When –Tree-Note-Selected o o o o o Key- [all] When-Window-Activated When-Window-Closed When-Window-Deactivated When-Window-Resized

39

 Master-detail triggers o On-Check-Delete-Master o On-Clear-Details o On-Populate-Details  Message-handling triggers o On-Error o On-Message  Navigational triggers o Pre- and Post- Triggers         o Pre-Form Pre-Block Pre-Record Pre-Text-Item Post-Text-Item Post-Record Post-Block Post-Form

When-New-Instance-Triggers     When-New-Form-Instance When-New-Block-Instance When-New-Record-Instance When-New-Item-Instance

 o o Pre-Query Post-Query

Query-time triggers

Shik Mahamood Ali  Transactional triggers. o o o o o o o o o o o o o o o o o o o On-Count On-Delete. On-Insert. On-Lock. On-Logon. On-Logout. On-Select. On-Update. Post-Database-Commit. Post-Delete. Post-Forms-Commit. Post-Insert. Post – Select. Post-Update. Pre-Commit. Pre-Delete. Pre-Insert. Pre-Select. Pre-Update.

40

 Validation triggers o o When-Validate-Item When-Validate-Record

 Mouse Event Triggers o o o o o o o o When-Custom-Item-Event When-Mouse-Click When-Mouse-Double Click When-Mouse-Down When-Mouse-Enter When-Mouse-Leave When-Mouse-Move When-Mouse-Up

 Key-Fn Trigger o A Key-Fn trigger fires when an operator presses the associated key. o Use Key-Fn triggers to create additional function keys for custom functions.  Calling user-named triggers

TRIGGER CATEGORIES
 A. BLOCK-PROCESSING TRIGGERS Block processing triggers fire in response to events related to record management in a block.

to set complex. and after the operator attempts to navigate out of the item..Ship_Method. Fires In • CREATE_RECORD WHEN-CREATE-RECORD TRIGGER This example assigns data-driven or calculated default values without marking the record as changed. In a When-Clear-Block trigger. FETCH ship_dflt INTO :Invoice.Shik Mahamood Ali 41 1. 2. but explicit cursor is more ** efficient. . the value of SYSTEM. its value is always accurate.. Fires In • • • CLEAR_BLOCK COUNT_QUERY ENTER_QUERY Clear_Block(No_Validate). When-Clear-Block Perform an action whenever Form Builder flushes the current block. Form Builder fires this trigger. END. removes all records from the block.Custid AND pref = 'SHIP'. DECLARE CURSOR ship_dflt IS SELECT val FROM cust_pref WHERE Custid = :Customer.INTO. that is. 3. That is the trigger fires as soon as Form Builder determines through validation that the record should be processed by the next post or commit as an insert or update. For example. This generally occurs only when the operator modifies the first item in a record. stored in a preference table. when the operator presses the [Insert] key. Because GET_RECORD_PROPERTY requires reference to a specific record. rather than design time. CLOSE ship_dflt. */ OPEN ship_dflt.Due_Date := SYSDATE + :Customer.Net_Days_Allowed. An alternative is to use GET_RECORD_PROPERTY to obtain the record status. /* ** Default the shipping method based on this customers ** preference. calculated. When-Create-Record Fires when Form Builder creates a new record. or data-driven default values that must be specified at runtime. Used For • • Use a When-Clear-Block trigger to perform an action every time Form Builder flushes the current block. or navigates to the last record in a set while scrolling down. We could ** use SELECT. Used For • Perform an action whenever Form Builder attempts to create a new record in a block.RECORD_STATUS is unreliable because there is no current record. For example. For example. When-Database-Record Fires when Form Builder first marks a record as an insert or an update. */ :Invoice. BEGIN /* ** Default Invoice Due Date based on Customer's ** Net Days Allowed value from the Customer block. you might want to perform an automatic commit whenever this condition occurs. The When-Clear-Block trigger does not fire when Form Builder clears the current block during the CLEAR_FORM event.

1. Perform an action whenever a record is cleared or deleted. to calculate text item values. Initiate an action when the operator toggles the state of a check box. When-Button-Pressed Fires when an operator selects a button. thus indicating that the record should be processed by the next COMMIT_FORM operation Use a When-Database-Record trigger to perform an action every time a record is first marked as an insert or an update.INTERFACE EVENT TRIGGERS Interface event triggers fire in response to events that occur in the form interface. 2. When-Remove-Record Fires whenever the operator or the application clears or deletes a record. For example.. either by clicking with the mouse. fire only in response to operator input or manipulation. like When-Window-Activated. then the commit was not successful.Form_Status = 'CHANGED' THEN Commit_Form. or using the keyboard. or for other item. Others. Usage Notes • Use a When-Button-Pressed trigger to perform navigation. such as When-Button-Pressed. END IF. or using the keyboard. 4. BEGIN IF :System. When-Checkbox-Changed Fires when an operator changes the state of a check box.. Some of these trigger. can fire in response to both operator input and programmatic control.Shik Mahamood Ali Used For • • 42 Perform an action whenever Form Builder changes a record's status to Insert or Update. or form level functionality. RAISE Form_Trigger_Failure. block. to adjust a running total that is being calculated for all of the records displayed in a block. This example executes a COMMIT_FORM if there are changes in the form. END IF. /* If the Form_Status is not back to 'QUERY' ** following a commit.Form_Status <> 'QUERY' THEN Message('Unable to commit order to database. by clicking with a mouse. END.'). either with the mouse or through keyboard selection . */ IF :System. Fires In • • CLEAR_RECORD DELETE_RECORD B.

If the check box is set off.JPG’.order_filled item prevents the date_shipped item from being updated if the user marks the order as filled ( checked on ). 4. Usage Notes • Use a When-Image-Pressed trigger to perform an action when an operator clicks or double clicks on an image item.date_shipped’. 3.date_shipped’. End if. When-Image-Pressed Initiate an action whenever an operator clicks on an image item.Update_allowed’.filled’) then Set_Item_Property(‘s_ord. • When an operator clicks in a check box. So for all navigation triggers that fire before the When-Checkbox-Changed trigger. End.property_false).STID)||’. the When-Checkbox-Changed trigger is the first trigger to register the changed value of a check box item. the value of the check box item remains as it was before the operator navigated to it. then the Date_Shipped item is enabled. the internal value of that item does not change until navigation is completed successfully. . End. Begin If checkbox_checked(‘s_ord. 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. The above When_Image_Pressed trigger on the stimage item displays a image of the current student (in the stmast block) when the user clicks the image item. Fires when an operator uses the mouse to: •  Single-click on an image item. Double-click on an image item.’STMAST:STIMAGE’).Update_allowed’. Note : That When-Image-Pressed also fires on a double-click. When-Checkbox-Changed Trigger examples This trigger on the :S_ord. Begin READ_IMAGE_FILE(‘ST_’||TO_CHAR(:STMAST. Else Set_Item_Property(‘s_ord.’JPG’.property_true). When-Image-Activated Initiate an action whenever the operator double-clicks an image item. Thus.Shik Mahamood Ali Usage Notes • 43 Use a When-Checkbox-Changed trigger to initiate a task dependent upon the state of a check box.

Declare . Begin Exception End. If not. When-Radio-Changed Description A fire when an operator selects a different radio button in a radio group. if a When-List-Changed trigger is attached to a combo box style list item. this trigger immediately confirms whether the customer has a good or excellent credit rating.Shik Mahamood Ali 44 5. or using the keyboard.Changed trigger will not fire if an end user duplicates the item using a key mapped to the DUPLICATE_ITEM built-in. the value of the radio group remains as it was before the operator navigated to it. • When-Radio-Changed Trigger examples When the user selects credit as the payment type for an order.) When an operator clicks an item in a radio group. or de-selects the currently selected radio button. For all navigation triggers that fire before the When-Radio-Changed trigger. the When-Radio-Changed trigger is the first trigger to register the changed value of a radio group. Populate student name based on the selected student id. 7. or if the end user causes a procedure to be invoked which changes the value. 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. When-List-Activated Trigger Fires when an operator double-clicks on an element in a list item that is displayed as a T-list. Select stname into :stname from the stmast where stid=:stid. The display style of a list item is determined by the List Style property. the When-List. not for dropdown lists or combo box style list items. operators use this technique in Enter Query mode to exclude a radio group from a query. the internal value of that item does not change until navigation is completed successfully. it fires each time the end user enters or modifies entered text. 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. 6. Usage Notes • Use a When-Radio-Changed trigger to perform an action depending on the state of a radio group. For example. either by clicking with the mouse. Usage Notes • A When-List-Activated trigger fires only for T-list style list items. In addition. When-List-Changed Trigger Description Fires when an end user selects a different element in a list item or de-selects the currently selected element. When no_data_found then Message(‘Invalid Student ‘). then the payment type is set to cash. (De-selecting a radio button in a radio group sets the radio group value to NULL. Initiate an action when an operator changes the current radio button selected in a radio group item. Thus.

payment_type=’CREDIT’ then Select credit_rate into v_credit from customer where custid=:s_ord. message(‘Warning – Customer must pay cash‘).' two_minutes NUMBER(6) := (120 * 1000).custid. call_status NUMBER.'. • • Fires In • Process Expired Timer When-Timer-Expired Trigger examples Example The following example displays a message box each time a repeating timer expires. navigation. Use a When-Timer-Expired trigger to initiate an event.timer_count = 1 THEN . You can call GET_APPLICATION_PROPERTY(TIMER_NAME) in a When-Timer-Expired trigger to determine the name of the most recently expired timer.timer_count := 1 BEGIN timer_id := FIND_TIMER('tele_timer'). msg_1 VARCHAR2(80) := 'Wrap up the first phase of your presentation'. alert_id := FIND_ALERT('tele_alert'). End if. The message box is displayed each time a repeating timer expires. End. When-Timer-Expired Description Fires when a timer expires.payment_type:=’CASH’. in which sales calls are timed. Usage Notes Timers are created programmatically by calling the CREATE_TIMER built-in procedure. If v_credit NOT_IN(‘GOOD’.credit_rate%type. or perform any task that should occur after a specified interval. msg_2 VARCHAR2(80) := 'Move into your close. Begin If :s_ord. or transaction processing. • The When-Timer-Expired trigger can not fire during trigger. BEGIN :GLOBAL.’EXCELLENT’) then :s_ord. IF :GLOBAL. update item values. one_and_half NUMBER(5) := (90 * 1000). 8. DECLARE timer_id TIMER. End if. The following example is from a telemarketing application. msg_3 VARCHAR2(80) := 'Ask for the order or repeat the close. Initiate an action when a programmatic timer expires.Shik Mahamood Ali 45 v_credit customer. and message boxes are displayed to prompt the salesperson through each stage of the call. alert_id ALERT.

call_status := Show_Alert(alert_id). NO_CHANGE). Fires when a window is made the active window. Next_Record. IF call_status = ALERT_BUTTON1 THEN Delete_Timer(timer_id).timer_count = 2 THEN Change_Alert_Message(alert_id. Note that on some window managers.timer_count := 0. call_status := Show_Alert(alert_id). a window can be activated by. :GLOBAL. navigating to an item in a different window always activates that window. ELSE Set_Timer(timer_id.timer_count := 0. IF call_status = ALERT_BUTTON1 THEN Delete_Timer(timer_id). END IF. Next_Record. 9. say. ELSIF call_status = ALERT_BUTTON2 THEN :GLOBAL. one_and_half. END IF. ELSIF :GLOBAL. This operation is independent of navigation to an item in the window. msg_2). END IF. clicking on its title bar. When-Window-Activated Initiate an action whenever an operator or the application activates a window. Thus. ELSE Set_Timer(timer_id. This occurs at form startup and whenever a different window is given focus.timer_count := 0. msg_1). NO_CHANGE). NO_CHANGE. END IF.timer_count = 2. NO_REPEAT). Next_Record. END. but window activation can also occur independently of navigation. ELSE Set_Timer(timer_id. ELSE Change_Alert_Message(alert_id. Usage Notes: Use this trigger to perform the following types of tasks: . call_status := Show_Alert(alert_id). ELSIF call_status = ALERT_BUTTON2 THEN :GLOBAL. msg_3). ELSIF call_status = ALERT_BUTTON2 THEN :GLOBAL. two_minutes. ALERT_MESSAGE_TEXT. IF call_status = ALERT_BUTTON1 THEN Delete_Timer(timer_id).Shik Mahamood Ali 46 Set_Alert_Property(alert_id.

when the root window is first drawn. When-Window-Deactivated Initiate an action whenever a window is deactivated as a result of another window becoming the active window. resizing the window programmatically fires the When–Window–Resized trigger.) This trigger also fires at form startup. either by the operator or programmatically through a call to RESIZE_WINDOW or SET_WINDOW_PROPERTY. and EXIT_FORM built–in subprograms. . • Keep track of the most recently fired window trigger by assigning the value from SYSTEM. PROPERTY_OFF). SET_WINDOW_PROPERTY. such as width. • Enforce navigation to a particular item whenever a window is activated. property). Set input focus in an item on the target window. (Even if the window is not currently displayed. • You can close a window with the HIDE_WINDOW . by way of the GET_WINDOW_PROPERTY built–in. Example: Begin GET_WINDOW_PROPERTY( window_name.When-Window-Closed Initiate an action whenever an operator closes a window with the window manager's Close command. 12. When-Window-Resized Initiate an action whenever a window is resized. End. It does not fire when a window is iconified. 10 . Fires when a window is resized. or y coordinate. VISIBLE. Example: The following example of a call to SET_WINDOW_PROPERTY from this trigger closes a window whenever the operator closes it by way of the window manager operation: Set_Window_Property(’window_name’. x coordinate.EVENT_WINDOW to a variable or global variable. 11. height.Shik Mahamood Ali 47 • Capture initial settings of window properties. • You can hide the window that contains the current item. Fires when an operator deactivates a window by setting the input focus to another window. Usage Notes: Use this trigger to perform any one of the following types of tasks: • • • Capture the changed window properties. Audit the actions of an operator. Usage Notes: Use this trigger to audit the state of a window whenever the operator deactivates the window by setting the input focus in another window. Usage Notes: • Use this trigger to programmatically close a window when the operator issues the window–manager Close command. either by the operator or programmatically.

*/ wn_id1 := Find_Window(Window1). you can define a Key-EXIT trigger to replace the default functionality of the [Help] key. /* ** Resize Window2 to the same size */ Resize_Window( Window2. the trigger fires when operator presses a specific key or key-sequence.Shik Mahamood Ali 48 • Maintain certain visual standards by resetting window size if the window was improperly resized. For example. h ).[ALL] ( KEY TRIGGERS ) Key Triggers have a one-to-one relationship with specific keys.HEIGHT). Example: /* ** Built–in: RESIZE_WINDOW ** Example: Set Window2 to be the same size as Window1 */ PROCEDURE Make_Same_Size_Win( Window1 VARCHAR2. i. END. w. BEGIN /* ** Find Window1 and get it’s width and height. Replace the default function associated with a function key. Key Triggers and Function Keys KEY TRIGGER Key–CLRBLK Key–CLRFRM Key–CLRREC Key–COMMIT Key–CQUERY Key–CREREC Key–DELREC Key–DOWN Key–DUP–ITEM Key–DUPREC Key–EDIT Key–ENTQRY Key–EXEQRY Key–EXIT Key–HELP Key–LISTVAL Key–MENU Key–NXTBLK Key–NXT–ITEM Key–NXTKEY Key–NXTREC Key–NXTSET Key–PRINT Key–PRVBLK Key–PRV–ITEM Key–PRVREC Key–SCRDOWN Key–SCRUP ASSOCIATED FUNCTION KEY [Clear Block] [Clear Form] [Clear Record] [Accept] [Count Query Hits] [Insert Record] [Delete Record] [Down] [Duplicate Item] [Duplicate Record] [Edit] [Enter Query] [Execute Query] [Exit] [Help] [List of Values] [Block Menu] [Next Block] [Next Item] [Next Primary Key] [Next Record] [Next Set of Records] [Print] [Previous Block] [Previous Item] [Previous Record] [Scroll Down] [Scroll Up] . w NUMBER. Window2 VARCHAR2) IS wn_id1 Window. h := Get_Window_Property(wn_id1.WIDTH). KEY.e. C. w := Get_Window_Property(wn_id1. h NUMBER.

KEY-COMMIT TRIGGER AT FORM LEVEL: EMPLOYEES FORM BEGIN IF GET_APPLICATION_PROPERTY( CALLING_FORM ) IS NULL THEN COMMIT_FORM. 2. END IF. ALERT_MESSAGE_TEXT.Shik Mahamood Ali Key–UP Key–UPDREC 49 [Up] Equivalent to Record. Usage Notes: Use Key–Others triggers to limit an operator’s possible actions. ’Do you really want to leave the form?’). Before you can attach key triggers to these keys. however. A Key–Others trigger overrides the default behavior of a Runform function key (unless one of the following restrictions apply). use Key–Others triggers to perform the following tasks: • Disable all keys that are not relevant in a particular situation. These keys are referred to as Key–F0 through Key–F9. 1. Key–Others Trigger A Key–Others trigger fires when an operator presses the associated key. When this occurs. KEY-EXIT AT FORM LEVEL SET_ALERT_PROPERTY (’question_alert’. • Perform one specific action whenever an operator presses any key. You can attach Key–Fn triggers to 10 keys or key sequences that normally do not perform any Oracle Forms operations. KEY-DELREC TRIGGER ON S_CUSTOMER BLOCK DELETE_RECORD. 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. Specifically. A Key–Others trigger is associated with all keys that can have key triggers associated with them but are not currently defined by function key triggers (at any level).MASTER-DETAIL TRIGGERS Form Builder generates master/detail triggers automatically when a master/detail relation is defined between blocks.Key–Fn Trigger A Key–Fn trigger fires when an operator presses the associated key. END. Lock command on the default menu 1. D. The default master/detail triggers enforce coordination between records in a detail block and the master record in a master block. Oracle Forms still displays the function key’s default entry in the Show Keys screen. IF SHOW_ALERT (’question_alert’) = ALERT_BUTTON1 THEN EXIT_FORM. END IF. . you or the DBA must use Oracle Terminal to map the keys to the appropriate functions. Usage Notes: Use Key–Fn triggers to create additional function keys for custom functions. ELSE POST.

Message handling triggers fire in response to these default messaging events. E. ERROR_TYPE. 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. On–Error triggers should be attached to the form. you can call the SET_BLOCK_PROPERTY(COORDINATION_STATUS) built–in. BEGIN SELECT SUM(dollar_amt) INTO the_sum FROM po_distribution WHERE po_number = :purchase_order. rather than to a block or item. • Example: .’). END IF. On-Error Replace a default error message with a custom error message. Trapping certain errors at the block or item level can be difficult if these errors occur while Oracle Forms is performing internal navigation. • If you intend to manage block coordination yourself. • When Immediate coordination is set. 1. RAISE Form_Trigger_Failure. Usage Notes: Oracle Forms creates the On–Clear–Details trigger automatically when you define a master– detail block relation. DBMS_ERROR_TEXT. 3.total THEN Message(’PO Distributions do not reconcile. Oracle Forms marks the blocks as needing to be coordinated. • When Deferred coordination is set and this trigger fires. 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.MESSAGE-HANDLING TRIGGERS Form Builder automatically issues appropriate error and informational messages in response to runtime events. Usage Notes Use an On–Error trigger for the following purposes: • • To trap and recover from an error To replace a standard error message with a custom message Use the ERROR_CODE. Immediate coordination is the default. In most cases. such as during a Commit process.Shik Mahamood Ali 50 DECLARE the_sum NUMBER.number. or DBMS_ERROR_CODE built–in function in an On–Error trigger to identify a specific error condition. IF the_sum <> :purchase_order. 2. 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. END. ERROR_TEXT. or to trap and recover from an error. this causes the details of the instantiated master to be populated immediately.

to replace a default message issued by Form Builder with a custom message. ELSE Message(lv_errtyp||’–’||to_char(lv_errcod)||’: ’||lv_errtxt). Usage Notes: Use an On–Message trigger for the following purposes: • To trap and respond to an informative message • To replace a standard informative message with a custom message • To exclude an inappropriate message Example: The following example responds to an error message by displaying an alert that gives the user a message and gives the user the choice to continue or to stop: DECLARE alert_button NUMBER.. lv_errtxt VARCHAR2(80) := ERROR_TEXT. ELSE . BEGIN IF lv_errcod = 40350 THEN alert_button := Show_Alert(’continue_alert’). END IF. DECLARE lv_errcod NUMBER := ERROR_CODE. On-Message To trap and respond to a message. ELSIF (lv_errcod = 40zzz) THEN ** More tasks here */ ELSE Message(lv_errtyp||’–’||to_char(lv_errcod)||’: ’||lv_errtxt). END. lv_errcod NUMBER := MESSAGE_CODE.. END IF.. .Shik Mahamood Ali 51 The following example checks specific error message codes and responds appropriately. IF alert_button = ALERT_BUTTON1 THEN . lv_errtxt VARCHAR2(80) := MESSAGE_TEXT. END.. for example.. BEGIN IF (lv_errcod = 40nnn) THEN /* ** Perform some tasks here */ ELSIF (lv_errcod = 40mmm) THEN /* ** More tasks here */ . END IF. lv_errtyp VARCHAR2(3) := ERROR_TYPE. lv_errtype VARCHAR2(3) := MESSAGE_TYPE.. RAISE Form_Trigger_Failure. RAISE Form_Trigger_Failure. 2.

] IF nvl(:control. • To test the operator’s query conditions.Mgr IS NULL THEN Message(’Supply Employee Name and/or Manager Id ’||’for Query. Begin End. Note that the trigger only fires on the initial fetch of a record not when a record is subsequently scrolled back into view a second or third time. Use it to check or modify query conditions. Make sure the user has given one of the two Columns which we have indexed in their search criteria.Ename IS NULL AND :Employee.lineitem_count FROM S_ITEM WHERE ord_id = :S_ORD. This Pre-Query trigger on the S_ORD block only permits queries if there is a restriction on either the Order ID. such as looking up values in other tables based on a value in the current record.name || ‘%’.’Y’)=’N’ then :S_Customer. or Date Shipped. This prevents attempts at very large queries. Use Post-Query as follows: • To populate non database items as records are returned from a query • To calculate statistics • A Post-Query trigger fires as each record is fetched (except array processing).exact_match. Date Ordered. RAISE Form_Trigger_Failure. Fires once for each record fetched into the block.’). and to fail the query process if the conditions are not satisfactory for the application • To add criteria for the query by assigning values to base table items • A Pre-Query trigger fires before a query executes.QUERY-TIME TRIGGERS 52 Query-time triggers fire just before and just after the operator or the application executes a query in a block. Use it to perform calculations and populate additional items. 2.Shik Mahamood Ali F. Post-Query fires for each record that is fetched into the block as a result of a query. otherwise fail the query with a helpful message A] IF :Employee.name:=’%’||:S_customer. END IF. END IF. This trigger is defined at block level or above. Post-Query Perform an action after fetching a record. 1. Pre-Query Validate the current query criteria or provide additional query criteria programmatically. and displays this number as a summary value in the non base table item :Lineitem_count. [ Set the initial value property to “Y”. B] [ exact_match – Check Box User can specify if or not a query condition for a customer name should exactly match the table value. just before sending the SELECT statement to the database. SELECT COUNT(ord_id) INTO :S_ORD. This Post-Query trigger on the S_ORD block selects the total count of line items for the current Order. .id.

. G.*/ OPEN lookup_payplan.TRIGGERS Fire as Form Builder navigates internally through different levels of the object hierarchy. but before the statement is actually issued. What is a difference between pre-select and pre-query? Fires during the execute query and count query processing after oracle forms constructs the select statement to be issued. A Post-Query trigger fires as each record is fetched (except array processing). FETCH lookup_payplan INTO :Employee. END.NAVIGATIONAL TRIGGERS Navigational triggers fire in response to navigational events. /* ** Lookup Area Descript given the Zipcode in ** the Employee Record just fetched. FETCH lookup_area INTO :Employee. CLOSE lookup_payplan. when the operator clicks on a text item in another block.Payplan_Desc_Nondb. Use it to check or modify query conditions. For instance.Payplan_Id.Zip. Use Explicit ** Cursor for highest efficiency.Area_Desc_Nondb. Use it to perform calculations and populate additional items.AND POST. Pre-query trigger fires before pre-select trigger. BEGIN /* Lookup the Payment Plan Description given the Payplan_Id in the Employee Record just fetched. CLOSE lookup_area. for display in non–database items in the current block. ** Use Explicit Cursor for highest efficiency. CURSOR lookup_area IS SELECT Area_Name FROM Zip_Code WHERE Zip = :Employee. A query fetched 10 records How many times does a PRE-QUERY Trigger and POST-QUERY Trigger will get executed? PRE-QUERY fires once. navigational events occur as Form Builder moves the input focus from the current item to the target item. • • A Pre-Query trigger fires before a query executes. I ] PRE.Shik Mahamood Ali 53 Example: This example retrieves descriptions for code fields. POST-QUERY fires 10 times. DECLARE CURSOR lookup_payplan IS SELECT Payplan_Desc FROM Payplan WHERE Payplan_Id = :Employee. */ OPEN lookup_area. The pre-query trigger fires just before oracle forms issues the select statement to the database after the operator as define the example records by entering the query criteria in enter query mode.

navigation triggers do not fire if they belong to a unit that is smaller than the current validation unit. IF not (DBMS_SESSION.or Post navigation trigger fails.and Post.IS_ROLE_ENABLED(’ADMINISTRATIVE’) or (DBMS_SESSION. if the validation unit is Record. When Do Navigation Triggers Not Fire? The Pre. the input focus returns to its initial location (where it was prior to the trigger firing).IS_ROLE_ENABLED(’TECHNICAL’) THEN MESSAGE(’You are not authorized to run this application’). To the user. it appears that the input focus has not moved at all.and Post-Navigation Triggers Fire? The Pre.Shik Mahamood Ali 54 When Do Pre.and Post-Text-Item triggers do not fire.and Post. such as at form startup. Pre. . What Happens When a Navigation Trigger Fails? If a Pre. 1.navigation triggers fire during navigation. Example The Pre-Text-Item trigger fires just before entering a text item. that is just before entry to or just after exit from the object specified as part of the trigger name. For instance. Pre-Form Perform an action just before Form Builder navigates to the form from "outside" the form.

Usage Notes: • Fires during the Enter the Record process. Pre-Text-Item Perform an action before Form Builder navigates to a text item from the record level. Usage Notes: . 3. property_false). when a form is exited. SET_ITEM_PROPERTY(’CONTROL. END IF.RECORD_STATUS evaluating to NEW.Shik Mahamood Ali PAUSE. such as when exiting the form. Pre-Block Perform an action before Form Builder navigates to the block level from the form level. 5. Pre-Record Perform an action before Form Builder navigates to the record level from the block level. Usage Notes: Use a Pre–Text–Item trigger to perform the following types of tasks: • Derive a complex default value. END IF. 55 2. during navigation to a different record. Record the current value of the text item for future reference. RAISE form_trigger_failure. • Use a Pre–Record trigger to keep a running total. during navigation from one block to another. Usage Notes: Use a Pre–Block trigger to: • Allow or disallow access to a block • Set variable values Disabling stock_button when leaving CONTROL block: begin End.stock_button’. enabled. 4. The following trigger prevents the user from entering a new record given some dynamic condition and the status of SYSTEM. based on other items previously entered into the same record. Fires during the Leave the Form process. and • store that value in a global variable or form parameter.Record_Status = ’NEW’) THEN RAISE Form_Trigger_Failure. IF (( dynamic–condition) AND :System. Post-Form Perform an action before Form Builder navigates to "outside" the form. Fires during the Enter the Block process.

Post-Block Manipulate the current record when Form Builder leaves a block and navigates to the form level. then skip to the next record instead of ** the default of going back to the first item in ** the same block ** Trigger: Key–Next–Item */ DECLARE cur_itm VARCHAR2(80) := :System. Example: /* ** Built–in: NEXT_RECORD ** Example: If the current item is the last item in the ** block. BEGIN lst_itm := cur_blk||’.Cursor_Block.’||Get_Block_Property(cur_blk. Usage Notes: Use a Post–Record trigger when you want to perform an action whenever the operator or the application moves the input focus from one record to another. ELSE Next_Item. 6. Example . PREVIOUS_BLOCK. The Leave the Record process can occur as a result of numerous operations.cmdsave’. NEXT_BLOCK. Set_item_property (‘control. lst_itm VARCHAR2(80). property_false). Fires during the Leave the Record process. including INSERT_RECORD. Usage Notes: • • Use a Post–Block trigger to validate the block’s current record. CREATE_RECORD.LAST_ITEM). cur_blk VARCHAR2(80) := :System. For example. Specifically. Post-Record Manipulate a record when Form Builder leaves a record and navigates to the block level. etc. you can do so from within this trigger. for example. 7. the Post–Record trigger fires whenever the operator or the application moves the input focus from one record to another. that is. NEXT_RECORD. This trigger does not fire when the form is exited abnormally. For example. IF cur_itm = lst_itm THEN Next_Record. • To display a message to the operator upon form exit. enabled. use a Post–Form trigger to erase any global variables that the form no longer requires. if validation fails in the form. DELETE_RECORD. You might also use this trigger to test a condition and prevent the user from leaving a block based on that condition. if you want to set a visual attribute for an item as the operator scrolls down through a set of records.Shik Mahamood Ali 56 You can use a Post–Form trigger for the following tasks: • To clean up the form before exiting. the record that had input focus when the Leave the Block event occurred.Cursor_Item.

where_cls’). when the ORDERS form is run. ’'GLOBAL. BEGIN DEFAULT_VALUE(’’. Specifically. When-New-Form-Instance Trigger at Form Level .HEIGHT). Fires during the Leave the Item process for a text item. END. :GLOBAL.WIDTH).HEIGHT).height_win_inventory := GET_WINDOW_PROPERTY(’win_inventory’. these triggers fire just after Form Builder moves the input focus to a different item. 1.height_win_order := GET_WINDOW_PROPERTY(’win_order’.where_cls). (Occurs after the Pre-Form trigger fires). Post-Text-Item Manipulate an item when Form Builder leaves a text item and navigates to the record level. 1b. II] WHEN-NEW-INSTANCE-TRIGGERS Fire at the end of a navigational sequence that places the input focus on a different item.width_win_inventory := GET_WINDOW_PROPERTY(’win_inventory’. 1d. this trigger fires when the input focus moves from a text item to any other item. Specifically. WIDTH). when the form returns to a quiet state to wait for operator input. by including the following code in your When-New-Form-Instance trigger: 1a. DEFAULT_WHERE. 1c. :GLOBAL. Perform a query of all orders. EXECUTE_QUERY. 57 8. BEGIN EXECUTE_QUERY. EXECUTE_QUERY.“object”-Instance Triggers Fire? The When-New-”object”-Instance triggers fire immediately after navigation to the object specified as part of the trigger name. Example The When-New-Item-Instance trigger fires immediately after navigation to a new instance of an item.:GLOBAL. END. :GLOBAL. When Do When-New. When-New-Form-Instance Perform an action at form start-up. :GLOBAL. SET_BLOCK_PROPERTY(’prod_lov_blk’. END.width_win_order := GET_WINDOW_PROPERTY(’win_order’.Shik Mahamood Ali END IF.

Set_Tree_Property(htree. Example The Cursor arrives in each record of the S_Item block. PROPERTY_FALSE). END. rg_emps := Create_Group_From_Query('rg_emps'. TITLE. fires after the When-New-Block-Instance trigger. each time Oracle Forms instantiates a new record in the block. SET_WINDOW_PROPERTY( forms_mdi_window. and populates the product_image item with a picture of the products. ’Summit Sporting Goods Application’). rg_emps). 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. If the new record is in a different block. Usage Notes: Use a When–New–Record–Instance trigger to perform an action every time Oracle Forms instantiates a new record. v_ignore := Populate_Group(rg_emps). but before the When-New-Item-Instance trigger. when an operator presses [Down] to scroll through a set of records.DELETE_ALLOWED. NULL. 3.htree3'). rg_emps RECORDGROUP. level. Example This code could be used in a WHEN-NEW-FORM-INSTANCE trigger to initially populate the hierarchical tree with data.Shik Mahamood Ali 58 BEGIN SET_WINDOW_PROPERTY( forms_mdi_window. a record group is created and the hierarchical tree is populated. The example locates the hierarchical tree first. to_char(empno) ’ ||' from emp ' ||'connect by prior empno = mgr ' ||’start with job = ’’PRESIDENT’’’). DECLARE htree ITEM.’select 1. Ftree. v_ignore NUMBER. in other words.RECORD_GROUP. END. Oracle Forms fires this trigger each time the input focus moves to the next record. IF GET_APPLICATION_PROPERTY(username) = ’SCOTT’ THEN SET_BLOCK_PROPERTY(’S_ITEM’. Then. END IF. ename. Usage Notes: Use a When–New–Block–Instance trigger to perform an action every time Oracle Forms instantiates a new block. Ftree. When-New-Record-Instance Perform an action immediately after the input focus moves to an item in a different record. WINDOW_STATE. MAXIMIZE ). 2. if one exists . Example The following example of a When-New-Block-Instance trigger conditionally sets the DELETE ALLOWED property to FALSE. For example. BEGIN htree := Find_Item('tree_block.

Message(’This date must be of the form 01–MON–YY’). End if End.date_shipped’. Specifically. END IF.] BEGIN IF (:global. property_true).UPDATE_ALLOWED. END IF.When-New-Item-Instance Fires when the input focus moves to an item. GO_ITEM(’S_ORD.a Example: Brings up the debugging window for a particular ** value of the ’JOB’ item anytime the user changes records.product_image’). END.order_filled’)THEN SET_ITEM_PROPERTY(’S_ORD. END. END.’S_ITEM. it fires after navigation to an item. 4. Call_Form(’clerk_timesheet’). The When-New-Item-Instance trigger is especially useful for calling restricted (navigational) built-ins. fires after the When-New-Block-Instance trigger. Break. 3. when Form Builder is ready to accept input in an item that is different than the item that previously had input focus. BEGIN IF TO_CHAR(:Emp. If the new item is in a different block.cancel_query = 'N'. END IF.’tiff’.Job = ’CLERK’ THEN Break.Empno IS NOT NULL THEN . END IF.Hiredate. Perform an action immediately after the input focus moves to a different item.Shik Mahamood Ali 59 1] Declare Filename varchar2(20). 1] IF CHECKBOX_CHECKED(’S_ORD.mode = 'ENTER-QUERY') THEN Exit_Form. :global. 3]. Usage Notes Use a When-New-Item-Instance trigger to perform an action whenever an item gets input focus.PRODUCT_ID). BEGIN IF :Emp.Example: Clear the current item if it does not represent ** the first day of a month.cancel_query = 'Y' and :system. If Filename= ‘ No file’ then Null.’DD’) <> ’01’ THEN Clear_Item.*/ BEGIN IF :Emp.date_shipped’). Begin Filename:=get_product_image(:S_ITEM. 2] Built–in: CLEAR_ITEM . Else Read_Image_File(filename. 2] 1.

if you commit (save) changes in the form.Format mask . When the record passes these checks. so that the operator can make corrections. record. If validation fails. programmatic control. such as a Commit operation. 4].Empno.Employee_Id := :Emp.Data type . • Validation happens when: – [Enter] Key or ENTER built-in is activated – Control leaves the validation unit due to navigation or commit Validation Process Form Builder performs a validation process at several levels to ensure that records and individual values follow appropriate rules.Required (if so. and a When-Validate-Record trigger is then fired. END IF. Validation occurs at item. it is set to valid. END.EMPNO’ and :System. Validation occurs at: • Item level: Form Builder records a status for each item to determine whether it is currently valid. all records below that level are validated.Mode = ’ENTER–QUERY’ IF NOT Show_Lov(’my_lov’) THEN RAISE Form_Trigger_Failure. or default processing. Assume that you want Oracle Forms to display an LOV when the operator enters query mode and the input focus is in a particular text item. Standard checks include the following: . H. • Block and form level: At block or form level. Form Builder checks to see whether the record is valid. VALIDATION TRIGGERS Validation triggers fire when Form Builder validates data in an item or record.Range (Lowest-Highest Allowed Value) .Validate from List (see later in this lesson) • Record level: After leaving a record. If an item has been changed and is not yet marked as valid. If not. The following trigger accomplishes that operation. if present. BEGIN THEN IF :System. These checks are carried out before firing any When-Validate-Item triggers that you have defined. then control is passed back to the appropriate level. and form levels. For example. unless you have suppressed this action. Form Builder performs validation checks during navigation that occurs in response to operator input. When Does Validation Occur? Form Builder carries out validation for the validation unit under the following conditions: . then the status of each item in the record is checked. then is the item null?) . END. Clear_Block(No_Validate).Shik Mahamood Ali 60 :Global. END IF. End if. then all records in the form are validated.Cursor_Item = ’EMP. then Form Builder first performs standard validation checks to ensure that the value conforms to the item’s properties. block.

you can optionally use the LOV contents to validate data entered in the item. • If the item value causes multiple records to be found in the LOV. Form Builder then automatically uses the item value as a non case-sensitive search string on the LOV contents. The item then passes this validation phase. Form Builder displays the LOV and uses the text item value as the search criteria to automatically reduce the list. it does make it possible for your application to commit an invalid value to the database. by default Form Builder will not allow navigation out of the item until a valid value is entered. • The operator or a trigger navigates out of the validation unit. Form Builder marks the changed item as Valid and does not re-validate it. At validation time. If validation succeeds. • If the item’s value causes a single record to be found in the LOV. • The Defer_Required_Enforcement property postpones enforcement of the Required property from item validation to record validation. The validation unit is discussed in the next section. validation succeeds. Validation Triggers • Item level When-Validate-Item • Block level When-Validate-Record 1. then the full LOV contents are displayed to the operator. When an item has the Required property set to Yes. block. but is a partial value of the LOV value. so that the operator must choose. While this behavior is necessary to avoid validation loops. Setting the Defer_Required_Enforcement property to Yes allows the operator to move freely among the items in the record. • If no match is found. or form by the designer. When – Validate -Item Fires during the Validate the Item process. depending on the circumstances: • If the value in the text item matches one of the values in the first column of the LOV. Specifically. Using LOVs for Validation When you attach an LOV to a text item by setting the LOV property of the item. When-Validate-Item Trigger You have already used this trigger to add item-level validation. The trigger fires after standard item validation. then the full LOV column value is returned to the item (providing that the item is defined as the return item in the LOV). Usage Notes • Use a When-Validate-Item trigger to supplement Form Builder default item validation processing. The following events then occur. The default validation unit is item.Shik Mahamood Ali 61 • The [Enter] key is (ENTER command is not necessary mapped to the key that is physically labeled Enter) pressed or the ENTER built-in procedure is run (whose purpose is to force validation immediately). and processing continues normally. it fires as the last part of item validation for items with the New or Changed validation status. This includes when changes are committed. Example . Do this by setting the Validate from List property to Yes for the item. but can also be set to record. • It is possible to write a When-Validate-Item trigger that changes the value of an item that Form Builder is validating. and input focus is returned to the item if the trigger fails. the LOV is not displayed.

End_Date THEN Message('Your date range ends before it starts!'). in the order they were entered. Use <List> for help'). /* Method 1: Hardcode the item names into the trigger.. Because Form Builder has already checked that required items for the record are valid.Commcode. RAISE Form_Trigger_Failure.TRANSACTIONAL TRIGGERS Transactional triggers fire in response to a wide variety of events that occur as a form interacts with the data source. I. Note that it is possible to write a When-Validate-Record trigger that changes the value of an item in the record that Form Builder is validating. END IF. If validation succeeds.Shik Mahamood Ali 62 The SELECT. RAISE Form_Trigger_Failure. Duplicate entries in COMMPLAN table!'). This implies PL/SQL may attempt to fetch data twice from the table in question to insure that there aren't two matching rows. END. EXCEPTION WHEN No. When-Validate-Record must be defined at block level or above. Use a When-Validate-Record trigger to supplement Form Builder default record validation processing. it does make it possible for your application to commit an invalid value to the database. you can use this trigger to perform additional checks that may involve more than one of the record’s items.Data_Found THEN Message('Invalid Commission Plan. 2. it's more convenient to check the combination of them once at the record level. Example The following example verifies that Start_Date is less than End_Date.. Since these two text items have values that are related. BEGIN SELECT description INTO :Employee. RAISE Form_Trigger_Failure. When – Validate -Record Fires during the Validate the Record process. Specifically.Start_Date > :Experiment. While this behavior is necessary to avoid validation loops. ** Structured this way. it fires as the last part of record validation for records with the New or Changed validation status. This code presumes both date items are mandatory and that neither will be NULL. Transaction processing includes two phases: • Post: – Writes record changes to base tables – Fires transactional triggers • Commit: Performs database commit .*/ BEGIN IF :Experiment. rather than check each item separately. when the operator has left a new or changed record.Commplan_Desc FROM commplan WHERE commcode = :Employee. WHEN Too_Many_Rows THEN Message('Error. END. the chance this code will ** be reusable in other forms we write is pretty low because of dependency on block and item ** names.INTO statement must return an error if more than one row is retrieved that matches the criteria. When-Validate-Record Trigger This trigger fires after standard record-level validation. Form Builder marks the record and all of the fields as Valid and does not re-validate.

. . before a row is deleted. If it is an updated record: Fire the Pre-Update trigger. Fire the Post-Update trigger. set up special locking Pre-Commit Fires once during commit processing.Fire the Post-Insert trigger. If the current operation is COMMIT. Usage Notes • Use a Pre-Delete trigger to delete the detail record of a master record. 5 Fire the Post-Forms-Commit trigger. fires if there are changes to base table items in the form or if changes have been posted but not yet committed (This trigger always fires in case of uncommitted posts. 4 Validate the block (for all blocks in sequential order). then: 6 Issue an SQL-COMMIT statement.Fire the Pre-Insert trigger. Commit Triggers Uses 1.Delete the row from the base table or fire the On-Delete trigger. implement foreign-key delete rule Fires during the Post and Commit Transactions process. even if there are no changes to post. .Insert the row into the base table or fire the On-Insert trigger. . Pre-Commit Check user authorization.) Usage Notes: Use a Pre–Commit trigger to perform an action. before base table blocks are processed. For all deleted records of the block (in reverse order of deletion): .Shik Mahamood Ali Errors result in: • Rollback of the database changes • Error message The Commit Sequence of Events 63 The commit sequence of events (when the Array DML size is 1) is as follows: 1 Validate the form. Check the record uniqueness Update the row in the base table or fire the On-Update trigger. 2 Process save point. anytime a database commit is going to occur. . 7 Fire the Post-Database-Commit trigger. . 3 Fire the Pre-Commit trigger. Pre-Delete Journaling.Fire the Post-Delete trigger.Copy Value From Item. such as setting up special locking requirements. .Fire the Pre-Delete trigger.Check the record uniqueness. Pre-Commit: Fires once if form changes are made or uncommitted changes are posted 2. For all inserted or updated records of the block in sequential order: If it is an inserted record: . It fires once for each record that is marked for delete.

BEGIN /* ** Fetch the next sequence number from the ** explicit cursor directly into the item in ** the Order record.. Example:2 This example assigns a primary key field based on a sequence number. which will be written to the ID column when the row is subsequently inserted. Note: The Insert Allowed and Keyboard Navigable properties on :S_ORD. and then writes a row into an auditing table. ** but explicit cursor is more efficient. */ OPEN next_ord. before a row is inserted. Pre-Insert Fires during the Post and Commit Transactions process.. PRE-DELETE TRIGGER -DECLARE CURSOR C1 IS SELECT ’anything’ FROM S_ORD WHERE customer_id = :S_CUSTOMER. check constraints Usage Notes: Use a Pre–Insert trigger to perform the following tasks: • change item values • keep track of the date a record is created and store that in the record prior to committing Example:1 This Pre-Insert trigger on the S_ORD block assigns an Order ID from the sequence S_ORD_ID. If you use this method. Generate sequence numbers. DECLARE CURSOR next_ord IS SELECT orderid_seq. RAISE form_trigger_failure. /* ** Make sure we populated a new order id ok. FETCH next_ord INTO :Order. automatically generated columns.INTO.. End.id should be No. FETCH C1 INTO :GLOBAL. END.id. ELSE CLOSE C1. CLOSE next_ord. Final checks before row deletion 3.nextval INTO :S_ORD. recording the new upper value for the sequence. so that the user does not enter an ID manually.dual. You can also assign sequence numbers from a table. Begin SELECT S_ORD_ID.OrderId. flagging creation of a new order.id FROM SYS. journaling.dummy. It fires once for each record that is marked for insert. Could use SELECT. */ . • Use Post-Insert to update the sequence table.Shik Mahamood Ali 64 • 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. END IF. IF C1%FOUND THEN MESSAGE(’There are orders for this customer!’).NEXTVAL FROM dual. BEGIN OPEN C1.. then two transactional triggers are usually involved: • Use Pre-Insert to select the next available number from the sequence table (locking the row to prevent other users from selecting the same value) and increment the value by the required amount.

/* ** Insert a row into the audit table */ INSERT INTO ord_audit( orderid. 4. END IF.5% to 20%’ */ oper_desc := ’Changed Discount from ’|| TO_CHAR(old_discount)||’% to ’|| TO_CHAR(new_discount)||’%’. including timestamp and username making the change.g.Discount_Pct. It fires once for each record that is marked for update. FETCH old_value INTO old_discount.CustId. BEGIN /* ** Fetch the old value of discount percentage from the database by CustomerId. implement foreign-key update rule. check constraints Usage Notes: Use a Pre–Update trigger to audit transactions.Discount_Pct will be the *new* value we’re getting ready to commit and we want to record for posterity the old and new values. Pre-Update Fires during the Post and Commit Transactions process. timestamp ) VALUES ( :Order.Shik Mahamood Ali 65 IF :Order.SYSDATE ).CustId. auto-generated columns. We need to do this since the value of :Customer. e. username.OrderId. /* ** Insert the audit record with timestamp and user */ INSERT INTO cust_audit( custid.USER. ’New Order’. CURSOR old_value IS SELECT discount_pct FROM customer WHERE CustId = :Customer. END. We could use SELECT. DECLARE old_discount NUMBER. CLOSE old_value. On-Commit .SYSDATE ). ** ’Changed Discount from 13. oper_desc VARCHAR2(80). operation. USER.. username. /* ** If the old and current values are different. 5.oper_desc. Journaling. operation. then we need to write out an audit record */ IF old_discount <> new_discount THEN /* Construct a string that shows the operation of Changing the old value to the new value. new_discount NUMBER := :Customer.INTO but choose an explicit cursor for efficiency. END IF.. RAISE Form_Trigger_Failure. END. Example: The following example writes a row into an Audit Table showing old discount and new discount for a given customer. timestamp ) VALUES ( :Customer. */ OPEN old_value.OrderId IS NULL THEN Message(’Error Generating Next Order Id’). before a row is updated.

6. that is. On-Insert Fires during the Post and Commit Transactions process when a record is inserted. include a call to the DELETE_RECORD built–in. Specifically. no action is performed */ END. this operation occurs after all records that have been marked as updates. On-Delete Fires during the Post and Commit Transactions process. To perform the default Form Builder processing from this trigger. The trigger fires once for each row that is marked for deletion from the database. inserts the current record into the database during Post and Commit Transactions processing. 7. BEGIN UPDATE emp SET termination_date = SYSDATE WHERE empno = :Emp. If the application is running against ORACLE. END IF. call to the COMMIT_FORM built–in. This built-in is included primarily for applications that will run against a non-ORACLE datasource. Description When called from an On-Insert trigger. it fires after the Pre–Delete trigger fires and before the Post–Delete trigger fires. Usage Notes: • Use an On–Commit trigger to change the conditions of normal Oracle Forms commit processing to fit the particular requirements of a commit to a non–ORACLE database. Usage Notes: • • Use an On–Delete trigger to replace the default Oracle Forms processing for handling deleted records during transaction posting. when Form Builder would normally insert a record in the database. and deletes have been posted to the database. rather than actually deleting the employee from the database. By default. Specifically. Example: This example disables the commit operation when running against a datasource that does not support transaction control. It fires once for each row that is marked for insertion into the database. BEGIN IF Get_Application_Property(DATA_SOURCE) = ’ORACLE’ THEN Commit_Form.Shik Mahamood Ali 66 Fires whenever Oracle Forms would normally issue a database commit statement to finalize a transaction. to delete a record from your form or from the database. the commit operation behaves normally. To perform the default Oracle Forms processing from this trigger. Usage Notes • • Use an On-Insert trigger to replace the default Form Builder processing for handling inserted records during transaction posting. Syntax PROCEDURE INSERT_RECORD. . /* ** otherwise.Empno. include a call to the INSERT_RECORD built-in. inserts. END. • To perform the default processing from this trigger. it fires after the Pre-Insert trigger fires and before the Post-Insert trigger fires. replacing the actual database delete of a given row. Example: This example updates the employee table to set the Termination_Date.

On-Update Fires during the Post and Commit Transactions process. include a call to the UPDATE_RECORD built–in.. . • Form Builder uses and retrieves ROWID. updates.WHERE ROWID = :ROWID DELETE FROM base_table WHERE ROWID = :ROWID DML Statements Issued During Commit Processing Rules: • DML statements may fire database triggers..Using_Transactional_Triggers = 'TRUE' THEN User_Exit('my_insrec block=EMP'). and deletes have been posted to the . when Oracle Forms would normally update a record in the database. */ ELSE Insert_Record.) VALUES ( :base_item. 8. To perform the default Oracle Forms processing from this trigger. DML Statements Issued During Commit Processing INSERT INTO base_table ( base_column. This builtin is included primarily for applications that run against a non-ORACLE data source. Usage Notes: • • Use an On–Update trigger to replace the default Oracle Forms processing for handling updated records during transaction posting. 9. • Locking statements are not issued. Specifically. initiates the default Form Builder processing for updating a record in the database during the Post and Commit Transaction process. When called from an On-Update trigger. END IF. base_column = :base_item. ** Trigger: On-Insert */ BEGIN /* ** Check the global flag we setup at form startup */ IF :Global. Note that the Post-Forms-Commit trigger fires after inserts. End. /* ** Otherwise. Begin UPDATE RECORD. perhaps based on a parameter. it fires after the Pre–Update trigger fires and before the Post–Update trigger fires. do the right thing.. :base_item. after the database commit occurs. ..Shik Mahamood Ali 67 /* ** Built-in: INSERT_RECORD ** Example : Perform Form Builder standard insert processing ** based on a global flag setup at startup by the ** form. Post – Database Commit Description Fires once during the Post and Commit Transactions process... END. • The Update Changed Columns Only and Enforce Column Security properties affect UPDATE statements..) UPDATE base_table SET base_column = :base_item. base_column. It fires once for each row that is marked for update in the form.

RETURN (:System. Post-Database-Commit Determines if commit was successful. Post – Form . without posting changes to the database. END. If the operator or the application initiates a Commit when there are no records in the form have been marked as inserts. such as updating an audit trail. It fires once for each row that is deleted from the database during the commit process.'Global.Did_DB_Commit'). after a row is deleted. RETURN (:System. The Post-DatabaseCommit Trigger fires after Form Builder issues the Commit to finalize the transaction.Did_DB_Commit = FALSE'). updates. END. uncommitted changes 10. Usage Notes Use a Post-Database-Commit trigger to perform an action anytime a database commit has occurred. or deletes. updates.Commit Fires once during the Post and Commit Transactions process.Did_DB_Commit = 'FALSE').Did_DB_Commit := 'FALSE'.Did_DB_Commit := 'FALSE'. */ BEGIN :Global. but before the transaction has been finalized by issuing the Commit. anytime a database commit is about to occur. Example /* ** FUNCTION recs_posted_and_not_committed ** RETURN BOOLEAN IS BEGIN Default_Value('TRUE'.Shik Mahamood Ali 68 database. form or block Usage Notes: . If there are records in the form that have been marked as inserts. */ BEGIN :Global. Usage Notes • • Use a Post-Forms-Commit trigger to perform an action.'Global. the Post-Forms-Commit trigger fires after these changes have been written to the database but before Form Builder issues the database Commit to finalize the transaction. Post-Forms-Commit Checks complex multirow constraints Example This example can be used in concert with the Post-Database-Commit trigger to detect if records have been posted but not yet committed. or deletes.Form_Status = 'QUERY' AND :Global. END. /* FUNCTION recs_posted_and_not_committed RETURN BOOLEAN IS BEGIN Default_Value('TRUE'. determines if there are posted.Did_DB_Commit').Form_Status = 'QUERY'AND :Global. Post – Delete Fires during the Post and Commit Transactions process. END. Form Builder fires the Post-Forms-Commit trigger immediately. 11.

It fires once for each row that is updated in the database during the commit process. Example .username). 12. Example 1 Keeping an Audit Trail :GLOBAL.id.Shik Mahamood Ali 69 Use a Post–Delete trigger to audit transactions.2 Begin Delete from S_ORD SET WHERE id = :S_ORD.1 Begin . Usage Notes: Use a Post–Update trigger to audit transactions. Example . Post – Update Fires during the Post and Commit Transactions process. Post – Insert Fires during the Post and Commit Transactions process. SYSDATE. Example . End.1 Begin INSERT INTO delete_audit (id. End.:GLOBAL. just after a record is inserted. RAISE form_trigger_failure. include EXCEPTION section in trigger. Post-Insert trigger: Begin INSERT INTO LOG_TAB (LOG_VAL. Write changes to nonbase tables.||SQLERRM). LOG_USER) VALUES(:S_DEPT. EXCEPTION WHEN OTHERS THEN MESSAGE(’Error! ’.id. USER ). • • • Use a Post-Insert trigger to audit transactions. who_did_it)VALUES ( :S_ORD. after a row is updated. 13. timestamp.id. IF SQL%NOTFOUND THEN MESSAGE(’Record not found in database’). Else Messafe(SQL%rowcount|| “ rows Deleted”).along with a time stamp and the user who performed the update.insert_tot)+1).insert_tot := TO_CHAR(TO_NUMBER(:GLOBAL. END IF. Example 2 To handle exceptions. End. This Post-Update trigger writes the current record ID to the UPDATE_AUDIT table. Gather statistics on applied changes. It fires once for each record that is inserted into the database during the commit process.

.Select Fires when Form Builder would normally execute the open cursor. and execute phases of a query. and then writes a row into an auditing table. IF :Order. RAISE Form_Trigger_Failure. */ OPEN next_ord. parse. • Example . Specifically. FETCH next_ord INTO :Order.2 Begin UPDATE S_ORD SET date_shipped = SYSDATE WHERE id = :S_ORD. timestamp.LAST_QUERY Fires after Form Builder has constructed the block SELECT statement based on the query conditions. timestamp ) VALUES ( :Order. 70 INSERT INTO update_audit (id. End.’New Order’. but before it issues this statement Use a Pre-Select trigger to prepare a query prior to execution against a non-ORACLE data source.OrderId. Example . 15. RAISE form_trigger_failure.1 . END IF. IF SQL%NOTFOUND THEN MESSAGE(’Record not found in database’). 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. after Form Builder constructs the SELECT statement to be issued.OrderId. DECLARE CURSOR next_ord IS SELECT orderid_seq. username. END. parse.. CLOSE next_ord. but before the statement is actually issued. Query Processing Triggers Uses 14. Pre – Select Fires during Execute Query and Count Query processing. who_did_it)VALUES ( :S_ORD. END IF.id. include a call to the SELECT_RECORDS built-in.id.Shik Mahamood Ali USER ). flagging creation of a neworder. /** Insert a row into the audit table INSERT INTO ord_audit( orderid. and execute phases.OrderId IS NULL THEN Message(’Error Generating Next Order Id’).NEXTVAL FROM dual.INTO. Could use SELECT. On . Note that the SELECT statement can be examined in a Pre-Select trigger by reading the value of the system variable SYSTEM. On-Select replaces open cursor.SYSDATE ). Usage Notes • Use an On-Select trigger to open and execute the database cursor. This example assigns a primary key field based on a sequence number. use this trigger when you are retrieving data from a non-ORACLE data source.USER. ** but explicit cursor is more efficient. operation. to identify the records in the database that match the current query criteria. BEGIN /** Fetch the next sequence number from the Explicit cursor directly into the item in the Order record. SYSDATE. To perform the default Form Builder processing from this trigger. End.

– It raises FORM_TRIGGER_FAILURE. On – Fetch Fires when Form Builder performs a fetch for a set of rows (You can use the CREATE_QUERIED_RECORD built-in to create queried records if you want to replace default fetch processing. IF Form_Failure OR Form_Fatal THEN ABORT_QUERY. End. On–Fetch: DECLARE j NUMBER := Get_Block_Property(blk_name.) • On-Fetch continues to fire until: – It fires without executing CREATE_QUERIED_RECORD.empno := emprow.. END LOOP. .' and a built-in subprogram.j LOOP /* ** Try to get the next row. END IF.ENAME. 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. IF form_fatal OR form_failure THEN raise form_trigger_failure. BEGIN FOR ctr IN 1. The trigger will fire once for each record that is to be fetched.Get_Next_Row(emprow).rowid := emprow. – The query is closed by the user or by ABORT_QUERY. 16.ename := emprow.Shik Mahamood Ali 71 In the following example. :Emp. emprow emp%ROWTYPE.EMPNO. It fires before any records are actually retrieved through fetch processing. :Emp. Create_Queried_Record. the On-Select trigger is used to call a user exit. but before it fetches the records The Post-Select trigger fires after the default selection phase of query processing.ROWID. to perform a query against a database. ELSE /* ** Perform the default Form Builder task of opening the query. */ Select_Records. 'Query. RECORDS_TO_FETCH). SELECT_RECORDS. Begin IF Get_Application_Property(DATASOURCE) = 'DB2' THEN User_Exit ( 'Query' ). Post-Select Trigger Description Fires after Form Builder has constructed and issued the block SELECT statement. or after the successful execution of the On-Select trigger. :Emp. 15. END IF. */ EXIT WHEN NOT MyPackage.

j).1 This example calls a user-named subprogram to count the number of records to be retrieved by the current query criteria. On – Count Fires when Form Builder would usually perform default Count Query processing to determine the number of rows that match the query conditions Fires when Form Builder would normally perform default Count Query processing to determine the number of rows in the database that match the current query criteria. and sets the Query_Hits property appropriately. Example 3 /* ** Built-in: COUNT_QUERY ** Example: Perform Form Builder count query hits processing. perhaps based on a parameter. Decide whether to use this Built-in or a user ** exit based on a global flag setup at startup by the form. Form Builder issues the standard query hits message: FRM-40355: Query will retrieve <n> records.QUERY_HITS. • To perform the default Form Builder processing from this trigger.Name_In('DEPT. Example 2 /* ** Built-in: COUNT_QUERY ** Example: Display the number of records that will be retrieved ** by the current query. • Form Builder 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.Shik Mahamood Ali END IF.DNAME')). BEGIN j := Recs_Returned('DEPT'. 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. */ BEGIN END. • If you are replacing default processing. the message reports 0 records identified. Usage Notes • Use an On-Count trigger to replace default Count Query processing in an application running against a non-ORACLE data source. Set_Block_Property('DEPT'. Count_Query. 72 16. DECLARE j NUMBER. Example . END. When the On-Count trigger completes execution. include a call to the built-in. END. * Trigger: On-Count */ . In such a case.

Form Builder queries the database to get the next value from the SEQUENCE whenever the Create Record event occurs.Using_Transactional_Triggers = ’TRUE’ THEN User_Exit(’my_seqnum seq=EMPNO_SEQ’). 17.:control.QUERY_HITS.Trigger_Block. Replaces the default series of events that occurs when Form Builder interacts with the database to get the next value from a SEQUENCE object defined in the database.hits).HITS item. Suppress or override this functionality with an On-Sequence-Number trigger. /* ** Otherwise. /* ** Deposit the number of query hits in the appropriate ** block property so Form Builder can display its normal ** status message.Using_Transactional_Triggers = 'TRUE' THEN /* ** User exit returns query hits count back into the ** CONTROL. */ ELSE END. call the GENERATE_SEQUENCE_NUMBER built-in. Example: /* ** Built–in: GENERATE_SEQUENCE_NUMBER ** Example: Perform Oracle Forms standard sequence number processing based on a global flag setup at ** startup by the form. • To perform the default Form Builder processing from this trigger.Shik Mahamood Ali BEGIN 73 /* ** Check the global flag we set during form startup */ IF :Global. */ ELSE Generate_Sequence_Number. perhaps based on a parameter. Count_Query.On-Sequence-Number Trigger Description Fires when Form Builder would normally perform the default processing for generating sequence numbers for default item values. . ** Trigger: On–Sequence–Number */ BEGIN /* ** Check the global flag we setup at form startup */ IF :Global. /* ** Otherwise. Usage Notes • When a SEQUENCE is used as a default item value. do the right thing. do the right thing. END IF. */ Set_Block_Property(:System. */ User_Exit('my_count').

checks the uniqueness of a record by constructing and executing the appropriate SQL statement to select for rows that match the current record's primary key values. close cursors. tmp VARCHAR2(1). to close files. 18. On-Check-Unique Trigger examples The following example verifies that the current record in question does not already exist in the DEPT table. When a block has the PRIMKEYB property set to Yes. RAISE Form_Trigger_Failure.'). It fires once for each record that has been inserted or updated. The On-Close trigger fires automatically when the ABORT_QUERY built-in is called from an On-Select trigger. by default. BEGIN OPEN chk_unique. Form Builder displays message FRM-40600: Record has already been inserted. END. Form Builder. 19. call the CHECK_RECORD_UNIQUENESS built-in. Form Builder always checks for unique primary key values. Replaces the default processing for checking record uniqueness. or when the operator or the application aborts the query. Usage Notes To perform the default processing from this trigger. On-Check-Unique Trigger 74 Description During a commit operation. In the case of an update. If a duplicate row is found. specifically. On-Close Trigger Description Fires when an operator or the application causes a query to close. DECLARE CURSOR chk_unique IS SELECT 'x' FROM dept WHERE deptno = :dept. END. . FETCH chk_unique INTO tmp. CLOSE chk_unique. IF tmp IS NOT NULL THEN Message('This department already exists. END IF. The On-Close trigger augments the normal Form Builder "close cursor" phase of a query. Form Builder closes a query when all of the records identified by the query criteria have been fetched. For a record that has been marked for insert. By default. Usage Notes • • Use an On-Close trigger after using the On-Select or On-Fetch triggers. and free memory.Shik Mahamood Ali END IF. Form Builder checks for unique primary key values only if one or more items that have the Primary Key item property have been modified.deptno. the On-Check-Unique trigger fires when Form Builder normally checks that primary key values are unique before inserting or updating a record in a base table.

Shik Mahamood Ali 75 Example The following example releases memory being used by a user-defined data access method via the transactional triggers.UPDATEABLE. END IF. Example The following example sets salary and commission text items in the current block to disabled and non-updateable. on_or_off NUMBER.UPDATEABLE. Set_Item_Property(itm_id. END IF.ENABLED. Form Builder enforces column security by querying the database to determine the base table columns to which the current form operator has update privileges.ENABLED. END.Sal').on_or_off). 20. On-Rollback Trigger Description Fires when Form Builder would normally issue a ROLLBACK statement. For columns to which the operator does not have update privileges. Form Builder makes the corresponding base table items in the form non-updateable by setting the Update Allowed item property Off dynamically. to roll back a . itm_id := Find_Item('Emp. Set_Item_Property(itm_id. BEGIN IF NOT role_is_set('SUPERUSER') THEN on_or_off := PROPERTY_OFF.on_or_off).Comm'). END. Form Builder performs this operation at form startup. ELSE on_or_off := PROPERTY_ON. processing each block in sequence. Usage Notes To perform the default processing from this trigger. DECLARE itm_id Item. BEGIN IF NOT my_data source_open('DX110_DEPT') THEN my_datasource_close('DX110_DEPT'). By default. call the ENFORCE_COLUMN_SECURITY built-in. Set_Item_Property(itm_id. On-Column-Security Trigger Description Fires when Form Builder would normally enforce column-level security for each block that has the Enforce Column Security block property set On. 21. unless the SUPERUSER role is enabled.on_or_off). Set_Item_Property(itm_id. itm_id := Find_Item('Emp. Only users with the user-defined SUPERUSER role can change these number fields.on_or_off).

(NULL = Full Rollback)*/ sp_name := Get_Application_Property(SAVEPOINT_NAME).Using_Transactional_Triggers = 'TRUE' THEN User_Exit('my_rollbk name='||sp_name). DECLARE connected BOOLEAN:=FALSE. On-Logon Trigger Fires once per logon when Oracle Forms normally initiates the logon sequence. END. ** Decide whether to use this built-in based on a ** global flag setup at startup by the form. J. Usage Notes Use an On-Rollback trigger to replace standard Form Builder rollback processing. include a call to the LOGON built–in. ** perhaps based on a parameter.Shik Mahamood Ali 76 transaction to the last savepoint that was issued. Usage Notes: Use an On–Logon trigger to initiate a logon procedure to a non–ORACLE data source. ** Trigger: On-Rollback */ DECLARE sp_name VARCHAR2(80). END IF . ELSE Issue_Rollback(sp_name). 2. particularly to a nonORACLE data source. You can supply a NULL command to this trigger to bypass the connection to a data source.LOGON TRANSACTION TRIGGERS 1. include a call to the ISSUE_ROLLBACK built-in. . • • • Pre–Logon and Post–Logon triggers fire as part of the logon procedure. BEGIN /* Get the name of the savepoint to which Form Builder needs to ** rollback. Usage Notes Use a Pre-Logon trigger to prepare the form for the logon procedure. To perform the default Oracle Forms processing from this trigger. To perform default Form Builder processing from this trigger. /* ** Check the global flag we setup at form startup */ IF :Global. Pre-Logon Trigger Fires just before Form Builder initiate a logon procedure to the data source. ISSUE_ROLLBACK examples /* ** Built-in: ISSUE_ROLLBACK ** Example: Perform Form Builder standard Rollback processing. if you want to create an application that does not require a data source.

un:=GET_APPLICATION_PROPERTY( USERNAME ). END IF. END LOOP. END. IF FORM_SUCESS THEN Connected:=TRUE. BEGIN 77 SET_APPLICATION_PROPERTY(CURSOR_STYLE.’DEFAULT’). cs VARCHAR2(30). Example This example calls a user exit to log the current username and time to an encrypted audit trail file on the file system. For example. WHILE CONNECTED = FALSE AND tries > 0 LOOP LOGON_SCREEN. The successful execution of the On-Logon trigger. cs:= GET_APPLICATION_PROPERTY( CONNECTION_STRING ). LOGON( un. IF NOT CONNECTED THEN MESSAGE(‘Too many tries’). pw:=GET_APPLICATION_PROPERTY( PASSWORD ). pw VARCHAR2(30). POST-LOGON TRIGGER Description Fires after either of the following events: • • The successful completion of Form Builder default logon processing. RAISE FORM_TRIGGER_FAILURE. the COPY built-in cannot be called from a Pre-Logout trigger . Pre-Logout Trigger Fires once before Form Builder initiate a logout procedure. un NUMBER. User_Exit('LogCrypt '|| USER||' ' ||TO_CHAR(SYSDATE. which for security reasons is outside the database.Shik Mahamood Ali tries NUMBER:=3. Usage Notes • • Use a Pre-Logout trigger to prepare the form for logging out from the data source. the results are undefined. Tries:=tries-1. 4. BEGIN END. FALSE ). pw || ‘@’ || CS . particularly a non-ORACLE data source. If you call certain built-ins from within one of the Logout triggers. 3. END IF.'YYYYMMDDHH24MISS')).

When-Mouse-Click Trigger . include a call to the LOGOUT built-in. J.Shik Mahamood Ali 78 because Pre-Logout fires after the Leave the Form event. If you call certain built-ins from within one of the Logout triggers. 6. END. Usage Notes • Use a Post-Logout trigger to audit or to perform tasks on an Form Builder 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.’YYYYMMDDHH24MISS’)). BEGIN User_Exit(’LogCrypt ’||USER||’ ’ || TO_CHAR(SYSDATE.MOUSE TRIGGERS 1. which for security reasons is outside the database. The successful execution of the On-Logout trigger. Because the form is no longer accessible. For example. Post-Logout Trigger Description Fires after either of the following events: • • Form Builder successfully logs out of ORACLE. On-Logout Trigger Fires when Form Builder normally initiates a logout procedure from Form Builder and from the RDBMS. the results are undefined. the COPY operation is not possible. Because the form is no longer accessible. Usage Notes • • • Use an On-Logout trigger to replace the default logout processing either from the RDBMS or from a non-ORACLE data source. you cannot call COPY from a Pre-Logout trigger because Pre-Logout fires after the Leave the Form event. This example calls a user exit to log the current username and time to an encrypted audit trail file on the file system. 5. a COPY operation is not possible. Because the form is no longer accessible at this point. a COPY operation is not possible. the results are undefined. For example. To perform the default Form Builder processing from this trigger. you cannot call the COPY built-in from a Pre-Logout trigger because Pre-Logout fires after the Leave the Form event.

when the mouse is clicked within the item Three events must occur before a When-Mouse-Click trigger will fire: • • • Mouse down Mouse up Mouse click Any trigger that is associated with these events will fire before the When-Mouse-Click trigger fires. Usage Notes Use a When-Mouse-DoubleClick trigger to perform an action every time the operator DoubleClick the mouse within an item and/or canvas. Usage Notes Use the When-Mouse-Click trigger to perform an action every time the operator clicks the mouse within an item and/or canvas. when the mouse is double-clicked within the item Six events must occur before a When-Mouse-DoubleClick trigger will fire: • • • • • • Mouse Mouse Mouse Mouse Mouse Mouse down up click down up double-click Any trigger that is associated with these events will fire before the When-Mouse-DoubleClick trigger fires. when the mouse is double-clicked within any canvas or item in the form if attached to a block. when the mouse is clicked within any item in the block if attached to an item. when the mouse is clicked within any canvas or item in the form if attached to a block. when the mouse is double-clicked within any item in the block if attached to an item.Shik Mahamood Ali Description 79 Fires after the operator click the mouse if one of the following events occurs: • • • if attached to the form. When-Mouse-DoubleClick Trigger Description Fires after the operator double-clicks the mouse if one of the following events occurs: • • • if attached to the form. 2. When-Mouse-DoubleClick Trigger examples Example .

assume that your When-Mouse-Enter trigger causes Alert_One to appear whenever the mouse enters Canvas_One.Shik Mahamood Ali 80 Assume that an application requires Behavior A when the operator clicks the mouse and Behavior B when the operator double-clicks the mouse. when the mouse enters any canvas or item in the form if attached to a block. . as soon as the mouse enters that area. 4. Finally. When-Mouse-Down Trigger Description Fires after the operator presses down the mouse button if one of the following events occurs: • • • if attached to the form. a product information window must appear. Do not use the When-Mouse-Enter trigger on a canvas that is larger than the window. Changing a tooltip's property in a When-Mouse-Enter trigger cancels the tooltip before it is ever shown. Assume also that your application contains two canvases. when the mouse enters any item in the block if attached to an item. when the mouse is pressed down within any item in the block if attached to an item. when the mouse is pressed within the item Usage Notes • Use a When-Mouse-Down trigger to perform an action every time the operator presses down the mouse button within an item and/or canvas. For example. For example. Doing so may cause the modal window to appear unnecessarily. assume that Alert_One displays within Canvas_Two's border. if the operator clicks the mouse. Canvas_One and Canvas_Two. Note: The mouse down event is always followed by a mouse up event. the trigger fires and returns focus to the previous target. If the operator double-clicks the mouse. 3. Canvas_One and Canvas_Two do not overlap each other. an online help window must appear. However. when the mouse enters the item Usage Notes Use a When-Mouse-Enter trigger to perform an action every time the mouse enters an item or canvas. but appear side by side on the screen. assume that the mouse has entered Canvas_One causing the When-Mouse-Enter trigger to fire which in turn causes Alert_One to appear. The user is able to scroll the canvas to see the items. Further. when the mouse is pressed down within any canvas or item in the form if attached to a block. Be careful when calling a modal window from a When-Mouse-Enter trigger. When-Mouse-Enter Trigger Description Fires when the mouse enters an item or canvas if one of the following events occurs: • • • if attached to the form. so the user is never able to click on those items. Iconic buttons and items on the canvas below the initial window cannot be selected.

when the operator moves the mouse out of Canvas_Two. when the mouse moves within the item Usage Notes • Use the When-Mouse-Move trigger to perform an action every time the operator moves the mouse.CURSOR_ITEM.MOUSE_CANVAS = ’CV_ORDER’ THEN :control.save_item_name). End. 5. When-Mouse-Move Trigger Description Fires each time the mouse moves if one of the following events occurs: • • • if attached to the form. The When-Mouse-Move trigger may have performance implications because of the number of times this trigger can potentially fire.save_item_name := :SYSTEM. Alert_One will appear again unnecessarily if the operator subsequently enters Canvas_One with the mouse. when the mouse leaves any item in the block if attached to an item. begin :GLOBAL. .show_help_button begin End. 6.Shik Mahamood Ali 81 When the operator dismisses the message box.id’). when the mouse moves within any item in the block if attached to an item. GO_ITEM(:GLOBAL. This may not be the desired behavior. when the mouse moves within any canvas or item in the form if attached to a block. WHEN-MOUSE-ENTER at Form Level begin IF :SYSTEM.show_help_button := ’?’. when the mouse leaves the item Usage Notes Use a When-Mouse-Leave trigger to perform an action every time the mouse leaves an item and/or canvas. END IF. WHEN-MOUSE-LEAVE trigger on control. when the mouse leaves any canvas or item in the form if attached to a block. HIDE_VIEW(’cv_help’). End. SHOW_VIEW(’cv_help’). In addition. GO_ITEM(’s_ord. When-Mouse-Leave Trigger Description Fires after the mouse leave an item or canvas if one of the following events occurs: • • • if attached to the form. any When-Mouse-Leave triggers associated with this event will fire.

which in turn calls the user-named subprogram defined in the current form. rather than for Item_Two. To execute a user–named trigger. K. when the mouse up event is received within any canvas or item in form attached to a block. When-Mouse-Up Trigger 82 Description Fires each time the operator presses down and releases the mouse button if one of the following events occurs: • • • if a if if attached to the form. you must call the EXECUTE_TRIGGER built–in procedure. which is defined in a different document. The mouse up event is always associated with the item that received the mouse down event. For example. (User-named subprograms defined in a form cannot be called directly from menu PL/SQL.Shik Mahamood Ali 7. If the operator presses down the mouse on Item_One. When more than one user-named trigger has the same name. Create a user-named trigger to execute user-named subprograms defined in a form document from menu PL/SQL commands and user-named subprograms. Each user–named trigger defined at the same definition level must have a unique name.OTHER TRIGGERS 1. Usage Notes User-named PL/SQL subprograms can be written to perform almost any task for which one might use a user-named trigger. when the mouse up event is received within an item Two events must occur before a When-Mouse-Up trigger will fire: • • Mouse down Mouse up Usage Notes Use the When-Mouse-Up trigger to perform an action every time the operator presses and releases the mouse. the mouse up trigger will fire for Item_One. as shown here: Execute_Trigger(’my_user_named_trigger’). As with all triggers.) In the menu PL/SQL. If no such key . User-Named Trigger A user–named trigger is a trigger that you define yourself in a form. call the EXECUTE_TRIGGER built-in to execute a usernamed trigger. Note: You can write user–named PL/SQL subprograms to perform almost any task for which you might use a user–named trigger. and then call explicitly from other triggers or user–named subprograms. but then releases the mouse on Item_Two. DO_KEY built-in Executes the key trigger that corresponds to the specified built-in subprogram. the trigger defined at the lowest level has precedence. assume that there is a When-Mouse-Up trigger attached to Item_One. It is most practical to define user-named triggers at the form level. when the mouse up event is received within any item in a block attached to an item. the scope of a user-named trigger is the definition level and below.

** Trigger: On-Savepoint */ DECLARE sp_name VARCHAR2(80).consequently. To accept a specific key name. if no On-Savepoint trigger were present. do the right thing. By default. the Savepoint_Name application property returns the name of the next savepoint that Form Builder would issue by default. Form Builder issues savepoints at form startup. /* Check the global flag we setup at form startup */ IF :Global. DO_KEY restrictions DO_KEY accepts built-in names only. */ BEGIN END. then the specified subprogram executes. Do_Key('Execute_Query'). /* ** Built-in: ISSUE_SAVEPOINT ** Example: Perform Form Builder standard savepoint processing. Form Builder does not issue savepoints and. /* Otherwise. Savepoint_Name returns the name of the savepoint to which Form Builder would roll back. BEGIN /* Get the name of the savepoint Form Builder needs to issue */ sp_name := Get_Application_Property(SAVEPOINT_NAME). 2.Shik Mahamood Ali 83 trigger exists. In an On-Rollback trigger . */ ELSE . and at the start of each Post and Commit Transaction process. Suppress default savepoint processing by setting the Savepoint Mode form document property to Off. include a call to the ISSUE_SAVEPOINT built-in. DO_KEY examples /* ** Built-in: DO_KEY ** Example: Simulate pressing the [Execute Query] key. the On-Savepoint trigger never fires. On-Savepoint Trigger Fires when Form Builder would normally issue a Savepoint statement. ** Decide whether to use this built-in based on a global flag setup at startup by the form. not key names: DO_KEY(ENTER_QUERY). In an On-Savepoint trigger.perhaps based on a parameter.Using_Transactional_Triggers = 'TRUE' THEN User_Exit('my_savept name='||sp_name). use the EXECUTE_TRIGGER built-in: EXECUTE_TRIGGER('KEY_F11'). When Savepoint Mode is Off. Syntax PROCEDURE DO_KEY (built-in_subprogram_name VARCHAR2). This behavior is analogous to pressing the corresponding function key. Usage Notes To perform default Form Builder processing from this trigger.

Usage Notes: • Use an On–Lock trigger to replace the default Oracle Forms processing for locking rows. you must include a Post-Query trigger in addition to your When-Validate-Item trigger. the When-ValidateItem trigger does not fire. END. In other words. Usage Notes • • The Post-Change trigger is included only for compatibility with previous versions of Form Builder. For example. use On–Lock if you are accessing a non–ORACLE data source directly. On-Lock Trigger Fires whenever Oracle Forms would normally attempt to lock a row. not by way of Open Gateway. An operator returns a value into an item by making a selection from a list of values. In this case. See "Usage Notes" below.Shik Mahamood Ali Issue_Savepoint(sp_name). the trigger fires only the first time the operator tries to modify an item in the record. Post-Change Trigger 84 Fires when any of the following conditions exist: • • • The Validate the Item process determines that an item is marked as Changed and is not NULL. Its use is not recommended in new applications.perhaps based on a parameter. • To perform the default Oracle Forms processing from this trigger. Given such changes. Form Builder marks the corresponding items and records as changed. include a call to the LOCK_RECORD built–in. • When the On–Lock trigger fires as a result of an operator trying to modify data. for every row that is to be locked. such as when an operator presses a key to modify data in an item. The trigger does not fire during subsequent modifications to items in the same record. Also. The Post-Query trigger does not have the restrictions of the Post-Change trigger. If you want to circumvent this situation and effectively get rid of the Post-Change trigger. Decide whether to use default processing or a user exit by consulting a global flag setup at startup by the form. Form Builder fetches a non-NULL value into an item. • Use this trigger to lock underlying tables for non–updateable views. You can use Post-Query to make changes to the fetched database values. if you are designing an application for use on a single–user system. END IF. The trigger fires between the key press and the display of the modified data. 3. /* ** Built-in: LOCK_RECORD ** Example: Perform Form Builder standard record locking on the queried record which has just been deleted or updated. ** Trigger: On-Lock */ BEGIN . the trigger fires once. you can use the On–Lock trigger to speed processing by bypassing all lock processing. 3. and the item is not NULL.

Non_Oracle_Datasource = 'TRUE' THEN User_Exit('my_lockrec block=EMP'). 8. 6.Shik Mahamood Ali 85 /* ** Check the global flag we set up at form startup */ IF :Global. 7. do the right thing. but the Query Data Source Columns property must be set so that those items can be passed to the query stored procedure. any of the items may be used. Usage Notes Use this trigger to enable or disable menu items on a pop-up menu before it is displayed. Example: This is an example of a procedure that can be called when Oracle Forms fires the When–Custom–Item–Event Trigger. . This trigger is called when a query operation is necessary. /* ** Otherwise. The system variable SYSTEM. (In a Microsoft Windows environment. Update-Procedure Trigger Automatically created by Form Builder when the update data source is a stored procedure. */ ELSE END IF. Usage Notes When constructing a query. Lock_Record. Pre-Popup-Menu Trigger This trigger is called when a user causes a pop-up menu to be displayed. this occurs when a user presses the right mouse button. Then. When-Custom-Item-Event Trigger Fires whenever a VBX control sends an event to Oracle Forms. the query stored procedure has to use those values to filter the data. Think of this as an On-Update trigger that is called by the system instead of doing default update operations.CUSTOM_ITEM_EVENT_PARAMETERS stores a parameter name that contains the supplementary arguments for an event that is fired by a VBX control. END. TabNumber Number. Think of this as an On-Query trigger that is called by the system instead of doing default query operations. Query-Procedure Trigger Automatically created by Form Builder when the query data source is a stored procedure. Usage Notes: Use a When–Custom–Item–Event trigger to respond to a selection or change of value for a VBX control. DECLARE TabEvent varchar2(80). and the system variable SYSTEM. This trigger is called when a update operation is necessary. 5.CUSTOM_ITEM_EVENT stores the case–sensitive name of the event that occurred.) Actions defined for this trigger are performed before the pop-up menu is displayed. This means that the enter query mode does not happen automatically unless you specify it.

WINDOW_STATE.MAXIMIZE).’CurrTab’). it does not respond to implicit navigation. end if. When-Tab-Page-Changed Fires whenever there is explicit item or mouse navigation from one tab page to another in a tab canvas. • When-Tab-Page-Changed fires only when tab page navigation is explicit. tp_lb := GET_TAB_PAGE_PROPERTY(tp_id. the trigger will fire when the mouse or keyboard is used to navigate between tab pages. Usage Notes • Use a When-Tab-Page-Changed trigger to perform actions when any tab page is changed during item or mouse navigation. For example. /* ** After detecting a Click event. topmost_tab_page). END IF. When-Form-Navigate Trigger Fires whenever any peer form navigation takes place. Goto_Tab_Page(TabNumber).WINDOW_STATE) = ’MAXIMIZE’ THEN SET_WINDOW_PROPERTY(win_id. but the trigger will not fire if an end user presses [Next Item] (Tab) to navigate from one field to another field in the same block. BEGIN tp_nm := GET_CANVAS_PROPERTY('emp_cvs'. else SET_WINDOW_PROPERTY(win_id. tp_id TAB_PAGE. DECLARE win_id WINDOW := FIND_WINDOW(’WINDOW12’).MINIMIZE). BEGIN if (GET_WINDOW_PROPERTY(win_id. identify the ** tab selected. END.Shik Mahamood Ali 86 BEGIN TabEvent := :system.custom_item_event. */ IF (UPPER(TabEvent) = ’CLICK’) THEN TabNumber := VBX. This is an example of a procedure that can be called when Oracle Forms fires the When–Form– Navigate Trigger.WINDOW_STATE. .Get_Property(’TABCONTROL’. Example /* Use a When-Tab-Page-Changed trigger to dynamically change a tab page's label from lowerto upper-case (to indicate to end users if they already have ** navigated to the tab page): */ DECLARE tp_nm VARCHAR2(30). 10. END. 9. and use the user– defined Goto_Tab_Page procedure to navigate to the selected page. form Use a When–Form–Navigate trigger to perform actions when any cross form navigation takes place without relying on window activate and window deactivate events. • When-Tab-Page-Changed does not fire when the tab page is changed programmatically. tp_id := FIND_TAB_PAGE(tp_nm). tp_lb VARCHAR2(30). label). but on different tab pages.

Only end-user action will generate an event. END IF. label.TRIGGER_NODE returns a value of type NODE. When the text list contains values that cannot be displayed (due to the displayable area of the item). Appears as a rectangular box which displays a fixed number of values.TRIGGER_NODE returns a value of type NODE.Shik Mahamood Ali 87 IF tp_lb LIKE 'Sa%' THEN SET_TAB_PAGE_PROPERTY(tp_id. Only enduser action will generate an event. text list. ELSE null. 13. When-Tree-Node-Selected Trigger Fires when a node is selected or deselected. Unlike the poplist or the text list style list items. Usage Notes • SYSTEM. The combo box list item appears as an empty box with an icon to the right. a vertical scroll bar appears. 12. 'SALARY'). . When-Tree-Node-Activated Trigger Fires when an operator double-clicks a node or presses Enter when a node is selected.TRIGGER_NODE is the node the user clicked on. No programmatic action will cause the When-Tree-Node-Activated trigger to fire. allowing the operator to view and select undisplayed values. or combo box DESCRIPTION Combo Box Appears initially as a single field (similar to a text item field). Usage Notes • • SYSTEM.TRIGGER_NODE is the node the user clicked on. Usage Notes • • SYSTEM.TRIGGER_NODE returns a value of type NODE. The user can enter text directly into the combo field or click the list icon to display a list of available values. When-Tree-Node-Expanded Trigger Fires when a node is expanded or collapsed. label. • Defining list items A list item displays a predefined set of choices that   LIST ITEM Poplist Text List are mutually exclusive can be displayed as either a poplist. 11. No programmatic action will cause the When-Tree-Node-Selected trigger to fire. When the operator selects the list icon. 'VACATION'). SYSTEM. Only end-user action will generate an event. END.TRIGGER_NODE is the node the user clicked on. Combines the features found in list and text items. SYSTEM. a list of available choices appears. SYSTEM. ELSIF tp_lb LIKE 'Va%' THEN SET_TAB_PAGE_PROPERTY(tp_id. the combo box style list item will display fixed values and accept one operator-entered value. No programmatic action will cause the When-Tree-Node-Expanded trigger to fire.

Shik Mahamood Ali 88 .

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.