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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Shik Mahamood Ali

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Shik Mahamood Ali 88 .

Sign up to vote on this title
UsefulNot useful