Shik Mahamood Ali Forms

1

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

COMPONENTS OF FORMS 1.Form Builder It is used to create a form. The design and layout of data entry screens the creations of event driven PL/SQL code used for data validation and navigate can be done via form builder.

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

Shik Mahamood Ali 2 It is a collection of form objects that you can use in other modules. You can create it to store, maintain and distribute standard objects that can be reuse across the entire development organization. 5. Object Group (Form Builder) An object group is a container for a group of objects. You define an object group when you want to package related objects so you can copy or subclass them in another module.

OBJECTS OF FORMS 1.Blocks Block is logical owner of items. It provides a mechanism for grouping related items into a functional unit for storing, displaying and manipulating records. 2.Items These are interface objects that present data values to the user or enable the user to interact with the form. 3. Canvas A canvas is the background object upon which interface items appear. 4. Frames Frames are used to arrange items with in a block. 5. Windows Windows contains for all visual objects that make up a form builder application. 6. PL/SQL Code Block It is used for event driven code. That code automatically executes when a specific event occurs. Form Built - ins 1.CLEAR_FORM Causes Form Builder to remove all records from, or flush, the current form, and puts the input focus in the first item of the first block. 2.COMMIT_FORM Causes Form Builder to update data in the database to match data in the form. Form Builder first validates the form, then, for each block in the form, deletes, inserts, and updates to the database, and performs a database commit. As a result of the database commit, the database releases all row and table locks. 3.DEBUG_MODE Toggles debug mode on and off in a menu. When debug mode is on in a menu, Form Builder issues an appropriate message when a menu item command executes. 4. ENTER Validates data in the current validation unit. (The default validation unit is Item.)

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

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

FORM_FATAL Returns the outcome of the action most recently performed during the current Runform session.

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

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

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

FORMS_DDL FORMS_DDL( statement); Issues dynamic SQL statements at runtime, including server–side PL/SQL and DDL.

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

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

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

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

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

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

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

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

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

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

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

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

