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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

6.Shik Mahamood Ali 81 When the operator dismisses the message box.save_item_name). when the mouse moves within any canvas or item in the form if attached to a block. when the mouse moves within the item Usage Notes • Use the When-Mouse-Move trigger to perform an action every time the operator moves the mouse. WHEN-MOUSE-LEAVE trigger on control.show_help_button begin End.show_help_button := ’?’. HIDE_VIEW(’cv_help’). 5. When-Mouse-Move Trigger Description Fires each time the mouse moves if one of the following events occurs: • • • if attached to the form. . when the mouse leaves any item in the block if attached to an item. when the operator moves the mouse out of Canvas_Two. GO_ITEM(:GLOBAL. This may not be the desired behavior. SHOW_VIEW(’cv_help’). any When-Mouse-Leave triggers associated with this event will fire. when the mouse moves within any item in the block if attached to an item. END IF. End. GO_ITEM(’s_ord. In addition. WHEN-MOUSE-ENTER at Form Level begin IF :SYSTEM. End.save_item_name := :SYSTEM. The When-Mouse-Move trigger may have performance implications because of the number of times this trigger can potentially fire. Alert_One will appear again unnecessarily if the operator subsequently enters Canvas_One with the mouse.CURSOR_ITEM. 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. begin :GLOBAL.MOUSE_CANVAS = ’CV_ORDER’ THEN :control.id’). when the mouse leaves any canvas or item in the form if attached to a block. 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 up event is received within any item in a block attached to an item. User-Named Trigger A user–named trigger is a trigger that you define yourself in a form. 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. K. For example. the mouse up trigger will fire for Item_One. (User-named subprograms defined in a form cannot be called directly from menu PL/SQL. which in turn calls the user-named subprogram defined in the current form. When more than one user-named trigger has the same name. To execute a user–named trigger. DO_KEY built-in Executes the key trigger that corresponds to the specified built-in subprogram. If the operator presses down the mouse on Item_One. 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. but then releases the mouse on Item_Two. 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. 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. As with all triggers. which is defined in a different document. call the EXECUTE_TRIGGER built-in to execute a usernamed trigger. as shown here: Execute_Trigger(’my_user_named_trigger’).) In the menu PL/SQL. Each user–named trigger defined at the same definition level must have a unique name. It is most practical to define user-named triggers at the form level. you must call the EXECUTE_TRIGGER built–in procedure. The mouse up event is always associated with the item that received the mouse down event. rather than for Item_Two. the trigger defined at the lowest level has precedence. If no such key . Note: You can write user–named PL/SQL subprograms to perform almost any task for which you might use a user–named trigger.OTHER TRIGGERS 1. when the mouse up event is received within any canvas or item in form attached to a block.

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

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

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

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

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

Shik Mahamood Ali 88 .

Sign up to vote on this title
UsefulNot useful