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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Usage Notes: Use Key–Fn triggers to create additional function keys for custom functions. */ wn_id1 := Find_Window(Window1). i. h := Get_Window_Property(wn_id1. /* ** Resize Window2 to the same size */ Resize_Window( Window2.Shik Mahamood Ali BEGIN 48 /* ** Find Window1 and get it’s width and height. C. 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. You can attach Key–Fn triggers to 10 keys or key sequences that normally do not perform any Oracle Forms operations.[ALL] ( KEY TRIGGERS ) Key Triggers have a one-to-one relationship with specific keys.HEIGHT). These keys are referred to as Key–F0 through Key–F9. the trigger fires when operator presses a specific key or key-sequence. w. Replace the default function associated with a function key.e. KEY. h ). you can define a Key-EXIT trigger to replace the default functionality of the [Help] key. you or the DBA must use Oracle Terminal to map the keys to the appropriate functions. Lock command on the default menu 1.WIDTH). .Key–Fn Trigger A Key–Fn trigger fires when an operator presses the associated key. w := Get_Window_Property(wn_id1. Before you can attach key triggers to these keys. END. For example.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Shik Mahamood Ali 88 .

Sign up to vote on this title
UsefulNot useful