Auto-Query False) Deferred with Auto Query Oracle Forms defers fetching the associated detail records until the operator navigates to the detail data block. Query record group A query record group is a record group that has an associated SELECT statement. and lengths from the database columns referenced in the SELECT statement.Shik Mahamood Ali Coordination 17 You can control how the detail records are displayed when a master block is queried by setting the coordination property. When a coordination-causing event occurs. Non-query record groups can be created and modified only at runtime. The records in a query record group are the rows retrieved by the query associated with that record group. 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. Default [Immediate] The default setting. The columns in a query record group derive their default names. For example. Join Condition Use to: • • • • • Create links between blocks using SQL Alter links between blocks using SQL Define using: Usual SQL equi-join condition syntax Block names instead of the base table names Item names that exist in the form module instead of base table column names Ø Master-detail triggers On-Check-Delete-Master. the operator must navigate to the detail data block and explicitly execute a query. (Deferred False. Query record groups can be created and modified at design time or at runtime. you can defer querying the line items for an order until the operator navigates to the item block. Deferred Without Auto Query When coordination-causing event occurs. On-Populate-Details. Oracle Forms does not automatically fetch the detail records. but whose structure and values can be modified programmatically at runtime. the detail records are fetched immediately. data types. 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. To fetch the detail records. Static record group . Non-query record group A non-query record group is a group that does not have an associated query.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

by using Object Libraries. object groups. it can be used to subclass existing objects in a form using the SmartClass option from the right mouse button popup menu. but they are protected against change in the library. An object library can contain simple objects. You can use the Object Library to create. and program units. They simplify reuse in complex environments. Objects can be used as standards (classes) for other objects. Reusing components enables you to: • Apply standards to simple objects. and personal standards. property classes. unique version of that object in the target module. • Changes made to a copied object in the source module do not affect the copied object in the target module. Object libraries simplify the sharing of reusable components. and distribute standard and reusable objects. and they support corporate. Object Library members which are not SmartClasses can only be used to create new objects in form modules into which they are added. Use copying to export the definition of an object to another module. maintain. In addition. for a consistent look and feel • Reuse complex objects such as a Navigator Benefits of the Object Library • Simplifies the sharing and reuse of objects • Provides control and enforcement of standards • Eliminates the need to maintain multiple referenced forms SMARTCLASS A SmartClass is a special member of an Object Library. • • • • Is a convenient container of objects for reuse Simplifies reuse in complex environments Supports corporate. such as buttons and items. Unlike other Object Library members.Shik Mahamood Ali 35 Copying an object creates a separate. Subclassing Subclassing is an object-oriented term that refers to the following capabilities: • Inheriting the characteristics of a base class (Inheritance) • Overriding properties of the base class (Specialization) OBJECT LIBRARY This object provides an easy method of reusing objects and enforcing standards across the entire development organization. and personal standards Simplifies the sharing of reusable components Object libraries are convenient containers of objects for reuse. project. you can rapidly create applications by dragging and dropping predefined objects to your form. store. . project. Any objects owned by the copied object are also copied.

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

Shik Mahamood Ali 37 VBX Provides built-ins for controlling and interacting with VBX controls; this package works only in a 16-bit environment and is provided for backward compatibility WEB Provides built-ins for the Web environment OLE2 Provides a PL/SQL API for creating, manipulating, and accessing attributes of OLE2 automation objects

SUBPROGRAM A subprogram can be either a procedure or a function. Built-in subprograms are therefore called in two distinct ways: • Built-in procedures: Called as a complete statement in a trigger or program unit with mandatory arguments. • Built-in functions: Called as part of a statement, in a trigger or program unit, at a position where the function’s return value will be used. Again, the function call must include any mandatory arguments. TRIGGER Triggers are blocks of PL/SQL code that are written to perform tasks when a specific event occurs within an application. In effect, a Form Builder trigger is an event-handler written in PL/SQL to augment (or occasionally replace) the default processing behavior. Every trigger has a name, and contains one or more PL/SQL statements. A trigger encapsulates PL/SQL code so that it can be associated with an event and executed and maintained as a distinct object.

Trigger Scope

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

Trigger Properties
Execution Style

Execution Hierarchy property Specifies how the current trigger code should execute if there is a trigger with the same name defined at a higher level in the object hierarchy. The following settings are valid for this property: Override Specifies that the current trigger fire instead of any trigger by the same name at any higher scope. This is known as "override parent" behavior.

Shik Mahamood Ali 38 Before Specifies that the current trigger fire before firing the same trigger at the next-higher scope. This is known as "fire before parent" behavior. After Specifies that the current trigger fire after firing the same trigger at the next-higher scope. This is known as "fire after parent" behavior.

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

Groups of triggers
GROUP FUNCTION

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

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

Trigger Categories ü Block-processing triggers o When-Create-Record o When-Clear-Block o When-Database-Record o When-Remove-Record ü Interface event triggers o When-Button-Pressed o When-Checkbox-Changed o When-Image-Activated o When-Image-Pressed o When-Radio-Changed

Shik Mahamood Ali o o o o o o o o o o o ü When-Timer-Expired When –List-Changed When –List-Activated When –Tree-Note-Activated When –Tree-Note-Expanded When –Tree-Note-Selected Key- [all] When-Window-Activated When-Window-Closed When-Window-Deactivated When-Window-Resized

39

Master-detail triggers o On-Check-Delete-Master o On-Clear-Details o On-Populate-Details

ü Message-handling triggers o On-Error o On-Message ü Navigational triggers o Pre- and Post- Triggers § § § § § § § § o Pre-Form Pre-Block Pre-Record Pre-Text-Item Post-Text-Item Post-Record Post-Block Post-Form

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

ü

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

ü Transactional triggers. o o o o o o o o On-Count On-Delete. On-Insert. On-Lock. On-Logon. On-Logout. On-Select. On-Update.

Shik Mahamood Ali o Post-Database-Commit. o Post-Delete. o Post-Forms-Commit. o Post-Insert. o Post – Select. o Post-Update. o o o o o Pre-Commit. Pre-Delete. Pre-Insert. Pre-Select. Pre-Update.

40

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

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

ü

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

ü Calling user-named triggers

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

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

Used For
• Perform an action whenever Form Builder attempts to create a new record in a block. For example, to set complex, calculated, or data-driven default values that must be specified at runtime, rather than design time.

Fires In
• CREATE_RECORD

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

to calculate text item values. or using the keyboard.. or form level functionality.INTERFACE EVENT TRIGGERS Interface event triggers fire in response to events that occur in the form interface. END IF.Shik Mahamood Ali Fires In • • CLEAR_RECORD DELETE_RECORD 42 B. */ IF :System. either by clicking with the mouse. /* If the Form_Status is not back to 'QUERY' ** following a commit. can fire in response to both operator input and programmatic control. So for all navigation triggers that fire before the When-Checkbox-Changed trigger. such as When-Button-Pressed. Thus.'). 2. like When-Window-Activated. . then the commit was not successful. This example executes a COMMIT_FORM if there are changes in the form. Some of these trigger.If the check box is set off.order_filled item prevents the date_shipped item from being updated if the user marks the order as filled ( checked on ). or using the keyboard. Usage Notes • Use a When-Button-Pressed trigger to perform navigation. END. When-Checkbox-Changed Fires when an operator changes the state of a check box. fire only in response to operator input or manipulation. block. either with the mouse or through keyboard selection Usage Notes • • Use a When-Checkbox-Changed trigger to initiate a task dependent upon the state of a check box. the When-Checkbox-Changed trigger is the first trigger to register the changed value of a check box item. or for other item.Form_Status <> 'QUERY' THEN Message('Unable to commit order to database. 1. the internal value of that item does not change until navigation is completed successfully. Initiate an action when the operator toggles the state of a check box. then the Date_Shipped item is enabled. by clicking with a mouse. When-Button-Pressed Fires when an operator selects a button.Form_Status = 'CHANGED' THEN Commit_Form.. When-Checkbox-Changed Trigger examples This trigger on the :S_ord. END IF. RAISE Form_Trigger_Failure. BEGIN IF :System. 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. Others.

When-List-Changed Trigger Description . 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. The display style of a list item is determined by the List Style property. 5. Begin READ_IMAGE_FILE(‘ST_’||TO_CHAR(:STMAST. 6. 3. End. When-Image-Activated Initiate an action whenever the operator double-clicks an image item. When-Image-Pressed Initiate an action whenever an operator clicks on an image item. End if. Else Set_Item_Property(‘s_ord.date_shipped’. 4. Fires when an operator uses the mouse to: • Single-click on an image item • Double-click on an image item Note : That When-Image-Activated also fires on a double-click. When-List-Activated Trigger Fires when an operator double-clicks on an element in a list item that is displayed as a T-list.’STMAST:STIMAGE’).’JPG’.filled’) then Set_Item_Property(‘s_ord.date_shipped’. Fires when an operator uses the mouse to: • Single-click on an image item.STID)||’.Update_allowed’.property_true).property_false). 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. Double-click on an image item. End.Shik Mahamood Ali 43 Begin If checkbox_checked(‘s_ord.JPG’. § Note : That When-Image-Pressed also fires on a double-click.Update_allowed’. Usage Notes • Use a When-Image-Pressed trigger to perform an action when an operator clicks or double clicks on an image item.

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

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

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

11. Maintain certain visual standards by resetting window size if the window was improperly resized. such as width. w NUMBER. 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. .) This trigger also fires at form startup. h NUMBER. Fires when a window is resized. 12. Audit the actions of an operator. VISIBLE. SET_WINDOW_PROPERTY. when the root window is first drawn. When-Window-Deactivated Initiate an action whenever a window is deactivated as a result of another window becoming the active window. Window2 VARCHAR2) IS wn_id1 Window. (Even if the window is not currently displayed.Shik Mahamood Ali 47 10 . Example: /* ** Built–in: RESIZE_WINDOW ** Example: Set Window2 to be the same size as Window1 */ PROCEDURE Make_Same_Size_Win( Window1 VARCHAR2. When-Window-Resized Initiate an action whenever a window is resized. resizing the window programmatically fires the When–Window–Resized trigger. Set input focus in an item on the target window. either by the operator or programmatically. Fires when an operator deactivates a window by setting the input focus to another window. and EXIT_FORM built–in subprograms. either by the operator or programmatically through a call to RESIZE_WINDOW or SET_WINDOW_PROPERTY. • You can close a window with the HIDE_WINDOW . It does not fire when a window is iconified. 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’. height. PROPERTY_OFF). or y coordinate. • You can hide the window that contains the current item. Usage Notes: • Use this trigger to programmatically close a window when the operator issues the window–manager Close command.When-Window-Closed Initiate an action whenever an operator closes a window with the window manager's Close command. x coordinate. Usage Notes: Use this trigger to perform any one of the following types of tasks: • • • • Capture the changed window properties.

h := Get_Window_Property(wn_id1. you can define a Key-EXIT trigger to replace the default functionality of the [Help] key. */ wn_id1 := Find_Window(Window1). Replace the default function associated with a function key. /* ** Resize Window2 to the same size */ Resize_Window( Window2.WIDTH). Usage Notes: Use Key–Fn triggers to create additional function keys for custom functions. C. you or the DBA must use Oracle Terminal to map the keys to the appropriate functions. Before you can attach key triggers to these keys.[ALL] ( KEY TRIGGERS ) Key Triggers have a one-to-one relationship with specific keys. These keys are referred to as Key–F0 through Key–F9. h ). You can attach Key–Fn triggers to 10 keys or key sequences that normally do not perform any Oracle Forms operations. . w := Get_Window_Property(wn_id1. Lock command on the default menu 1. i. the trigger fires when operator presses a specific key or key-sequence. KEY.Shik Mahamood Ali BEGIN 48 /* ** Find Window1 and get it’s width and height. END. w.HEIGHT).e. Key Triggers and Function Keys KEY TRIGGER Key–CLRBLK Key–CLRFRM Key–CLRREC Key–COMMIT Key–CQUERY Key–CREREC Key–DELREC Key–DOWN Key–DUP–ITEM Key–DUPREC Key–EDIT Key–ENTQRY Key–EXEQRY Key–EXIT Key–HELP Key–LISTVAL Key–MENU Key–NXTBLK Key–NXT–ITEM Key–NXTKEY Key–NXTREC Key–NXTSET Key–PRINT Key–PRVBLK Key–PRV–ITEM Key–PRVREC Key–SCRDOWN Key–SCRUP Key–UP Key–UPDREC ASSOCIATED FUNCTION KEY [Clear Block] [Clear Form] [Clear Record] [Accept] [Count Query Hits] [Insert Record] [Delete Record] [Down] [Duplicate Item] [Duplicate Record] [Edit] [Enter Query] [Execute Query] [Exit] [Help] [List of Values] [Block Menu] [Next Block] [Next Item] [Next Primary Key] [Next Record] [Next Set of Records] [Print] [Previous Block] [Previous Item] [Previous Record] [Scroll Down] [Scroll Up] [Up] Equivalent to Record. For example.Key–Fn Trigger A Key–Fn trigger fires when an operator presses the associated key.

however. RAISE Form_Trigger_Failure. END IF. D. Key–Others Trigger A Key–Others trigger fires when an operator presses the associated key. When this occurs. KEY-EXIT AT FORM LEVEL SET_ALERT_PROPERTY (’question_alert’. END. A Key–Others trigger is associated with all keys that can have key triggers associated with them but are not currently defined by function key triggers (at any level). 2. IF SHOW_ALERT (’question_alert’) = ALERT_BUTTON1 THEN EXIT_FORM. On-Clear-Details . END. IF the_sum <> :purchase_order. ’Do you really want to leave the form?’).MASTER-DETAIL TRIGGERS Form Builder generates master/detail triggers automatically when a master/detail relation is defined between blocks. On-Check-Delete-Master Fires when Form Builder attempts to delete a record in a block that is a master block in a master/detail relation. ALERT_MESSAGE_TEXT.number. END IF. Specifically. • Perform one specific action whenever an operator presses any key. 1. DECLARE the_sum NUMBER. A Key–Others trigger overrides the default behavior of a Runform function key (unless one of the following restrictions apply). Usage Notes: Use Key–Others triggers to limit an operator’s possible actions. KEY-DELREC TRIGGER ON S_CUSTOMER BLOCK DELETE_RECORD. END IF.’). BEGIN SELECT SUM(dollar_amt) INTO the_sum FROM po_distribution WHERE po_number = :purchase_order. Oracle Forms still displays the function key’s default entry in the Show Keys screen. KEY-COMMIT TRIGGER AT FORM LEVEL: EMPLOYEES FORM BEGIN IF GET_APPLICATION_PROPERTY( CALLING_FORM ) IS NULL THEN COMMIT_FORM. The default master/detail triggers enforce coordination between records in a detail block and the master record in a master block. ELSE POST. use Key–Others triggers to perform the following tasks: • Disable all keys that are not relevant in a particular situation.total THEN Message(’PO Distributions do not reconcile.Shik Mahamood Ali 49 2.

you can call the SET_BLOCK_PROPERTY(COORDINATION_STATUS) built–in. 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. 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.Shik Mahamood Ali 50 Fires when Form Builder needs to clear records in a block that is a detail block in a master/detail relation because those records no longer correspond to the current record in the master block. 1. Message handling triggers fire in response to these default messaging events. 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. • When Deferred coordination is set and this trigger fires. such as during a Commit process. Trapping certain errors at the block or item level can be difficult if these errors occur while Oracle Forms is performing internal navigation. ERROR_TEXT. E. this causes the details of the instantiated master to be populated immediately. 3. BEGIN IF (lv_errcod = 40nnn) THEN /* ** Perform some tasks here */ ELSIF (lv_errcod = 40mmm) THEN . Immediate coordination is the default. In most cases. rather than to a block or item. Oracle Forms marks the blocks as needing to be coordinated. lv_errtxt VARCHAR2(80) := ERROR_TEXT. • When Immediate coordination is set. On–Error triggers should be attached to the form. Usage Notes: Oracle Forms creates the On–Clear–Details trigger automatically when you define a master– detail block relation. DECLARE lv_errcod NUMBER := ERROR_CODE. ERROR_TYPE. DBMS_ERROR_TEXT. On-Error Replace a default error message with a custom error message. lv_errtyp VARCHAR2(3) := ERROR_TYPE. or to trap and recover from an error. • If you intend to manage block coordination yourself. or DBMS_ERROR_CODE built–in function in an On–Error trigger to identify a specific error condition. • Example: The following example checks specific error message codes and responds appropriately.MESSAGE-HANDLING TRIGGERS Form Builder automatically issues appropriate error and informational messages in response to runtime events.

.. ELSE . 1.. This prevents attempts at very large queries. END. END. END IF... Pre-Query Validate the current query criteria or provide additional query criteria programmatically. RAISE Form_Trigger_Failure. 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. lv_errcod NUMBER := MESSAGE_CODE. ELSE Message(lv_errtyp||’–’||to_char(lv_errcod)||’: ’||lv_errtxt).. IF alert_button = ALERT_BUTTON1 THEN . for example. Date Ordered.Shik Mahamood Ali /* ** More tasks here */ 51 . 2.. to replace a default message issued by Form Builder with a custom message.QUERY-TIME TRIGGERS Query-time triggers fire just before and just after the operator or the application executes a query in a block. On-Message To trap and respond to a message. ELSIF (lv_errcod = 40zzz) THEN ** More tasks here */ ELSE Message(lv_errtyp||’–’||to_char(lv_errcod)||’: ’||lv_errtxt). lv_errtxt VARCHAR2(80) := MESSAGE_TEXT. or Date Shipped. END IF. RAISE Form_Trigger_Failure. This Pre-Query trigger on the S_ORD block only permits queries if there is a restriction on either the Order ID. F. END IF. just before sending the SELECT statement to the database. BEGIN IF lv_errcod = 40350 THEN alert_button := Show_Alert(’continue_alert’). lv_errtype VARCHAR2(3) := MESSAGE_TYPE.

B] This Post-Query trigger on the S_ORD block selects the total count of line items for the current Order. 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. RAISE Form_Trigger_Failure.’). FETCH lookup_payplan INTO :Employee. Begin SELECT COUNT(ord_id) INTO :S_ORD. Post-Query fires for each record that is fetched into the block as a result of a query. [ exact_match – Check Box User can specify if or not a query condition for a customer name should exactly match the table value.’Y’)=’N’ then :S_Customer. . Make sure the user has given one of the two Columns which we have indexed in their search criteria. Use it to perform calculations and populate additional items.Ename IS NULL AND :Employee.Payplan_Id. This trigger is defined at block level or above. END IF. DECLARE CURSOR lookup_payplan IS SELECT Payplan_Desc FROM Payplan WHERE Payplan_Id = :Employee. ] IF nvl(:control. for display in non–database items in the current block. 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. Fires once for each record fetched into the block. Example: This example retrieves descriptions for code fields.id. such as looking up values in other tables based on a value in the current record. Post-Query Perform an action after fetching a record.lineitem_count FROM S_ITEM WHERE ord_id = :S_ORD. CURSOR lookup_area IS SELECT Area_Name FROM Zip_Code WHERE Zip = :Employee. otherwise fail the query with a helpful message A] IF :Employee. END IF. End.Zip.name:=’%’||:S_customer. ** Use Explicit Cursor for highest efficiency.Shik Mahamood Ali • • • 52 To test the operator’s query conditions. BEGIN /* Lookup the Payment Plan Description given the Payplan_Id in the Employee Record just fetched.Payplan_Desc_Nondb.exact_match. 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). and displays this number as a summary value in the non base table item :Lineitem_count.Mgr IS NULL THEN Message(’Supply Employee Name and/or Manager Id ’||’for Query. [ Set the initial value property to “Y”. 2. Use it to check or modify query conditions.*/ OPEN lookup_payplan.name || ‘%’.

