Shik Mahamood Ali Forms

1

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

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

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

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

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

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

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

END;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Returns a BOOLEAN value that indicates whether the object ID is available. ID_NULL (Alert BOOLEAN). al_button := Show_Alert( al_id ). FIND_ALERT (alert_name VARCHAR2). Displays the given alert. You define an object group when you want to package related objects so you can copy or subclass them in another module.property VARCHAR2. Each style denotes a different level of message severity. ** Built-in: SET_ALERT_PROPERTY ** Example: Places the error message into a user-defined alert ** named 'My_Error_Alert' and displays the alert. BEGIN al_id := Find_Alert('My_Error_Alert').button NUMBER. You define an object group when you want to package related objects for copying or sub classing in another module. OBJECT GROUPS An object group is a container for a group of objects. Changes the label on one of the buttons in an alert. Changes the message text for an existing alert. ** Trigger: On-Error */ DECLARE err_txt VARCHAR2(80) := Error_Text. Searches the list of valid alerts in Form Builder. message SHOW_ALERT (alert_id Alert). and returns a numeric value when the operator selects one of three alert buttons. Using Object Groups • Blocks include: Items Item-level triggers Block-level triggers Relations • Object groups cannot include other object groups . err_txt ). SET_ALERT_BUTTON_PROPERTY(alert_id ALERT. alert_message_text. SET_ALERT_PROPERTY (alert_id ALERT. the subprogram returns an alert ID.Shik Mahamood Ali 34 There are three styles of alerts: Stop. Define the variable with a type of Alert. Message severity is represented visually by a unique icon that displays in the alert window. al_id Alert. You can use object groups to bundle numerous objects into higher-level building blocks that you can use again in another application. al_button Number. When the given alert is located. Caution. 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. VARCHAR2). property NUMBER. END. value VARCHAR2). and Note. You must return the ID to an appropriately typed variable. 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 distribute standard and reusable objects. They simplify reuse in complex environments. store. You can use the Object Library to create. • Changes made to a copied object in the source module do not affect the copied object in the target module. and personal standards. Any objects owned by the copied object are also copied. such as buttons and items. by using Object Libraries. Reusing components enables you to: • Apply standards to simple objects. project. Object libraries simplify the sharing of reusable components. project. In addition. Use copying to export the definition of an object to another module. An object library can contain simple objects. unique version of that object in the target module. Objects can be used as standards (classes) for other objects. and personal standards Simplifies the sharing of reusable components Object libraries are convenient containers of objects for reuse. 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 . maintain. you can rapidly create applications by dragging and dropping predefined objects to your form. property classes. object groups.Shik Mahamood Ali 35 • Deleting: An object group does not affect the objects An object affects the object group Copying an Object Copying an object creates a separate. and program units. but they are protected against change in the library. • • • • Is a convenient container of objects for reuse Simplifies reuse in complex environments Supports corporate. and they support corporate.

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

Shik Mahamood Ali

37

EXEC_SQL Provides built-ins for executing dynamic SQL within PL/SQL procedures

VBX Provides built-ins for controlling and interacting with VBX controls; this package works only in a 16-bit environment and is provided for backward compatibility WEB Provides built-ins for the Web environment OLE2 Provides a PL/SQL API for creating, manipulating, and accessing attributes of OLE2 automation objects SUBPROGRAM A subprogram can be either a procedure or a function. Built-in subprograms are therefore called in two distinct ways: • Built-in procedures: Called as a complete statement in a trigger or program unit with mandatory arguments. • Built-in functions: Called as part of a statement, in a trigger or program unit, at a position where the function’s return value will be used. Again, the function call must include any mandatory arguments. TRIGGER Triggers are blocks of PL/SQL code that are written to perform tasks when a specific event occurs within an application. In effect, a Form Builder trigger is an event-handler written in PL/SQL to augment (or occasionally replace) the default processing behavior. Every trigger has a name, and contains one or more PL/SQL statements. A trigger encapsulates PL/SQL code so that it can be associated with an event and executed and maintained as a distinct object.

Trigger Scope

1.Form Level The trigger belongs to the form and can fire due to events across the entire form. 2.Block Level The trigger belongs to a block and can only fire when this block is the current block. 3.Item Level The trigger belongs to an individual item and can only fore when this item is the current item. Trigger Properties
Execution Style

Execution Hierarchy property Specifies how the current trigger code should execute if there is a trigger with the same name defined at a higher level in the object hierarchy.

Shik Mahamood Ali The following settings are valid for this property:

38

Override Specifies that the current trigger fire instead of any trigger by the same name at any higher scope. This is known as "override parent" behavior. Before Specifies that the current trigger fire before firing the same trigger at the next-higher scope. This is known as "fire before parent" behavior. After Specifies that the current trigger fire after firing the same trigger at the next-higher scope. This is known as "fire after parent" behavior.

What are triggers used for?
           Validate data entry Protect the database from operator errors Limit operator access to specified forms Display related field data by performing table lookups Compare values between fields in the form Calculate field values and display the results of those calculations Perform complex transactions, such as verifying totals Display customized error and information messages to the operator Alter default navigation Display alert boxes Create, initialize, and increment timers

Groups of triggers
GROUP FUNCTION

When-triggers On-triggers Pre- and Post-triggers Key-trigger

Execute in addition to default processing Replace default processing Add processing before or after an event Change default processing assigned to a specific key

Trigger Categories  Block-processing triggers o When-Create-Record o When-Clear-Block o When-Database-Record o When-Remove-Record

Shik Mahamood Ali  Interface event triggers o When-Button-Pressed o When-Checkbox-Changed o When-Image-Activated o When-Image-Pressed o When-Radio-Changed o When-Timer-Expired o When –List-Changed o When –List-Activated o When –Tree-Note-Activated o When –Tree-Note-Expanded o When –Tree-Note-Selected o o o o o Key- [all] When-Window-Activated When-Window-Closed When-Window-Deactivated When-Window-Resized

39

 Master-detail triggers o On-Check-Delete-Master o On-Clear-Details o On-Populate-Details  Message-handling triggers o On-Error o On-Message  Navigational triggers o Pre- and Post- Triggers         o Pre-Form Pre-Block Pre-Record Pre-Text-Item Post-Text-Item Post-Record Post-Block Post-Form

When-New-Instance-Triggers     When-New-Form-Instance When-New-Block-Instance When-New-Record-Instance When-New-Item-Instance

 o o Pre-Query Post-Query

Query-time triggers

Shik Mahamood Ali  Transactional triggers. o o o o o o o o o o o o o o o o o o o On-Count On-Delete. On-Insert. On-Lock. On-Logon. On-Logout. On-Select. On-Update. Post-Database-Commit. Post-Delete. Post-Forms-Commit. Post-Insert. Post – Select. Post-Update. Pre-Commit. Pre-Delete. Pre-Insert. Pre-Select. Pre-Update.

40

 Validation triggers o o When-Validate-Item When-Validate-Record

 Mouse Event Triggers o o o o o o o o When-Custom-Item-Event When-Mouse-Click When-Mouse-Double Click When-Mouse-Down When-Mouse-Enter When-Mouse-Leave When-Mouse-Move When-Mouse-Up

 Key-Fn Trigger o A Key-Fn trigger fires when an operator presses the associated key. o Use Key-Fn triggers to create additional function keys for custom functions.  Calling user-named triggers

TRIGGER CATEGORIES
 A. BLOCK-PROCESSING TRIGGERS Block processing triggers fire in response to events related to record management in a block.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Shik Mahamood Ali 88 .

Sign up to vote on this title
UsefulNot useful