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.

COL’||TO_CHAR(i)||’ NUMBER’... Example 3: /* ** Built–in: FORMS_DDL ** Example: The statement parameter can be a block ** of dynamically created PL/SQL code. Line breaks. ** Create a table with n Number columns.. If you • • • • • If you use FORMS_DDL to execute a valid PL/SQL block: Use semicolons where appropriate. BEGIN my_stmt := ’create table tmp(COL1 NUMBER’. while permitted. FOR I in 2. END IF. . IF NOT Form_Success THEN Message (’Table Creation Failed’). create the table.. COLn). Example 2: /* ** Built–in: FORMS_DDL ** Example: The string can be an expression or variable. are not required.*/ BEGIN Forms_DDL(’create table temp(n NUMBER)’). END LOOP.. BEGIN . Enclose the PL/SQL block in a valid BEGIN/END block structure.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. my_stmt := my_stmt||’)’. /* ** Now. ELSE Message (’Table Created’). */ PROCEDURE Create_N_Column_Number_Table (n NUMBER) IS my_stmt VARCHAR2(2000). 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. */ Forms_DDL(my_stmt). END.N LOOP my_stmt := my_stmt||’. END. ELSE Message (’Table Created’).. Do not end the PL/SQL block with a slash. END IF. ** TEMP(COL1. IF NOT Form_Success THEN Message (’Table Creation Failed’). */ DECLARE procname VARCHAR2(30). COL2.

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

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

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. data_mode NUMBER. update. or delete records. and deletes from within the called form. Runs an indicated form while keeping the parent form active. paramlist_id . QUERY_ONLY Causes Oracle Forms to run the indicated form in Query Only mode.Shik Mahamood Ali 8 The name you gave the parameter list object when you defined it. CALL_FORM (formmodule_name VARCHAR2. allowing the operator to perform inserts. NO_HIDE Causes Oracle Forms to display the called form without clearing the calling form from the screen. A parameter list passed to a form via NEW_FORM cannot contain parameters of type DATA_PARAMETER (a pointer to record group). but not to insert. The data type of the name is CHAR. DO_REPLACE Causes Oracle Forms to replace the default menu application of the calling form with the default menu application of the called form. 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 NUMBER. paramlist_name VARCHAR2). 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. HIDE is the default parameter. 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. Oracle Forms runs the called form with the same Runform preferences as the parent form. CALL_FORM. updates. The name must be enclosed in single quotes. query_mode NUMBER. Parameters: formmodule_name Specifies the formmodule name of the called form. display NUMBER. The data type of the name is CHAR. allowing the operator to query.

activate_mode.session_mode. that is.activate_mode. applications that open more than one form at the same time.paramlist_name). separate database session should be created for the opened form. Call_Form(’lookcust’. session_mode NO_SESSION Specifies that the opened form should share the same database session as the current form. form_name.session_mode). The current form remains current.activate_mode). OPEN_FORM( OPEN_FORM( OPEN_FORM( OPEN_FORM( OPEN_FORM( REPLACE_MENU form_name). OPEN_FORM Opens the indicated form. activate_mode NUMBER. NO_ACTIVATE Opens the form but does not set focus to the form. session_mode NUMBER. paramlist_name Specifies the CHAR name of a parameter list to be passed to the opened form.NO_HIDE. paramlist_id Specifies the unique ID that Oracle Forms assigns to the parameter list at the time it is created. You can optionally include a parameter list as initial input to the called form. activate_mode ACTIVATE Sets focus to the form to make it the active form in the application. 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.session_mode. data_mode NUMBER. form_name Specifies the CHAR name of the form to open.DO_REPLACE. The data type of the name is CHAR.Shik Mahamood Ali 9 Specifies the unique ID Oracle Forms assigns when it creates the parameter list. form_name. form_name. Use the GET_PARAMETER_LIST function to return the ID to a variable of type PARAMLIST.activate_mode. SESSION Specifies that a new. OPEN_FORM (form_name VARCHAR2.paramlist_id). .QUERY_ONLY). The data type of the ID is PARAMLIST. paramlist_name The name you gave the parameter list object when you defined it. paramlist_id PARAMLIST). form_name.

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

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

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

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

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

and on which master block of a master/detail relation.or Post-Form trigger. The following trigger performs this function. The master data block is based on the table with the primary key.MASTER_BLOCK This system variable works with its companion SYSTEM. ELSIF curblk = ’ITEMS’ THEN Go_Block(’CUSTOMERS’). ELSIF curblk = ’CUSTOMERS’ THEN Go_Block(’ORDERS’). When-Database-Record.TRIGGER_BLOCK represents the name of the block where the cursor was located when the current trigger initially fired. The following statement performs this function. 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. The value is NULL if the current trigger is a Pre. END.TRIGGER_BLOCK SYSTEM. using :SYSTEM. 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. 4. 5.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. The value is always a character string. A master-detail relationship equates to the one-tomany relationship in the entity relationship diagram. When-Clear-Block. SYSTEM. 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.Cursor_Block. DECLARE curblk VARCHAR2(30). Go_Block(Name_In(’System. What Is a Relation? .Trigger_Block’)). BEGIN curblk := :System. END IF.CURSOR_BLOCK stored in a local variable.COORDINATION_OPERATION to help an On-Clear-Details trigger determine what type of coordination-causing operation fired the trigger. IF curblk = ’ORDERS’ THEN Go_Block(’ITEMS’). Block – Based Triggers [Block Processing Trigger] When-Create-Record. and the detail data block is based on the table with the foreign key.

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 . for example. or isolate deletion of a record in a master block when corresponding records exist in the detail block by setting the Master Deletes property. S_ORD_S_ITEM. Explicit Relations If a relation is not established when default blocks are created. For example.Delete trigger. Changing the Master Deletes property from the default of Non-Isolated to Isolated results in the removal of the On-Check-Delete-Master trigger. PL/SQL program units and triggers are created automatically when you explicitly create a relation. Master Deletes You can prevent. propagate. 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. Like implicitly created relations.Shik Mahamood Ali 16 A relation is a Form Builder object that handles the relationship between two associated blocks. you can create your own by setting the properties in the New Relation dialog box. 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. This relation is named masterblock_detailblock. you can delete all corresponding line items when an order is deleted. a relation is automatically created.

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. and lengths from the database columns referenced in the SELECT statement. Static record group . 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. 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. the detail records are fetched immediately. Query record group A query record group is a record group that has an associated SELECT statement. On-Populate-Details. The records in a query record group are the rows retrieved by the query associated with that record group. When a coordination-causing event occurs. To fetch the detail records. the operator must navigate to the detail data block and explicitly execute a query. (Deferred False. Deferred Without Auto Query When coordination-causing event occurs. Non-query record groups can be created and modified only at runtime. data types. For example. 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. 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. Default [Immediate] The default setting. Query record groups can be created and modified at design time or at runtime. you can defer querying the line items for an order until the operator navigates to the item block. The columns in a query record group derive their default names. Oracle Forms does not automatically fetch the detail records.

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

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

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

11. Returns information about a specified list of values (LOV). When this property is true a dialog box appear. 3. When Automatic Confirm is set to No. property NUMBER. from this value entered the where clause constructed. Set_LOV_Property('my_lov'. 8.Validation from Lov to text item. When Automatic Skip is set to No. 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 . 9. giving the operator the option to explicitly select the remaining choice or dismiss the LOV.Title property Specifies the title to be displayed for the object. 6. SET_LOV_COLUMN_PROPERTY (lov_id NUMBER. SET_LOV_PROPERTY(lov_id LOV.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. the LOV is dismissed automatically and column values from the single row are assigned to their corresponding return items.Column Mapping This property is used to specify the return item. SET_LOV_COLUMN_PROPERTY Sets the given LOV property for the given LOV. 7.Automatic Refresh property Determines whether Form Builder re-executes the query to populate an LOV that is based on a query record group.Shik Mahamood Ali 21 1. 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.colnum NUMBER. property LOV).value VARCHAR2). 4. property 5. the focus remains in the text item after the operator makes a selection from the LOV.>If it is not specified then value from Lov cannot assigned to the block.GROUP_NAME. In this dialog box any value can be entered.'new_group'). the LOV remains displayed. . 10. Sets the given LOV property for the given LOV.GROUP_NAME Specifies the name of the record group on which an LOV is based. LOV. value NUMBER). 2. 12. GET_LOV_PROPERTY (lov_id. Long List It is used to append a ‘ where clause ‘ to the select statement.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.

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

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

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

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

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

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

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

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

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

width. The EDIT_TEXTITEM procedure invokes the editor associated with the current text item in the form (the default editor. ed_ok). Pass the contents of the :emp. BEGIN itm_x_pos := Get_Item_Property(:System. Edit_Textitem(x. BEGIN mi_id := Find_Menu_Item(’PREFERENCES. */ val := :emp.SYSTEM_EDITOR’). END IF. /* ** Show the appropriate editor at position (10.CHECKED) = ’TRUE’ THEN ed_name := ’system_editor’.14) on the ** screen. message_in. mi_id MenuItem. Show_Editor( ed_id. result).Cursor_Item. ELSE ed_name := ’my_editor1’. IF ed_ok THEN :emp.X_POS). x. Example: /* ** Built–in: SHOW_EDITOR ** Example: Accept input from the operator in a user–defined ** editor. */ DECLARE ed_id Editor. 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. END. val. IF Get_Menu_Item_Property(mi_id. END IF.14. message_out. a user-named editor. 10. ed_ok BOOLEAN.comments := val. y. 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. Use the system editor if the user has ** checked the ”System_Editor” menu item under the ** ”Preferences” menu in our custom menu module. ed_id := Find_Editor( ed_name ). val VARCHAR2(32000). y.comments. or the current system editor). The SHOW_EDITOR procedure displays a user-named editor at the specified display coordinates. ed_name VARCHAR2(40). val. */ DECLARE itm_x_pos NUMBER.Shik Mahamood Ali 31 SHOW_EDITOR(editor_name. IF itm_x_pos > 40 THEN .comments item ** into the editor and reassign the edited contents if ** ’ed_ok’ returns boolean TRUE. height).

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

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

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

and personal standards. They simplify reuse in complex environments. Reusing components enables you to: • Apply standards to simple objects. project. An object library can contain simple objects. • • • • Is a convenient container of objects for reuse Simplifies reuse in complex environments Supports corporate. maintain. and program units. Use copying to export the definition of an object to another module. object groups. unique version of that object in the target module. 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. Any objects owned by the copied object are also copied. store.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. 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 . and they support corporate. such as buttons and items. and distribute standard and reusable objects. • Changes made to a copied object in the source module do not affect the copied object in the target module. you can rapidly create applications by dragging and dropping predefined objects to your form. project. property classes. You can use the Object Library to create. Objects can be used as standards (classes) for other objects. but they are protected against change in the library. and personal standards Simplifies the sharing of reusable components Object libraries are convenient containers of objects for reuse. In addition. Object libraries simplify the sharing of reusable components. by using Object Libraries.

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

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.

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

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

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

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

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

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

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

END. */ wn_id1 := Find_Window(Window1). w := Get_Window_Property(wn_id1. h := Get_Window_Property(wn_id1. Window2 VARCHAR2) IS wn_id1 Window. w NUMBER. 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] .WIDTH). C. Example: /* ** Built–in: RESIZE_WINDOW ** Example: Set Window2 to be the same size as Window1 */ PROCEDURE Make_Same_Size_Win( Window1 VARCHAR2.HEIGHT).[ALL] ( KEY TRIGGERS ) Key Triggers have a one-to-one relationship with specific keys. w. the trigger fires when operator presses a specific key or key-sequence. Replace the default function associated with a function key. BEGIN /* ** Find Window1 and get it’s width and height. h ). you can define a Key-EXIT trigger to replace the default functionality of the [Help] key. h NUMBER. i.Shik Mahamood Ali 48 • Maintain certain visual standards by resetting window size if the window was improperly resized. For example. /* ** Resize Window2 to the same size */ Resize_Window( Window2.e. KEY.

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

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

. 2. RAISE Form_Trigger_Failure. lv_errtyp VARCHAR2(3) := ERROR_TYPE. ELSE . END IF. DECLARE lv_errcod NUMBER := ERROR_CODE.. lv_errtype VARCHAR2(3) := MESSAGE_TYPE... ELSE Message(lv_errtyp||’–’||to_char(lv_errcod)||’: ’||lv_errtxt). lv_errcod NUMBER := MESSAGE_CODE..Shik Mahamood Ali 51 The following example checks specific error message codes and responds appropriately. 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). for example. END IF. END IF. . lv_errtxt VARCHAR2(80) := ERROR_TEXT. END. BEGIN IF (lv_errcod = 40nnn) THEN /* ** Perform some tasks here */ ELSIF (lv_errcod = 40mmm) THEN /* ** More tasks here */ . to replace a default message issued by Form Builder with a custom message. BEGIN IF lv_errcod = 40350 THEN alert_button := Show_Alert(’continue_alert’). 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) := MESSAGE_TEXT. IF alert_button = ALERT_BUTTON1 THEN .. RAISE Form_Trigger_Failure. END.

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

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

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

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

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

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

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

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

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

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

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

Pre-Commit Check user authorization. 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. For all deleted records of the block (in reverse order of deletion): . then: 6 Issue an SQL-COMMIT statement. Pre-Commit: Fires once if form changes are made or uncommitted changes are posted 2.Delete the row from the base table or fire the On-Delete trigger.Fire the Post-Delete trigger.Copy Value From Item.) Usage Notes: Use a Pre–Commit trigger to perform an action. 4 Validate the block (for all blocks in sequential order).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.Fire the Post-Insert trigger. anytime a database commit is going to occur. implement foreign-key delete rule Fires during the Post and Commit Transactions process.Insert the row into the base table or fire the On-Insert trigger. 2 Process save point. . set up special locking Pre-Commit Fires once during commit processing.Check the record uniqueness. 5 Fire the Post-Forms-Commit trigger. such as setting up special locking requirements. . If it is an updated record: Fire the Pre-Update trigger. before base table blocks are processed. Check the record uniqueness Update the row in the base table or fire the On-Update trigger. 3 Fire the Pre-Commit trigger. .Fire the Pre-Insert trigger. . Commit Triggers Uses 1. 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. even if there are no changes to post. . Pre-Delete Journaling. . 7 Fire the Post-Database-Commit trigger. Fire the Post-Update trigger.Fire the Pre-Delete trigger. Usage Notes • Use a Pre-Delete trigger to delete the detail record of a master record. If the current operation is COMMIT. . before a row is deleted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. 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. 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. when the mouse is double-clicked within any canvas or item in the form if attached to a block. 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 clicked within any canvas or item in the form if attached to a block. When-Mouse-DoubleClick Trigger examples Example . 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. 2. when the mouse is clicked within any item in the block if attached to an item. 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.

Finally. Note: The mouse down event is always followed by a mouse up event. Assume also that your application contains two canvases. However. the trigger fires and returns focus to the previous target. 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. . if the operator clicks the mouse. Do not use the When-Mouse-Enter trigger on a canvas that is larger than the window.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. assume that the mouse has entered Canvas_One causing the When-Mouse-Enter trigger to fire which in turn causes Alert_One to appear. If the operator double-clicks the mouse. assume that your When-Mouse-Enter trigger causes Alert_One to appear whenever the mouse enters Canvas_One. Changing a tooltip's property in a When-Mouse-Enter trigger cancels the tooltip before it is ever shown. 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. when the mouse is pressed down within any item in the block if attached to an item. but appear side by side on the screen. Canvas_One and Canvas_Two do not overlap each other. an online help window must appear. as soon as the mouse enters that area. when the mouse enters any item in the block if attached to an item. The user is able to scroll the canvas to see the items. 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. 4. Iconic buttons and items on the canvas below the initial window cannot be selected. Doing so may cause the modal window to appear unnecessarily. when the mouse is pressed down within any canvas or item in the form if attached to a block. For example. assume that Alert_One displays within Canvas_Two's border. when the mouse enters any canvas or item in the form if attached to a block. Further. a product information window must appear. so the user is never able to click on those items. Be careful when calling a modal window from a When-Mouse-Enter trigger. 3. Canvas_One and Canvas_Two. 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. For example.

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

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

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

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

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

identify the ** tab selected. Goto_Tab_Page(TabNumber). tp_id := FIND_TAB_PAGE(tp_nm). and use the user– defined Goto_Tab_Page procedure to navigate to the selected page. • When-Tab-Page-Changed fires only when tab page navigation is explicit. end if. Usage Notes • Use a When-Tab-Page-Changed trigger to perform actions when any tab page is changed during item or mouse navigation. */ IF (UPPER(TabEvent) = ’CLICK’) THEN TabNumber := VBX. 10. For example. /* ** After detecting a Click event. the trigger will fire when the mouse or keyboard is used to navigate between tab pages.WINDOW_STATE.Get_Property(’TABCONTROL’. BEGIN if (GET_WINDOW_PROPERTY(win_id. label). it does not respond to implicit navigation. END IF.Shik Mahamood Ali 86 BEGIN TabEvent := :system. tp_id TAB_PAGE. BEGIN tp_nm := GET_CANVAS_PROPERTY('emp_cvs'. else SET_WINDOW_PROPERTY(win_id.custom_item_event. DECLARE win_id WINDOW := FIND_WINDOW(’WINDOW12’). but on different tab pages. 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.WINDOW_STATE) = ’MAXIMIZE’ THEN SET_WINDOW_PROPERTY(win_id.MAXIMIZE). tp_lb := GET_TAB_PAGE_PROPERTY(tp_id.’CurrTab’). 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).WINDOW_STATE. • When-Tab-Page-Changed does not fire when the tab page is changed programmatically. tp_lb VARCHAR2(30). When-Form-Navigate Trigger Fires whenever any peer form navigation takes place. END. END. topmost_tab_page). When-Tab-Page-Changed Fires whenever there is explicit item or mouse navigation from one tab page to another in a tab canvas. 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. This is an example of a procedure that can be called when Oracle Forms fires the When–Form– Navigate Trigger. 9. .MINIMIZE).

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

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.