Example The Pre-Text-Item trigger fires just before entering a text item.TRIGGERS Fire as Form Builder navigates internally through different levels of the object hierarchy. For instance. when the operator clicks on a text item in another block. FETCH lookup_area INTO :Employee. What Happens When a Navigation Trigger Fails? . END. CLOSE lookup_area. Use it to perform calculations and populate additional items. G. Use it to check or modify query conditions. • • A Pre-Query trigger fires before a query executes.and Post. if the validation unit is Record. For instance. POST-QUERY fires 10 times. Pre-query trigger fires before pre-select trigger.navigation triggers fire during navigation.and Post. 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. */ OPEN lookup_area.and Post-Text-Item triggers do not fire. A Post-Query trigger fires as each record is fetched (except array processing). I ] PRE.Area_Desc_Nondb. navigational events occur as Form Builder moves the input focus from the current item to the target item. 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.Shik Mahamood Ali CLOSE lookup_payplan. When Do Navigation Triggers Not Fire? The Pre. When Do Pre. Use Explicit ** Cursor for highest efficiency. 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.NAVIGATIONAL TRIGGERS Navigational triggers fire in response to navigational events. 53 /* ** Lookup Area Descript given the Zipcode in ** the Employee Record just fetched. but before the statement is actually issued.and Post-Navigation Triggers Fire? The Pre. A query fetched 10 records How many times does a PRE-QUERY Trigger and POST-QUERY Trigger will get executed? PRE-QUERY fires once.AND POST.

it appears that the input focus has not moved at all. IF not (DBMS_SESSION. 2. PAUSE. during navigation from one block to another.IS_ROLE_ENABLED(’ADMINISTRATIVE’) or (DBMS_SESSION. 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: .IS_ROLE_ENABLED(’TECHNICAL’) THEN MESSAGE(’You are not authorized to run this application’). RAISE form_trigger_failure.Shik Mahamood Ali 54 If a Pre. To the user. Pre-Form Perform an action just before Form Builder navigates to the form from "outside" the form. such as at form startup. the input focus returns to its initial location (where it was prior to the trigger firing). Pre-Block Perform an action before Form Builder navigates to the block level from the form level.or Post navigation trigger fails. END IF. Fires during the Enter the Block process. 1.

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

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

v_ignore NUMBER.where_cls’). 1d. when the form returns to a quiet state to wait for operator input. EXECUTE_QUERY. (Occurs after the Pre-Form trigger fires). 1. DEFAULT_WHERE. SET_WINDOW_PROPERTY( forms_mdi_window. :GLOBAL.:GLOBAL. rg_emps RECORDGROUP. Example The When-New-Item-Instance trigger fires immediately after navigation to a new instance of an item. TITLE. Then. :GLOBAL.width_win_order := GET_WINDOW_PROPERTY(’win_order’. these triggers fire just after Form Builder moves the input focus to a different item. Specifically. SET_BLOCK_PROPERTY(’prod_lov_blk’. BEGIN DEFAULT_VALUE(’’.Shik Mahamood Ali 57 Fire at the end of a navigational sequence that places the input focus on a different item. WIDTH). When-New-Form-Instance Trigger at Form Level BEGIN SET_WINDOW_PROPERTY( forms_mdi_window. Perform a query of all orders. END. WINDOW_STATE.HEIGHT). END. DECLARE htree ITEM.“object”-Instance Triggers Fire? The When-New-”object”-Instance triggers fire immediately after navigation to the object specified as part of the trigger name.where_cls). END.height_win_order := GET_WINDOW_PROPERTY(’win_order’.WIDTH). :GLOBAL. 1b.width_win_inventory := GET_WINDOW_PROPERTY(’win_inventory’. . ’'GLOBAL. 1c. BEGIN EXECUTE_QUERY.height_win_inventory := GET_WINDOW_PROPERTY(’win_inventory’. when the ORDERS form is run. a record group is created and the hierarchical tree is populated. When-New-Form-Instance Perform an action at form start-up. EXECUTE_QUERY. :GLOBAL. The example locates the hierarchical tree first. Example This code could be used in a WHEN-NEW-FORM-INSTANCE trigger to initially populate the hierarchical tree with data. MAXIMIZE ).HEIGHT). by including the following code in your When-New-Form-Instance trigger: 1a. When Do When-New. ’Summit Sporting Goods Application’).

to_char(empno) ’ ||' from emp ' ||'connect by prior empno = mgr ' ||’start with job = ’’PRESIDENT’’’). Begin Filename:=get_product_image(:S_ITEM. Ftree. PROPERTY_FALSE).DELETE_ALLOWED.’S_ITEM.Job = ’CLERK’ THEN Break. level. Example The following example of a When-New-Block-Instance trigger conditionally sets the DELETE ALLOWED property to FALSE. END. each time Oracle Forms instantiates a new record in the block. and populates the product_image item with a picture of the products. Else Read_Image_File(filename. END IF. if one exists 1] Declare Filename varchar2(20). rg_emps). For example. . 2] 1.PRODUCT_ID). 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.RECORD_GROUP. NULL. rg_emps := Create_Group_From_Query('rg_emps'. End if End. IF GET_APPLICATION_PROPERTY(username) = ’SCOTT’ THEN SET_BLOCK_PROPERTY(’S_ITEM’. Oracle Forms fires this trigger each time the input focus moves to the next record. in other words.*/ BEGIN IF :Emp. 3. Usage Notes: Use a When–New–Block–Instance trigger to perform an action every time Oracle Forms instantiates a new block.Shik Mahamood Ali 58 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.Set_Tree_Property(htree. fires after the When-New-Block-Instance trigger. Usage Notes: Use a When–New–Record–Instance trigger to perform an action every time Oracle Forms instantiates a new record. Example The Cursor arrives in each record of the S_Item block.htree3').’tiff’. v_ignore := Populate_Group(rg_emps). ename.a Example: Brings up the debugging window for a particular ** value of the ’JOB’ item anytime the user changes records.’select 1. when an operator presses [Down] to scroll through a set of records.product_image’). If the new record is in a different block. but before the When-New-Item-Instance trigger. 2. If Filename= ‘ No file’ then Null. Ftree.

59 3. Perform an action immediately after the input focus moves to a different item. Clear_Block(No_Validate). END.Empno. 3].Shik Mahamood Ali Call_Form(’clerk_timesheet’). BEGIN IF :Emp. End if. END IF. The following trigger accomplishes that operation. it fires after navigation to an item.EMPNO’ and :System.] BEGIN IF (:global.Example: Clear the current item if it does not represent ** the first day of a month.mode = 'ENTER-QUERY') THEN Exit_Form. :global. 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.cancel_query = 'N'.Hiredate.Employee_Id := :Emp.When-New-Item-Instance Fires when the input focus moves to an item. END IF. 4. 4]. Break. when Form Builder is ready to accept input in an item that is different than the item that previously had input focus. . END IF.cancel_query = 'Y' and :system. Usage Notes Use a When-New-Item-Instance trigger to perform an action whenever an item gets input focus. END. END IF. Message(’This date must be of the form 01–MON–YY’).Mode = ’ENTER–QUERY’ THEN IF NOT Show_Lov(’my_lov’) THEN RAISE Form_Trigger_Failure. Specifically.Empno IS NOT NULL THEN :Global. GO_ITEM(’S_ORD.date_shipped’. The WhenNew-Item-Instance trigger is especially useful for calling restricted (navigational) built-ins. BEGIN IF :System. END IF. 1] IF CHECKBOX_CHECKED(’S_ORD. If the new item is in a different block. property_true).date_shipped’). END IF.Cursor_Item = ’EMP.order_filled’)THEN SET_ITEM_PROPERTY(’S_ORD. BEGIN IF TO_CHAR(:Emp. END.’DD’) <> ’01’ THEN Clear_Item.UPDATE_ALLOWED. END. fires after the When-New-Block-Instance trigger. 2] Built–in: CLEAR_ITEM .

