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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Shik Mahamood Ali 88 .

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

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

Cancel anytime.