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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Shik Mahamood Ali 88 .

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

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

Cancel anytime.