Range (Lowest-Highest Allowed Value) . then the status of each item in the record is checked. validation succeeds. VALIDATION TRIGGERS 60 Validation triggers fire when Form Builder validates data in an item or record. If not.Shik Mahamood Ali END. such as a Commit operation.Required (if so. all records below that level are validated. . it is set to valid. and processing continues normally. then all records in the form are validated. At validation time. if present. Validation occurs at item.Data type . These checks are carried out before firing any When-Validate-Item triggers that you have defined. If validation fails. When the record passes these checks. Form Builder checks to see whether the record is valid. Using LOVs for Validation When you attach an LOV to a text item by setting the LOV property of the item. The following events then occur. and a When-Validate-Record trigger is then fired. When Does Validation Occur? Form Builder carries out validation for the validation unit under the following conditions: • The [Enter] key is (ENTER command is not necessary mapped to the key that is physically labeled Enter) pressed or the ENTER built-in procedure is run (whose purpose is to force validation immediately). but can also be set to record.Validate from List (see later in this lesson) • Record level: After leaving a record. record. or default processing. H. The validation unit is discussed in the next section. the LOV is not displayed. so that the operator can make corrections. then control is passed back to the appropriate level. programmatic control. then is the item null?) . block. For example. • The operator or a trigger navigates out of the validation unit.Format mask . Standard checks include the following: . if you commit (save) changes in the form. Do this by setting the Validate from List property to Yes for the item. block. The default validation unit is item. If an item has been changed and is not yet marked as valid. • 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. then Form Builder first performs standard validation checks to ensure that the value conforms to the item’s properties. Form Builder then automatically uses the item value as a non case-sensitive search string on the LOV contents. This includes when changes are committed. you can optionally use the LOV contents to validate data entered in the item. or form by the designer. • Block and form level: At block or form level. unless you have suppressed this action. Form Builder performs validation checks during navigation that occurs in response to operator input. Validation occurs at: • Item level: Form Builder records a status for each item to determine whether it is currently valid. and form levels. depending on the circumstances: • If the value in the text item matches one of the values in the first column of the LOV.

