Shik Mahamood Ali Forms

1

Definition Forms used for presenting and manipulating data can be developed. It is GUI used for developing client server database application. .FMB .FMT .FMX Form Module Binary Form Module Text Form Module Executable

COMPONENTS OF FORMS 1.Form Builder It is used to create a form. The design and layout of data entry screens the creations of event driven PL/SQL code used for data validation and navigate can be done via form builder. 2.Form Compiler It is required to compile the file created in form builder and create a binary file, which can be executable form runtime. 3.Form Runtime It is used to run the complied code created by forms compiler. COMPONENTS OF FORM BUILDER 1. Object Navigator It is hierarchical browsing and editing interface that enables you locate and manipulate application objects quickly and easily. 2.Property Palette It is used set and modify the properties for all objects in form modules. 3.Layout Editor It is graphical design facility for creating and arranging interface items and graphical objects in your application. 4.PL / SQL Editor It is the integrated functionality of oracle procedure builder that exists with in form builder. It provides: Development of Trigger, Procedures, Functions and Packages Development of libraries to hold PL/SQL program unit. FORM MODULE TYPES 1.Form Module It is a collection of objectives such as block, canvas, items and event based PL/SQL code blocks called trigger . 2.Menu Module It is a collection of menu items. It can be main menu or sub menu. 3.PL / SQL Libraries The library module is a collection of PL/SQL function and package stored ion a single library file. This library file is the attached to form / menu modules. All other objects in the form or menu can now access share the collection of PL/SQL functions and procedures. 4.Object Libraries

Shik Mahamood Ali 2 It is a collection of form objects that you can use in other modules. You can create it to store, maintain and distribute standard objects that can be reuse across the entire development organization. 5. Object Group (Form Builder) An object group is a container for a group of objects. You define an object group when you want to package related objects so you can copy or subclass them in another module. OBJECTS OF FORMS 1.Blocks Block is logical owner of items. It provides a mechanism for grouping related items into a functional unit for storing, displaying and manipulating records. 2.Items These are interface objects that present data values to the user or enable the user to interact with the form. 3. Canvas A canvas is the background object upon which interface items appear. 4. Frames Frames are used to arrange items with in a block. 5. Windows Windows contains for all visual objects that make up a form builder application. 6. PL/SQL Code Block It is used for event driven code. That code automatically executes when a specific event occurs. Form Built - ins 1.CLEAR_FORM Causes Form Builder to remove all records from, or flush, the current form, and puts the input focus in the first item of the first block. 2.COMMIT_FORM Causes Form Builder to update data in the database to match data in the form. Form Builder first validates the form, then, for each block in the form, deletes, inserts, and updates to the database, and performs a database commit. As a result of the database commit, the database releases all row and table locks. 3.DEBUG_MODE Toggles debug mode on and off in a menu. When debug mode is on in a menu, Form Builder issues an appropriate message when a menu item command executes. 4. ENTER Validates data in the current validation unit. (The default validation unit is Item.)

5.ERASE Removes an indicated global variable, so that it no longer exists, and releases the memory associated with the global variable. Global always allocate 255 bytes of storage. To ensure

Shik Mahamood Ali 3 that performance is not impacted more than necessary, always erase any global variable when it is no longer needs 6. EXECUTE_TRIGGER EXECUTE_TRIGGER executes an indicated trigger. 7. EXIT_FORM Provides a means to exit a form, confirming commits and specifying rollback action. 8.FIND_FORM Searches the list of forms and returns a form module ID when it finds a valid form with the given name. You must define an appropriately typed variable to accept the return value. Define the variable with a type of Form module. 9. FORM_FAILURE Returns a value that indicates the outcome of the action most recently performed during the current Runform session. Use FORM_FAILURE to test the outcome of a built–in to determine further processing within any trigger. To get the correct results, you must perform the test immediately after the action executes. That is, another action should not occur prior to the test. Example: /* ** Built–in: FORM_FAILURE ** Example: Determine if the most recently executed built–in ** failed. */ BEGIN GO_BLOCK(’Success_Factor’); /* ** If some validation failed and prevented us from leaving ** the current block, then stop executing this trigger. ** ** Generally it is recommended to test ** IF NOT Form_Success THEN ... ** Rather than explicitly testing for FORM_FAILURE */ IF Form_Failure THEN RAISE Form_Trigger_Failure; END IF; END; FORM_FATAL Returns the outcome of the action most recently performed during the current Runform session.

Use FORM_FATAL to test the outcome of a built–in to determine further processing within any trigger. To get the correct results, you must perform the test immediately after the action executes. That is, another action should not occur prior to the test. Example: /* ** Built–in: FORM_FATAL

Shik Mahamood Ali 4 ** Example: Check whether the most–recently executed built–in had a fatal error.*/ BEGIN User_Exit(’Calculate_Line_Integral control.start control.stop’); /* ** If the user exit code returned a fatal error, print a ** message and stop executing this trigger. ** ** Generally it is recommended to test ** ** IF NOT FORM_SUCCESS THEN ... ** ** Rather than explicitly testing for FORM_FATAL IF Form_Fatal THEN Message(’Cannot calculate the Line Integral due to internal error.’); RAISE Form_Trigger_Failure; END IF;

END;

FORM_SUCCESS Returns the outcome of the action most recently performed during the current Runform session. Use FORM_SUCCESS to test the outcome of a built–in to determine further processing within any trigger. To get the correct results, you must perform the test immediately after the action executes. That is, another action should not occur prior to the test. Note: FORM_SUCCESS should not be used to test whether a COMMIT_FORM or POST built–in has succeeded. Because COMMIT_FORM may cause many other triggers to fire, when you evaluate FORM_SUCCESS it may not reflect the status of COMMIT_FORM but of some other, more recently executed built–in. A more accurate technique is to check that the SYSTEM.FORM_STATUS variable is set to ’QUERY’ after the operation is done. Example: /* ** Built–in: FORM_SUCCESS ** Example: Check whether the most–recently executed built–in ** succeeded. BEGIN /* ** Force validation to occur*/ Enter; /* ** If the validation succeeded, then Commit the data. ** */ IF Form_Success THEN Commit; IF :System.Form_Status <> ’QUERY’ THEN Message(’Error prevented Commit’); RAISE Form_Trigger_Failure; END IF; END IF; END; FORMS_DDL FORMS_DDL( statement); Issues dynamic SQL statements at runtime, including server–side PL/SQL and DDL.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Shik Mahamood Ali 88 .

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

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

Cancel anytime.