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.

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

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

paramlist_name . The data type of the ID is PARAMLIST. 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.Shik Mahamood Ali 7 Exits the current form and enters the indicated form. updates. These locks can also occur when invoking Oracle Forms from an external 3GL program.) query_mode Takes one of the following constants as an argument: NO_QUERY_ONLY Runs the indicated form normally. The name must be enclosed in single quotes.paramlist_name ) formmodule_name Specifies the formmodule name of the called form. and deletes in the form. NEW_FORM (formmodule_name VARCHAR2. The locks are still in effect when you regain control from Oracle Forms. The calling form is terminated as the parent form. You can leave the top level form without performing a rollback. If the calling form had been called by a higher form. Oracle Forms keeps the higher call active and treats it as a call to the new form. rollback_mode. NO_ROLLBACK Oracle Forms exits the current form without rolling back to a savepoint. A parameter list passed to a form via NEW_FORM cannot contain parameters of type DATA_PARAMETER (a pointer to record group). The data type of the name is CHAR. You cannot specify a FULL_ROLLBACK from a form that is running in post–only mode. If the parent form was a called form.query_mode. Oracle Forms prevents any commit processing in the called form.data_mode. QUERY_ONLY Runs the indicated form as a query–only form. Oracle Forms releases memory (such as database cursors) that the terminated form was using. 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. To avoid losing the locks issued by the calling form. which means that you retain any locks across a NEW_FORM operation. Specify a parameter list when you want to pass parameters from the calling form to the new form. allowing the operator to perform inserts. FULL_ROLLBACK Oracle Forms rolls back all uncommitted changes (including posted changes) that were made during the current Runform session. (Post–only mode can occur when your form issues a call to another form while unposted records exist in the calling 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. switch_menu NUMBER. CALL_FORM. QUERY_ONLY Causes Oracle Forms to run the indicated form in Query Only mode. allowing the operator to query. DO_REPLACE Causes Oracle Forms to replace the default menu application of the calling form with the default menu application of the called form. The data type of the name is CHAR. query_mode NUMBER.Shik Mahamood Ali 8 The name you gave the parameter list object when you defined it. Oracle Forms runs the called form with the same Runform preferences as the parent form. display NUMBER. paramlist_name VARCHAR2). data_mode NUMBER. query_mode Takes one of the following constants as an argument: NO_QUERY_ONLY Causes Oracle Forms to run the indicated form in normal mode. NO_HIDE Causes Oracle Forms to display the called form without clearing the calling form from the screen. 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. HIDE is the default parameter. The data type of the name is CHAR. CALL_FORM (formmodule_name VARCHAR2. or delete records. update. The name must be enclosed in single quotes. 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. Parameters: formmodule_name Specifies the formmodule name of the called form. and deletes from within the called form. Runs an indicated form while keeping the parent form active. A parameter list passed to a form via NEW_FORM cannot contain parameters of type DATA_PARAMETER (a pointer to record group). updates. paramlist_id . but not to insert. allowing the operator to perform inserts.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

BEGIN SELECT ename INTO v_ename FROM emp WHERE empno = bind_value.MMB Menu Module Binary .MMT Menu Module Text . report. or graphic modules  Supports dynamic loading of program units FUNCTION locate_emp(bind_value IN NUMBER) RETURN VARCHAR2 IS v_ename VARCHAR2(15). 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.PLD .PLX PL/SQL Library Module Binary PL/SQL Library Module Text PL/SQL Library Module Executable . • 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.MMX Menu Module Executable Form Builder Built-in Package EXEC_SQL Provides built-ins for executing dynamic SQL within PL/SQL procedures . END.Shik Mahamood Ali 36 If you frequently use certain objects as standards. including procedures. Reasons to share objects and code:  Increased productivity  Increased modularity  Decreased maintenance  Maintaining standards . such as standard buttons. You can mark many different objects that are spread across multiple object libraries as SmartClasses. and packages. functions.PLL . and alerts. you can mark them as SmartClasses by selecting each object in the object library and choosing Object—>SmartClass. RETURN(v_ename). date items. A single library can contain many program units that can be shared among the Oracle Developer modules and applications that need to use them.menu.

Shik Mahamood Ali 37 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. The following settings are valid for this property: 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.

Shik Mahamood Ali 38 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  Interface event triggers o When-Button-Pressed o When-Checkbox-Changed o When-Image-Activated

Shik Mahamood Ali o o o o o o o o o o o o o When-Image-Pressed When-Radio-Changed When-Timer-Expired When –List-Changed When –List-Activated When –Tree-Note-Activated When –Tree-Note-Expanded When –Tree-Note-Selected 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

 Query-time triggers o o Pre-Query Post-Query

 Transactional triggers. o o o On-Count On-Delete. On-Insert.

Shik Mahamood Ali o On-Lock. o On-Logon. o On-Logout. o On-Select. o On-Update. o o o o o o o o o o o 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.

1. When-Create-Record
Fires when Form Builder creates a new record. For example, when the operator presses the [Insert] key, or navigates to the last record in a set while scrolling down, Form Builder fires this trigger.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

ROWID. BEGIN j := Recs_Returned('DEPT'. 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.ENAME. include a call to the built-in. IF form_fatal OR form_failure THEN raise form_trigger_failure. Example . Set_Block_Property('DEPT'. and sets the Query_Hits property appropriately. END IF. END.EMPNO.ename := emprow. Form Builder issues the standard query hits message: FRM-40355: Query will retrieve <n> records. . Usage Notes • Use an On-Count trigger to replace default Count Query processing in an application running against a non-ORACLE data source. END LOOP. 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.Name_In('DEPT. DECLARE j NUMBER.j). END. 16. :Emp. :Emp.empno := emprow. When the On-Count trigger completes execution. • If you are replacing default processing. • To perform the default Form Builder processing from this trigger. Example 2 /* ** Built-in: COUNT_QUERY ** Example: Display the number of records that will be retrieved ** by the current query.1 This example calls a user-named subprogram to count the number of records to be retrieved by the current query criteria. Count_Query.rowid := emprow.QUERY_HITS.Shik Mahamood Ali 72 :Emp. • 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.DNAME')). the message reports 0 records identified. */ BEGIN END. In such a case.

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

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. CLOSE chk_unique. Form Builder closes a query when all of the records identified by the query criteria have been fetched.'). tmp VARCHAR2(1). IF tmp IS NOT NULL THEN Message('This department already exists. 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. RAISE Form_Trigger_Failure. On-Check-Unique Trigger Description During a commit operation.Shik Mahamood Ali 74 IF :Global. FETCH chk_unique INTO tmp. */ ELSE Generate_Sequence_Number. 19. It fires once for each record that has been inserted or updated. 18. DECLARE CURSOR chk_unique IS SELECT 'x' FROM dept WHERE deptno = :dept. On-Check-Unique Trigger examples The following example verifies that the current record in question does not already exist in the DEPT table. Form Builder. call the CHECK_RECORD_UNIQUENESS built-in.deptno. . END IF. On-Close Trigger Description Fires when an operator or the application causes a query to close. END IF. do the right thing. Usage Notes To perform the default processing from this trigger. /* ** Otherwise. END. When a block has the PRIMKEYB property set to Yes. In the case of an update. END. or when the operator or the application aborts the query. Form Builder displays message FRM-40600: Record has already been inserted. If a duplicate row is found. By default.Using_Transactional_Triggers = ’TRUE’ THEN User_Exit(’my_seqnum seq=EMPNO_SEQ’). Form Builder always checks for unique primary key values. Replaces the default processing for checking record uniqueness. BEGIN OPEN chk_unique. by default. Form Builder checks for unique primary key values only if one or more items that have the Primary Key item property have been modified.

Only users with the user-defined SUPERUSER role can change these number fields. Example The following example releases memory being used by a user-defined data access method via the transactional triggers. Example The following example sets salary and commission text items in the current block to disabled and non-updateable. The On-Close trigger fires automatically when the ABORT_QUERY built-in is called from an On-Select trigger. BEGIN IF NOT my_data source_open('DX110_DEPT') THEN my_datasource_close('DX110_DEPT'). Form Builder makes the corresponding base table items in the form non-updateable by setting the Update Allowed item property Off dynamically. . Usage Notes To perform the default processing from this trigger. BEGIN IF NOT role_is_set('SUPERUSER') THEN on_or_off := PROPERTY_OFF. 20. itm_id := Find_Item('Emp. END IF. Set_Item_Property(itm_id. 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.Sal').on_or_off). call the ENFORCE_COLUMN_SECURITY built-in. close cursors. DECLARE itm_id Item.Shik Mahamood Ali 75 The On-Close trigger augments the normal Form Builder "close cursor" phase of a query. processing each block in sequence. Form Builder performs this operation at form startup. ELSE on_or_off := PROPERTY_ON. Usage Notes • • Use an On-Close trigger after using the On-Select or On-Fetch triggers. and free memory. unless the SUPERUSER role is enabled. specifically.ENABLED. on_or_off NUMBER. to close files. END. For columns to which the operator does not have update privileges. By default. END IF. Form Builder enforces column security by querying the database to determine the base table columns to which the current form operator has update privileges.

BEGIN /* Get the name of the savepoint to which Form Builder needs to ** rollback.Shik Mahamood Ali 76 Set_Item_Property(itm_id. On-Rollback Trigger Description Fires when Form Builder would normally issue a ROLLBACK statement. Pre-Logon Trigger Fires just before Form Builder initiate a logon procedure to the data source. ELSE Issue_Rollback(sp_name). /* ** Check the global flag we setup at form startup */ IF :Global.Using_Transactional_Triggers = 'TRUE' THEN User_Exit('my_rollbk name='||sp_name). 2. (NULL = Full Rollback)*/ sp_name := Get_Application_Property(SAVEPOINT_NAME). Usage Notes Use a Pre-Logon trigger to prepare the form for the logon procedure.on_or_off).Comm'). Usage Notes Use an On-Rollback trigger to replace standard Form Builder rollback processing. END.on_or_off). itm_id := Find_Item('Emp. to roll back a transaction to the last savepoint that was issued.UPDATEABLE. J.LOGON TRANSACTION TRIGGERS 1. . include a call to the ISSUE_ROLLBACK built-in. 21. Set_Item_Property(itm_id.UPDATEABLE.ENABLED. ISSUE_ROLLBACK examples /* ** Built-in: ISSUE_ROLLBACK ** Example: Perform Form Builder standard Rollback processing. ** perhaps based on a parameter. ** Decide whether to use this built-in based on a ** global flag setup at startup by the form. On-Logon Trigger Fires once per logon when Oracle Forms normally initiates the logon sequence.on_or_off). Set_Item_Property(itm_id. To perform default Form Builder processing from this trigger. END IF . ** Trigger: On-Rollback */ DECLARE sp_name VARCHAR2(80). particularly to a nonORACLE data source. END.

LOGON( un. cs:= GET_APPLICATION_PROPERTY( CONNECTION_STRING ). 3. if you want to create an application that does not require a data source.’DEFAULT’). cs VARCHAR2(30). .'YYYYMMDDHH24MISS')). POST-LOGON TRIGGER Description Fires after either of the following events: • • The successful completion of Form Builder default logon processing. END IF. END. FALSE ). BEGIN END. END IF. Example This example calls a user exit to log the current username and time to an encrypted audit trail file on the file system. DECLARE connected BOOLEAN:=FALSE. Tries:=tries-1. • • • Pre–Logon and Post–Logon triggers fire as part of the logon procedure. WHILE CONNECTED = FALSE AND tries > 0 LOOP LOGON_SCREEN. include a call to the LOGON built–in. which for security reasons is outside the database. RAISE FORM_TRIGGER_FAILURE. pw VARCHAR2(30). IF NOT CONNECTED THEN MESSAGE(‘Too many tries’). The successful execution of the On-Logon trigger. To perform the default Oracle Forms processing from this trigger. un:=GET_APPLICATION_PROPERTY( USERNAME ).Shik Mahamood Ali Usage Notes: 77 Use an On–Logon trigger to initiate a logon procedure to a non–ORACLE data source. You can supply a NULL command to this trigger to bypass the connection to a data source. IF FORM_SUCESS THEN Connected:=TRUE. User_Exit('LogCrypt '|| USER||' ' ||TO_CHAR(SYSDATE. pw || ‘@’ || CS . un NUMBER. pw:=GET_APPLICATION_PROPERTY( PASSWORD ). END LOOP. BEGIN SET_APPLICATION_PROPERTY(CURSOR_STYLE. tries NUMBER:=3.

Shik Mahamood Ali 78 4. To perform the default Form Builder processing from this trigger. 5. the results are undefined. For example. If you call certain built-ins from within one of the Logout triggers. . Because the form is no longer accessible. Pre-Logout Trigger Fires once before Form Builder initiate a logout procedure. you cannot call COPY from a Pre-Logout trigger because Pre-Logout fires after the Leave the Form event. Usage Notes • • • Use an On-Logout trigger to replace the default logout processing either from the RDBMS or from a non-ORACLE data source. If you call certain built-ins from within one of the Logout triggers. the results are undefined. Usage Notes • • Use a Post-Logout trigger to audit or to perform tasks on an Form Builder application that does not require or affect the RDBMS or other data source. On-Logout Trigger Fires when Form Builder normally initiates a logout procedure from Form Builder and from the RDBMS. a COPY operation is not possible. include a call to the LOGOUT built-in. 6. Because the form is no longer accessible at this point. For example. particularly a non-ORACLE data source. Because the form is no longer accessible. Usage Notes • • Use a Pre-Logout trigger to prepare the form for logging out from the data source. the COPY built-in cannot be called from a Pre-Logout trigger because Pre-Logout fires after the Leave the Form event. For example. the COPY operation is not possible. a COPY operation is not possible. If you call certain built-ins from within one of the Logout triggers. Post-Logout Trigger Description Fires after either of the following events: • • Form Builder successfully logs out of ORACLE. The successful execution of the On-Logout trigger. you cannot call the COPY built-in from a Pre-Logout trigger because Pre-Logout fires after the Leave the Form event. the results are undefined.

when the mouse is double-clicked within any canvas or item in the form if attached to a block. Usage Notes Use the When-Mouse-Click trigger to perform an action every time the operator clicks the mouse within an item and/or canvas. When-Mouse-Click Trigger Description Fires after the operator click the mouse if one of the following events occurs: • • • if attached to the form. when the mouse is clicked within any canvas or item in the form if attached to a block. J. when the mouse is clicked within any item in the block if attached to an item. END. When-Mouse-DoubleClick Trigger Description Fires after the operator double-clicks the mouse if one of the following events occurs: • • • if attached to the form. when the mouse is clicked within 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 79 This example calls a user exit to log the current username and time to an encrypted audit trail file on the file system. 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 .’YYYYMMDDHH24MISS’)). when the mouse is double-clicked within any item in the block if attached to an item. which for security reasons is outside the database. 2.MOUSE TRIGGERS 1. BEGIN User_Exit(’LogCrypt ’||USER||’ ’ || TO_CHAR(SYSDATE.

. Changing a tooltip's property in a When-Mouse-Enter trigger cancels the tooltip before it is ever shown. When-Mouse-DoubleClick Trigger examples Example Assume that an application requires Behavior A when the operator clicks the mouse and Behavior B when the operator double-clicks the mouse.Shik Mahamood Ali 80 Any trigger that is associated with these events will fire before the When-Mouse-DoubleClick trigger fires. if the operator clicks the mouse. when the mouse is pressed down within any canvas or item in the form if attached to a block. when the mouse enters any item in the block if attached to an item. the trigger fires and returns focus to the previous target. However. Do not use the When-Mouse-Enter trigger on a canvas that is larger than the window. 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. a product information window must appear. when the mouse is pressed down within any item in the block if attached to an item. when the mouse enters the item Usage Notes Use a When-Mouse-Enter trigger to perform an action every time the mouse enters an item or canvas. When-Mouse-Down Trigger Description Fires after the operator presses down the mouse button if one of the following events occurs: • • • if attached to the form. If the operator double-clicks the mouse. when the mouse enters any canvas or item in the form if attached to a block. an online help window must appear. as soon as the mouse enters that area. 4. Iconic buttons and items on the canvas below the initial window cannot be selected. so the user is never able to click on those items. Note: The mouse down event is always followed by a mouse up event. For example. 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. 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. 3.

When the operator dismisses the message box. For example.show_help_button := ’?’. when the mouse leaves any canvas or item in the form if attached to a block. Canvas_One and Canvas_Two.save_item_name). Assume also that your application contains two canvases. End. SHOW_VIEW(’cv_help’). when the operator moves the mouse out of Canvas_Two. HIDE_VIEW(’cv_help’). any When-Mouse-Leave triggers associated with this event will fire.CURSOR_ITEM. WHEN-MOUSE-LEAVE trigger on control. Canvas_One and Canvas_Two do not overlap each other. END IF. when the mouse leaves any item in the block if attached to an item. WHEN-MOUSE-ENTER at Form Level begin IF :SYSTEM. assume that the mouse has entered Canvas_One causing the When-Mouse-Enter trigger to fire which in turn causes Alert_One to appear. End. In addition.Shik Mahamood Ali 81 Be careful when calling a modal window from a When-Mouse-Enter trigger. begin :GLOBAL. GO_ITEM(’s_ord. When-Mouse-Move Trigger Description Fires each time the mouse moves if one of the following events occurs: .save_item_name := :SYSTEM. but appear side by side on the screen. Further.show_help_button begin End. Finally. assume that your When-Mouse-Enter trigger causes Alert_One to appear whenever the mouse enters Canvas_One.MOUSE_CANVAS = ’CV_ORDER’ THEN :control. assume that Alert_One displays within Canvas_Two's border. 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. 6. Doing so may cause the modal window to appear unnecessarily. GO_ITEM(:GLOBAL. 5.id’). Alert_One will appear again unnecessarily if the operator subsequently enters Canvas_One with the mouse. This may not be the desired behavior. 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.

7. . 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. as shown here: Execute_Trigger(’my_user_named_trigger’).OTHER TRIGGERS 1. When-Mouse-Up Trigger Description Fires each time the operator presses down and releases the mouse button if one of the following events occurs: • • • if a if if attached to the form. when 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 mouse up event is always associated with the item that received the mouse down event. when the mouse moves within any canvas or item in the form • if attached to a block. when the mouse moves within any item in the block • if attached to an item. when the mouse up event is received within any canvas or item in form attached to a block. For example. and then call explicitly from other triggers or user–named subprograms. K. 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. If the operator presses down the mouse on Item_One. The When-Mouse-Move trigger may have performance implications because of the number of times this trigger can potentially fire. rather than for Item_Two. assume that there is a When-Mouse-Up trigger attached to Item_One. To execute a user–named trigger. when the mouse up event is received within any item in a block attached to an item. User-Named Trigger A user–named trigger is a trigger that you define yourself in a form. you must call the EXECUTE_TRIGGER built–in procedure. but then releases the mouse on Item_Two.Shik Mahamood Ali 82 • if attached to the form. Note: You can write user–named PL/SQL subprograms to perform almost any task for which you might use a user–named trigger. Each user–named trigger defined at the same definition level must have a unique name.

If no such key trigger exists. On-Savepoint Trigger Fires when Form Builder would normally issue a Savepoint statement.perhaps based on a parameter. This behavior is analogous to pressing the corresponding function key. use the EXECUTE_TRIGGER built-in: EXECUTE_TRIGGER('KEY_F11').) In the menu PL/SQL. 2. In an On-Savepoint trigger. ** Trigger: On-Savepoint */ Do_Key('Execute_Query'). /* ** Built-in: ISSUE_SAVEPOINT ** Example: Perform Form Builder standard savepoint processing. DO_KEY built-in Executes the key trigger that corresponds to the specified built-in subprogram. Usage Notes To perform default Form Builder processing from this trigger. Form Builder issues savepoints at form startup. the trigger defined at the lowest level has precedence. When Savepoint Mode is Off. Create a user-named trigger to execute user-named subprograms defined in a form document from menu PL/SQL commands and user-named subprograms. DO_KEY restrictions DO_KEY accepts built-in names only. and at the start of each Post and Commit Transaction process. */ BEGIN END. call the EXECUTE_TRIGGER built-in to execute a usernamed trigger. which in turn calls the user-named subprogram defined in the current form. the On-Savepoint trigger never fires. the scope of a user-named trigger is the definition level and below. DO_KEY examples /* ** Built-in: DO_KEY ** Example: Simulate pressing the [Execute Query] key. By default. Form Builder does not issue savepoints and.Shik Mahamood Ali 83 As with all triggers. In an On-Rollback trigger . It is most practical to define user-named triggers at the form level. Syntax PROCEDURE DO_KEY (built-in_subprogram_name VARCHAR2).consequently. then the specified subprogram executes. . Suppress default savepoint processing by setting the Savepoint Mode form document property to Off. (User-named subprograms defined in a form cannot be called directly from menu PL/SQL. the Savepoint_Name application property returns the name of the next savepoint that Form Builder would issue by default. if no On-Savepoint trigger were present. not key names: DO_KEY(ENTER_QUERY). To accept a specific key name. Savepoint_Name returns the name of the savepoint to which Form Builder would roll back. ** Decide whether to use this built-in based on a global flag setup at startup by the form. include a call to the ISSUE_SAVEPOINT built-in. When more than one user-named trigger has the same name. which is defined in a different document.

and the item is not NULL. In this case.Shik Mahamood Ali 84 DECLARE sp_name VARCHAR2(80). do the right thing. In other words. An operator returns a value into an item by making a selection from a list of values. END. See "Usage Notes" below. not by way of Open Gateway. Usage Notes • • The Post-Change trigger is included only for compatibility with previous versions of Form Builder. /* Otherwise. For example. When the On–Lock trigger fires as a result of an operator trying to modify data. use On–Lock if you are accessing a non–ORACLE data source directly. for every row that is to be locked. • . END IF.Using_Transactional_Triggers = 'TRUE' THEN User_Exit('my_savept name='||sp_name). such as when an operator presses a key to modify data in an item. the trigger fires only the first time the operator tries to modify an item in the record. /* Check the global flag we setup at form startup */ IF :Global. If you want to circumvent this situation and effectively get rid of the Post-Change trigger. */ ELSE Issue_Savepoint(sp_name). BEGIN /* Get the name of the savepoint Form Builder needs to issue */ sp_name := Get_Application_Property(SAVEPOINT_NAME). you can use the On–Lock trigger to speed processing by bypassing all lock processing. if you are designing an application for use on a single–user system. The trigger fires between the key press and the display of the modified data. 3. you must include a Post-Query trigger in addition to your When-Validate-Item trigger. Form Builder marks the corresponding items and records as changed. Its use is not recommended in new applications. Usage Notes: • Use an On–Lock trigger to replace the default Oracle Forms processing for locking rows. The Post-Query trigger does not have the restrictions of the Post-Change trigger. 3. The trigger does not fire during subsequent modifications to items in the same record. the trigger fires once. Also. Given such changes. Post-Change Trigger 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. You can use Post-Query to make changes to the fetched database values. the When-ValidateItem trigger does not fire. Form Builder fetches a non-NULL value into an item. On-Lock Trigger Fires whenever Oracle Forms would normally attempt to lock a row.

Shik Mahamood Ali 85 • To perform the default Oracle Forms processing from this trigger. this occurs when a user presses the right mouse button. any of the items may be used. Pre-Popup-Menu Trigger This trigger is called when a user causes a pop-up menu to be displayed. . 7. This trigger is called when a query operation is necessary. Query-Procedure Trigger Automatically created by Form Builder when the query data source is a stored procedure. but the Query Data Source Columns property must be set so that those items can be passed to the query stored procedure. /* ** Built-in: LOCK_RECORD ** Example: Perform Form Builder standard record locking on the queried record which has just been deleted or updated. Think of this as an On-Update trigger that is called by the system instead of doing default update operations. the query stored procedure has to use those values to filter the data. END. Usage Notes When constructing a query. Then.) Actions defined for this trigger are performed before the pop-up menu is displayed. 5. • Use this trigger to lock underlying tables for non–updateable views. Think of this as an On-Query trigger that is called by the system instead of doing default query operations. Usage Notes Use this trigger to enable or disable menu items on a pop-up menu before it is displayed. This trigger is called when a update operation is necessary.perhaps based on a parameter. include a call to the LOCK_RECORD built–in. /* ** Otherwise. Lock_Record. Decide whether to use default processing or a user exit by consulting a global flag setup at startup by the form. ** Trigger: On-Lock */ BEGIN /* ** Check the global flag we set up at form startup */ IF :Global. Update-Procedure Trigger Automatically created by Form Builder when the update data source is a stored procedure. */ ELSE END IF. do the right thing.Non_Oracle_Datasource = 'TRUE' THEN User_Exit('my_lockrec block=EMP'). This means that the enter query mode does not happen automatically unless you specify it. (In a Microsoft Windows environment. 6.

Goto_Tab_Page(TabNumber). Usage Notes: Use a When–Custom–Item–Event trigger to respond to a selection or change of value for a VBX control.CUSTOM_ITEM_EVENT stores the case–sensitive name of the event that occurred.MINIMIZE). TabNumber Number. BEGIN TabEvent := :system. END IF. END. When-Tab-Page-Changed Fires whenever there is explicit item or mouse navigation from one tab page to another in a tab canvas. This is an example of a procedure that can be called when Oracle Forms fires the When–Form– Navigate Trigger. end if. . When-Custom-Item-Event Trigger 86 Fires whenever a VBX control sends an event to Oracle Forms.WINDOW_STATE. Usage Notes • Use a When-Tab-Page-Changed trigger to perform actions when any tab page is changed during item or mouse navigation.CUSTOM_ITEM_EVENT_PARAMETERS stores a parameter name that contains the supplementary arguments for an event that is fired by a VBX control.Shik Mahamood Ali 8. 10. 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.MAXIMIZE).WINDOW_STATE) = ’MAXIMIZE’ THEN SET_WINDOW_PROPERTY(win_id. END. The system variable SYSTEM. Example: This is an example of a procedure that can be called when Oracle Forms fires the When–Custom–Item–Event Trigger.’CurrTab’). When-Form-Navigate Trigger Fires whenever any peer form navigation takes place. BEGIN if (GET_WINDOW_PROPERTY(win_id. else SET_WINDOW_PROPERTY(win_id. DECLARE TabEvent varchar2(80).WINDOW_STATE.custom_item_event. */ IF (UPPER(TabEvent) = ’CLICK’) THEN TabNumber := VBX. and the system variable SYSTEM.Get_Property(’TABCONTROL’. and use the user–defined Goto_Tab_Page procedure to navigate to the selected page. /* ** After detecting a Click event. 9. identify the ** tab selected. DECLARE win_id WINDOW := FIND_WINDOW(’WINDOW12’).

When-Tree-Node-Selected Trigger Fires when a node is selected or deselected. Usage Notes • • SYSTEM. topmost_tab_page).TRIGGER_NODE is the node the user clicked on. Only end-user action will generate an event. Usage Notes • • SYSTEM. tp_id TAB_PAGE. No programmatic action will cause the When-Tree-Node-Activated trigger to fire. END IF.TRIGGER_NODE is the node the user clicked on. tp_lb VARCHAR2(30). ELSIF tp_lb LIKE 'Va%' THEN SET_TAB_PAGE_PROPERTY(tp_id. Example /* Use a When-Tab-Page-Changed trigger to dynamically change a tab page's label from lower. 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. the trigger will fire when the mouse or keyboard is used to navigate between tab pages. 'VACATION'). SYSTEM. When-Tree-Node-Expanded Trigger Fires when a node is expanded or collapsed. 13. it does not respond to implicit navigation. No programmatic action will cause the When-Tree-Node-Expanded trigger to fire. • When-Tab-Page-Changed does not fire when the tab page is changed programmatically.TRIGGER_NODE returns a value of type NODE. SYSTEM. Usage Notes • SYSTEM. tp_lb := GET_TAB_PAGE_PROPERTY(tp_id.TRIGGER_NODE returns a value of type NODE. label). .to uppercase (to indicate to end users if they already have ** navigated to the tab page): */ DECLARE tp_nm VARCHAR2(30). IF tp_lb LIKE 'Sa%' THEN SET_TAB_PAGE_PROPERTY(tp_id. BEGIN tp_nm := GET_CANVAS_PROPERTY('emp_cvs'. SYSTEM. but on different tab pages.TRIGGER_NODE is the node the user clicked on. END.TRIGGER_NODE returns a value of type NODE. Only end-user action will generate an event. When-Tree-Node-Activated Trigger Fires when an operator double-clicks a node or presses Enter when a node is selected. label. 12. 11. label. 'SALARY'). ELSE null. For example. tp_id := FIND_TAB_PAGE(tp_nm).Shik Mahamood Ali 87 • When-Tab-Page-Changed fires only when tab page navigation is explicit.

Shik Mahamood Ali 88 • No programmatic action will cause the When-Tree-Node-Selected trigger to fire. When the text list contains values that cannot be displayed (due to the displayable area of the item). . a vertical scroll bar appears. Defining list items A list item displays a predefined set of choices that  are mutually exclusive  can be displayed as either a poplist. Unlike the poplist or the text list style list items. allowing the operator to view and select undisplayed values. the combo box style list item will display fixed values and accept one operator-entered value. The combo box list item appears as an empty box with an icon to the right. or combo box LIST ITEM Poplist Text List DESCRIPTION Combo Box Appears initially as a single field (similar to a text item field). When the operator selects the list icon. Appears as a rectangular box which displays a fixed number of values. text list. Only enduser action will generate an event. Combines the features found in list and text items. The user can enter text directly into the combo field or click the list icon to display a list of available values. a list of available choices appears.

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.