EXCEPTION WHEN No.Commplan_Desc FROM commplan WHERE commcode = :Employee.Commcode. END.INTO statement must return an error if more than one row is retrieved that matches the criteria. If validation succeeds. Use <List> for help'). • If the item value causes multiple records to be found in the LOV.Data_Found THEN Message('Invalid Commission Plan. When – Validate -Item Fires during the Validate the Item process. Validation Triggers • Item level When-Validate-Item • Block level When-Validate-Record 1. Example The SELECT. When – Validate -Record . The trigger fires after standard item validation. The Defer_Required_Enforcement property postpones enforcement of the Required property from item validation to record validation. This implies PL/SQL may attempt to fetch data twice from the table in question to insure that there aren't two matching rows. Usage Notes • • Use a When-Validate-Item trigger to supplement Form Builder default item validation processing.. Specifically. • When-Validate-Item Trigger You have already used this trigger to add item-level validation. Form Builder marks the changed item as Valid and does not re-validate it. but is a partial value of the LOV value. Form Builder displays the LOV and uses the text item value as the search criteria to automatically reduce the list. Setting the Defer_Required_Enforcement property to Yes allows the operator to move freely among the items in the record. The item then passes this validation phase. then the full LOV contents are displayed to the operator. and input focus is returned to the item if the trigger fails. then the full LOV column value is returned to the item (providing that the item is defined as the return item in the LOV).Shik Mahamood Ali 61 • If the item’s value causes a single record to be found in the LOV. 2. RAISE Form_Trigger_Failure. • If no match is found. so that the operator must choose. BEGIN SELECT description INTO :Employee. Duplicate entries in COMMPLAN table!'). While this behavior is necessary to avoid validation loops. When an item has the Required property set to Yes. WHEN Too_Many_Rows THEN Message('Error. it fires as the last part of item validation for items with the New or Changed validation status. it does make it possible for your application to commit an invalid value to the database. It is possible to write a When-Validate-Item trigger that changes the value of an item that Form Builder is validating.. RAISE Form_Trigger_Failure. by default Form Builder will not allow navigation out of the item until a valid value is entered.

This code presumes both date items are mandatory and that neither will be NULL.Start_Date > :Experiment. you can use this trigger to perform additional checks that may involve more than one of the record’s items.Fire the Post-Delete trigger. it does make it possible for your application to commit an invalid value to the database. END. Since these two text items have values that are related. it's more convenient to check the combination of them once at the record level. 4 Validate the block (for all blocks in sequential order). For all inserted or updated records of the block in sequential order: . 2 Process save point. in the order they were entered. ** Structured this way. If validation succeeds. While this behavior is necessary to avoid validation loops. Specifically. RAISE Form_Trigger_Failure. /* Method 1: Hardcode the item names into the trigger. .Shik Mahamood Ali 62 Fires during the Validate the Record process. END IF. when the operator has left a new or changed record. I. Transaction processing includes two phases: • Post: – Writes record changes to base tables – Fires transactional triggers • Commit: Performs database commit Errors result in: • Rollback of the database changes • Error message The Commit Sequence of Events The commit sequence of events (when the Array DML size is 1) is as follows: 1 Validate the form. the chance this code will ** be reusable in other forms we write is pretty low because of dependency on block and item ** names. When-Validate-Record must be defined at block level or above.TRANSACTIONAL TRIGGERS Transactional triggers fire in response to a wide variety of events that occur as a form interacts with the data source. When-Validate-Record Trigger This trigger fires after standard record-level validation. it fires as the last part of record validation for records with the New or Changed validation status. Use a When-Validate-Record trigger to supplement Form Builder default record validation processing.Fire the Pre-Delete trigger. . Form Builder marks the record and all of the fields as Valid and does not re-validate. 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.*/ BEGIN IF :Experiment. 3 Fire the Pre-Commit trigger. Because Form Builder has already checked that required items for the record are valid.Delete the row from the base table or fire the On-Delete trigger.End_Date THEN Message('Your date range ends before it starts!'). For all deleted records of the block (in reverse order of deletion): . rather than check each item separately. Example The following example verifies that Start_Date is less than End_Date.

Check the record uniqueness. END. Pre-Commit Check user authorization. END IF. . PRE-DELETE TRIGGER -DECLARE CURSOR C1 IS SELECT ’anything’ FROM S_ORD WHERE customer_id = :S_CUSTOMER. Fire the Post-Update trigger. Usage Notes • Use a Pre-Delete trigger to delete the detail record of a master record. ELSE CLOSE C1. Check the record uniqueness Update the row in the base table or fire the On-Update trigger.Copy Value From Item. . IF C1%FOUND THEN MESSAGE(’There are orders for this customer!’). set up special locking Pre-Commit Fires once during commit processing.Insert the row into the base table or fire the On-Insert trigger. such as setting up special locking requirements. even if there are no changes to post.Fire the Pre-Insert trigger. Pre-Delete Journaling. 5 Fire the Post-Forms-Commit trigger. before base table blocks are processed.dummy. Commit Triggers Uses 1. • 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.) Usage Notes: Use a Pre–Commit trigger to perform an action. If it is an updated record: Fire the Pre-Update trigger. RAISE form_trigger_failure.id. If the current operation is COMMIT. Pre-Insert . Pre-Commit: Fires once if form changes are made or uncommitted changes are posted 2.Shik Mahamood Ali 63 If it is an inserted record: . 7 Fire the Post-Database-Commit trigger. Final checks before row deletion 3. before a row is deleted. . . then: 6 Issue an SQL-COMMIT statement. anytime a database commit is going to occur. FETCH C1 INTO :GLOBAL. It fires once for each record that is marked for delete.Fire the Post-Insert trigger. BEGIN OPEN C1. implement foreign-key delete rule Fires during the Post and Commit Transactions process. 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.

