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.

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

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

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

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

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

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

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

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

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

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

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

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

Static record group . On-Populate-Details. The records in a query record group are the rows retrieved by the query associated with that record group. 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. Query record group A query record group is a record group that has an associated SELECT statement. but whose structure and values can be modified programmatically at runtime. Non-query record groups can be created and modified only at runtime. 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. To fetch the detail records. Query record groups can be created and modified at design time or at runtime. (Deferred False. For example. Oracle Forms does not automatically fetch the detail records.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. data types. Deferred Without Auto Query When coordination-causing event occurs. Non-query record group A non-query record group is a group that does not have an associated query. When a coordination-causing event occurs. and lengths from the database columns referenced in the SELECT statement. the detail records are fetched immediately. the operator must navigate to the detail data block and explicitly execute a query. Join Condition Use to: • • • • • Create links between blocks using SQL Alter links between blocks using SQL Define using: Usual SQL equi-join condition syntax Block names instead of the base table names Item names that exist in the form module instead of base table column names  Master-detail triggers On-Check-Delete-Master. Default [Immediate] The default setting. The columns in a query record group derive their default names. you can defer querying the line items for an order until the operator navigates to the item block. Auto-Query False) Deferred with Auto Query Oracle Forms defers fetching the associated detail records until the operator navigates to the detail data block.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When-Mouse-DoubleClick Trigger examples Example . 2. when the mouse is double-clicked within any canvas or item in the form if attached to a block. 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. when the mouse is 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. 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 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. when the mouse is double-clicked within the item Six events must occur before a When-Mouse-DoubleClick trigger will fire: • • • • • • Mouse Mouse Mouse Mouse Mouse Mouse down up click down up double-click Any trigger that is associated with these events will fire before the When-Mouse-DoubleClick trigger fires. when the mouse is double-clicked within any item in the block if attached to an item. Usage Notes Use the When-Mouse-Click trigger to perform an action every time the operator clicks the mouse within an item and/or canvas. when the mouse is clicked within any canvas or item in the form if attached to a block.

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

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

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

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

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

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

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

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

Shik Mahamood Ali 88 .

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.