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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

when the mouse is double-clicked within any item in the block if attached to an item. When-Mouse-DoubleClick Trigger examples Example . 2. 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-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 canvas or item in the form if attached to a block. when the mouse is double-clicked within any canvas or item in the form if attached to a block. when the mouse is double-clicked within the item Six events must occur before a When-Mouse-DoubleClick trigger will fire: • • • • • • Mouse Mouse Mouse Mouse Mouse Mouse down up click down up double-click Any trigger that is associated with these events will fire before the When-Mouse-DoubleClick trigger fires. 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 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.Shik Mahamood Ali Description 79 Fires after the operator click the mouse if one of the following events occurs: • • • if attached to the form. when the mouse is clicked within any item in the block if attached to an item.

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

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

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

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

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

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

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

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

Shik Mahamood Ali 88 .

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer: Get 4 months of Scribd and The New York Times for just $1.87 per week!

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