Shik Mahamood Ali 64 Fires during the Post and Commit Transactions process. */ IF :Order. Note: The Insert Allowed and Keyboard Navigable properties on :S_ORD.. Could use SELECT. If you use this method. which will be written to the ID column when the row is subsequently inserted. automatically generated columns. BEGIN /* ** Fetch the next sequence number from the ** explicit cursor directly into the item in ** the Order record. username. It fires once for each record that is marked for update. 4. RAISE Form_Trigger_Failure. check constraints . recording the new upper value for the sequence. operation. DECLARE CURSOR next_ord IS SELECT orderid_seq. USER.SYSDATE ). ** but explicit cursor is more efficient. End.OrderId. implement foreign-key update rule. CLOSE next_ord.. timestamp ) VALUES ( :Order.NEXTVAL FROM dual. journaling.id FROM SYS. Example:2 This example assigns a primary key field based on a sequence number. check constraints Usage Notes: Use a Pre–Insert trigger to perform the following tasks: • Example:1 • change item values keep track of the date a record is created and store that in the record prior to committing This Pre-Insert trigger on the S_ORD block assigns an Order ID from the sequence S_ORD_ID. Generate sequence numbers. You can also assign sequence numbers from a table.nextval INTO :S_ORD. */ OPEN next_ord. and then writes a row into an auditing table. before a row is updated. Journaling.OrderId. before a row is inserted..dual. ’New Order’.OrderId IS NULL THEN Message(’Error Generating Next Order Id’). END IF. • Use Post-Insert to update the sequence table. It fires once for each record that is marked for insert. Pre-Update Fires during the Post and Commit Transactions process. END. auto-generated columns. /* ** Make sure we populated a new order id ok.id should be No.. /* ** Insert a row into the audit table */ INSERT INTO ord_audit( orderid. FETCH next_ord INTO :Order. Begin SELECT S_ORD_ID. so that the user does not enter an ID manually. flagging creation of a new order.INTO. 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.

END. /* ** If the old and current values are different. 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. CURSOR old_value IS SELECT discount_pct FROM customer WHERE CustId = :Customer. DECLARE old_discount NUMBER. • To perform the default processing from this trigger. the commit operation behaves normally. inserts. FETCH old_value INTO old_discount.INTO but choose an explicit cursor for efficiency. BEGIN IF Get_Application_Property(DATA_SOURCE) = ’ORACLE’ THEN .CustId. call to the COMMIT_FORM built–in. Example: The following example writes a row into an Audit Table showing old discount and new discount for a given customer. END IF..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. By default. ** ’Changed Discount from 13. /* ** Insert the audit record with timestamp and user */ INSERT INTO cust_audit( custid.5% to 20%’ */ oper_desc := ’Changed Discount from ’|| TO_CHAR(old_discount)||’% to ’|| TO_CHAR(new_discount)||’%’. Example: This example disables the commit operation when running against a datasource that does not support transaction control. If the application is running against ORACLE.USER.Discount_Pct. On-Commit Fires whenever Oracle Forms would normally issue a database commit statement to finalize a transaction.CustId.oper_desc. 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. new_discount NUMBER := :Customer. this operation occurs after all records that have been marked as updates. oper_desc VARCHAR2(80). We need to do this since the value of :Customer.SYSDATE ).. including timestamp and username making the change. and deletes have been posted to the database. We could use SELECT. operation. username.Shik Mahamood Ali 65 Usage Notes: Use a Pre–Update trigger to audit transactions. */ OPEN old_value. CLOSE old_value. BEGIN /* ** Fetch the old value of discount percentage from the database by CustomerId. e.g. timestamp ) VALUES ( :Customer. 5.

Shik Mahamood Ali 66 Commit_Form.Using_Transactional_Triggers = 'TRUE' THEN User_Exit('my_insrec block=EMP'). it fires after the Pre–Delete trigger fires and before the Post–Delete trigger fires. To perform the default Form Builder processing from this trigger. BEGIN UPDATE emp SET termination_date = SYSDATE WHERE empno = :Emp. rather than actually deleting the employee from the database. Syntax PROCEDURE INSERT_RECORD. Example: This example updates the employee table to set the Termination_Date. */ ELSE Insert_Record. END. include a call to the INSERT_RECORD built-in. /* ** Otherwise. perhaps based on a parameter. when Form Builder would normally insert a record in the database. Description When called from an On-Insert trigger. inserts the current record into the database during Post and Commit Transactions processing. that is. replacing the actual database delete of a given row. no action is performed */ END. On-Delete Fires during the Post and Commit Transactions process. This built-in is included primarily for applications that will run against a nonORACLE datasource. do the right thing. It fires once for each row that is marked for insertion into the database. /* ** Built-in: INSERT_RECORD ** Example : Perform Form Builder standard insert processing ** based on a global flag setup at startup by the ** form. END IF. /* ** otherwise. To perform the default Oracle Forms processing from this trigger. 7. The trigger fires once for each row that is marked for deletion from the database. Specifically. it fires after the Pre-Insert trigger fires and before the Post-Insert trigger fires. On-Insert Fires during the Post and Commit Transactions process when a record is inserted. include a call to the DELETE_RECORD built–in. Specifically. to delete a record from your form or from the database.Empno. Usage Notes: • • Use an On–Delete trigger to replace the default Oracle Forms processing for handling deleted records during transaction posting. . 6. ** Trigger: On-Insert */ BEGIN /* ** Check the global flag we setup at form startup */ IF :Global. Usage Notes • • Use an On-Insert trigger to replace the default Form Builder processing for handling inserted records during transaction posting.

but before the transaction has been finalized by issuing the Commit.. it fires after the Pre–Update trigger fires and before the Post–Update trigger fires. On-Update 67 Fires during the Post and Commit Transactions process. 8. . updates..Did_DB_Commit = 'FALSE'). Post – Database Commit Description Fires once during the Post and Commit Transactions process.. END. DML Statements Issued During Commit Processing INSERT INTO base_table ( base_column. Begin UPDATE RECORD.'Global.Form_Status = 'QUERY' AND :Global. and deletes have been posted to the database. RETURN (:System. To perform the default Oracle Forms processing from this trigger. • The Update Changed Columns Only and Enforce Column Security properties affect UPDATE statements. base_column. initiates the default Form Builder processing for updating a record in the database during the Post and Commit Transaction process.. • Form Builder uses and retrieves ROWID. Example /* ** FUNCTION recs_posted_and_not_committed ** RETURN BOOLEAN IS BEGIN Default_Value('TRUE'. include a call to the UPDATE_RECORD built–in... . The Post-DatabaseCommit Trigger fires after Form Builder issues the Commit to finalize the transaction. after the database commit occurs. Usage Notes Use a Post-Database-Commit trigger to perform an action anytime a database commit has occurred.Shik Mahamood Ali END IF. END. when Oracle Forms would normally update a record in the database. . This built-in is included primarily for applications that run against a non-ORACLE data source..) UPDATE base_table SET base_column = :base_item.Did_DB_Commit'). Specifically. • Locking statements are not issued. It fires once for each row that is marked for update in the form. 9.WHERE ROWID = :ROWID DELETE FROM base_table WHERE ROWID = :ROWID DML Statements Issued During Commit Processing Rules: • DML statements may fire database triggers. Note that the Post-Forms-Commit trigger fires after inserts. Usage Notes: • • Use an On–Update trigger to replace the default Oracle Forms processing for handling updated records during transaction posting. base_column = :base_item. :base_item.) VALUES ( :base_item. End. When called from an On-Update trigger.

. It fires once for each row that is deleted from the database during the commit process. SYSDATE. Post – Form . updates. without posting changes to the database. 11. or deletes.Did_DB_Commit := 'FALSE'. END. Form Builder fires the Post-Forms-Commit trigger immediately. anytime a database commit is about to occur. USER ).Did_DB_Commit = FALSE'). 68 Post-Database-Commit Determines if commit was successful. /* FUNCTION recs_posted_and_not_committed RETURN BOOLEAN IS BEGIN Default_Value('TRUE'. after a row is deleted. or deletes. End.Commit Fires once during the Post and Commit Transactions process.1 Begin INSERT INTO delete_audit (id.Form_Status = 'QUERY'AND :Global. Example . Post – Delete Fires during the Post and Commit Transactions process. If there are records in the form that have been marked as inserts. IF SQL%NOTFOUND THEN MESSAGE(’Record not found in database’). Example .id. If the operator or the application initiates a Commit when there are no records in the form have been marked as inserts. RETURN (:System. Usage Notes • • Use a Post-Forms-Commit trigger to perform an action.Did_DB_Commit'). */ BEGIN :Global. who_did_it)VALUES ( :S_ORD. determines if there are posted. 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. RAISE form_trigger_failure. form or block Usage Notes: Use a Post–Delete trigger to audit transactions. the Post-Forms-Commit trigger fires after these changes have been written to the database but before Form Builder issues the database Commit to finalize the transaction.Shik Mahamood Ali */ BEGIN :Global.Did_DB_Commit := 'FALSE'.2 Begin Delete from S_ORD SET WHERE id = :S_ORD. END. timestamp.id. updates. uncommitted changes 10.'Global. END. such as updating an audit trail.

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

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

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

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

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

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

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

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

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

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

when the mouse is double-clicked within any item in the block if attached to an item. 3.Shik Mahamood Ali 79 • if attached to an item. 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. an online help window must appear. Usage Notes Use the When-Mouse-Click trigger to perform an action every time the operator clicks the mouse within an item and/or canvas. When-Mouse-Down Trigger Description . If the operator double-clicks the mouse. 2. a product information window must appear. when the mouse is double-clicked within any canvas or item in the form if attached to a block. For example. if the operator clicks the mouse. 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. 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 Assume that an application requires Behavior A when the operator clicks the mouse and Behavior B when the operator double-clicks the mouse.

Alert_One will appear again unnecessarily if the operator subsequently enters Canvas_One with the mouse. but appear side by side on the screen. when the operator moves the mouse out of Canvas_Two. However. When the operator dismisses the message box. Assume also that your application contains two canvases. Be careful when calling a modal window from a When-Mouse-Enter trigger. any When-Mouse-Leave triggers associated with this event will fire. assume that Alert_One displays within Canvas_Two's border. assume that your When-Mouse-Enter trigger causes Alert_One to appear whenever the mouse enters Canvas_One.save_item_name := :SYSTEM.CURSOR_ITEM. Further. begin :GLOBAL. 4. when the mouse enters any item in the block if attached to an item.Shik Mahamood Ali 80 Fires after the operator presses down the mouse button if one of the following events occurs: • • • if attached to the form.id’). Finally. when the mouse is pressed down within any item in the block if attached to an item. when the mouse enters the item Usage Notes Use a When-Mouse-Enter trigger to perform an action every time the mouse enters an item or canvas. . when the mouse is pressed down within any canvas or item in the form if attached to a block. assume that the mouse has entered Canvas_One causing the When-Mouse-Enter trigger to fire which in turn causes Alert_One to appear. This may not be the desired behavior. Changing a tooltip's property in a When-Mouse-Enter trigger cancels the tooltip before it is ever shown. when the mouse enters any canvas or item in the form if attached to a block. For example. Canvas_One and Canvas_Two. Doing so may cause the modal window to appear unnecessarily. Canvas_One and Canvas_Two do not overlap each other. Iconic buttons and items on the canvas below the initial window cannot be selected. Note: The mouse down event is always followed by a mouse up event. the trigger fires and returns focus to the previous target. The user is able to scroll the canvas to see the items. GO_ITEM(’s_ord. Do not use the When-Mouse-Enter trigger on a canvas that is larger than the window. 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. 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. so the user is never able to click on those items. as soon as the mouse enters that area. In addition.

show_help_button := ’?’. When-Mouse-Move Trigger Description Fires each time the mouse moves if one of the following events occurs: • • • if attached to the form.Shik Mahamood Ali SHOW_VIEW(’cv_help’). when the mouse leaves any canvas or item in the form if attached to a block. END IF. 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 Description Fires after the mouse leave an item or canvas if one of the following events occurs: • • • if attached to the form. when the mouse moves within any canvas or item in the form if attached to a block. 5. WHEN-MOUSE-ENTER at Form Level begin 81 IF :SYSTEM. End. End. WHEN-MOUSE-LEAVE trigger on control. When-Mouse-Up Trigger Description Fires each time the operator presses down and releases the mouse button if one of the following events occurs: .MOUSE_CANVAS = ’CV_ORDER’ THEN :control. End. when the mouse leaves any item in the block if attached to an item. The When-Mouse-Move trigger may have performance implications because of the number of times this trigger can potentially fire. GO_ITEM(:GLOBAL. 6.save_item_name).show_help_button begin HIDE_VIEW(’cv_help’). 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. 7. when the mouse moves within any item in the block if attached to an item.

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

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

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

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

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

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

Shik Mahamood Ali 88 .

Sign up to vote on this title
UsefulNot useful