This action might not be possible to undo. Are you sure you want to continue?
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;
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.
. /* ** Now. 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. Do not end the PL/SQL block with a slash.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. END. */ DECLARE procname VARCHAR2(30). my_stmt := my_stmt||’)’. COLn). while permitted. FOR I in 2. */ PROCEDURE Create_N_Column_Number_Table (n NUMBER) IS my_stmt VARCHAR2(2000). END.. IF NOT Form_Success THEN Message (’Table Creation Failed’). Example 3: /* ** Built–in: FORMS_DDL ** Example: The statement parameter can be a block ** of dynamically created PL/SQL code. Enclose the PL/SQL block in a valid BEGIN/END block structure. ** TEMP(COL1. */ Forms_DDL(my_stmt). END IF..*/ BEGIN Forms_DDL(’create table temp(n NUMBER)’). BEGIN . . COL2. IF NOT Form_Success THEN Message (’Table Creation Failed’). Line breaks. If you • • • • • If you use FORMS_DDL to execute a valid PL/SQL block: Use semicolons where appropriate. ELSE Message (’Table Created’). ELSE Message (’Table Created’). END LOOP. END IF. are not required. Example 2: /* ** Built–in: FORMS_DDL ** Example: The string can be an expression or variable. create the table.COL’||TO_CHAR(i)||’ NUMBER’. BEGIN my_stmt := ’create table tmp(COL1 NUMBER’. ** Create a table with n Number columns....N LOOP my_stmt := my_stmt||’.
ELSE Message (’Employee Maintenance Successful’). RETURN SQL_SUCCESS. or called form. ** and return a number representing the outcome of ** executing the SQL statement. ** A result of zero represents success.Shik Mahamood Ali 6 IF :global. IF Form_Success THEN RETURN SQL_SUCCESS. END. check_for_locks BOOLEAN := TRUE) RETURN NUMBER IS SQL_SUCCESS CONSTANT NUMBER := 0. End. Example 4: /* ** Built–in: FORMS_DDL ** Example: Issue the SQL statement passed in as an argument.’).Form_Status = ’CHANGED’ THEN Message (’DO_SQL: Form has outstanding locks pending. IF Check_For_Locks AND :System. ELSE RETURN Dbms_Error_Code. Forms_DDL(stmt). RETURN SQL_SUCCESS. then you can call this built-in to return information about the calling form. END IF. NEW_FORM . as well as about the current. END IF .’). BEGIN IF stmt IS NULL THEN Message (’DO_SQL: Passed a null statement. END IF. END IF. IF NOT Form_Success THEN Message (’Employee Maintenance Failed’).’). GET_FORM_PROPERTY Returns information about the given form. If your application is a multi-form application. */ FUNCTION Do_Sql (stmt VARCHAR2. ID_NULL Returns a BOOLEAN value that indicates whether the object ID is available. ELSE procname := ’Update_New_Employer’.flag = ’TRUE’ THEN procname := ’Assign_New_Employer’. END. Forms_DDL(’Begin ’|| procname ||’. END IF.
A parameter list passed to a form via NEW_FORM cannot contain parameters of type DATA_PARAMETER (a pointer to record group). These locks can also occur when invoking Oracle Forms from an external 3GL program. The data type of the name is CHAR. Oracle Forms runs the new form with the same Runform options as the parent form. The calling form is terminated as the parent form. NEW_FORM (formmodule_name VARCHAR2. If the calling form had been called by a higher form. The locks are still in effect when you regain control from Oracle Forms. which means that you retain any locks across a NEW_FORM operation. The name must be enclosed in single quotes. FULL_ROLLBACK Oracle Forms rolls back all uncommitted changes (including posted changes) that were made during the current Runform session. rollback_mode.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.) query_mode Takes one of the following constants as an argument: NO_QUERY_ONLY Runs the indicated form normally. Specify a parameter list when you want to pass parameters from the calling form to the new form. To avoid losing the locks issued by the calling form. Oracle Forms releases memory (such as database cursors) that the terminated form was using. paramlist_id Specifies the unique ID Oracle Forms assigns when it creates the parameter list. Oracle Forms prevents any commit processing in the called form. allowing the operator to perform inserts.data_mode. and deletes in the form. If the parent form was a called form. paramlist_name .Shik Mahamood Ali 7 Exits the current form and enters the indicated form. (Post–only mode can occur when your form issues a call to another form while unposted records exist in the calling form. NO_ROLLBACK Oracle Forms exits the current form without rolling back to a savepoint.query_mode. Oracle Forms runs the new form with the same options as the parent form. QUERY_ONLY Runs the indicated form as a query–only form. updates. The data type of the ID is PARAMLIST. You cannot specify a FULL_ROLLBACK from a form that is running in post–only mode. rollback_mode TO_SAVEPOINT Oracle Forms rolls back all uncommitted changes (including posted changes) to the current form’s savepoint. You can leave the top level form without performing a rollback.
allowing the operator to perform inserts. 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. HIDE is the default parameter. allowing the operator to query. The data type of the name is CHAR. paramlist_id . switch_menu NUMBER. display NUMBER. data_mode NUMBER. CALL_FORM (formmodule_name VARCHAR2. 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. updates. CALL_FORM. The name must be enclosed in single quotes. and deletes from within the called form. query_mode NUMBER. The data type of the name is CHAR.Shik Mahamood Ali 8 The name you gave the parameter list object when you defined it. A parameter list passed to a form via NEW_FORM cannot contain parameters of type DATA_PARAMETER (a pointer to record group). 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. DO_REPLACE Causes Oracle Forms to replace the default menu application of the calling form with the default menu application of the called form. or delete records. Parameters: formmodule_name Specifies the formmodule name of the called form. but not to insert. Oracle Forms runs the called form with the same Runform preferences as the parent form. QUERY_ONLY Causes Oracle Forms to run the indicated form in Query Only mode. Runs an indicated form while keeping the parent form active. paramlist_name VARCHAR2). display Specify one of the following constants as an argument: HIDE Causes Oracle Forms to clear the calling form from the screen before drawing the called form. update. NO_HIDE Causes Oracle Forms to display the called form without clearing the calling form from the screen.
session_mode.activate_mode. session_mode NO_SESSION Specifies that the opened form should share the same database session as the current form. The data type of the name is CHAR. SESSION Specifies that a new. activate_mode NUMBER. You can optionally include a parameter list as initial input to the called form.paramlist_id). OPEN_FORM (form_name VARCHAR2.activate_mode. activate_mode ACTIVATE Sets focus to the form to make it the active form in the application. paramlist_name The name you gave the parameter list object when you defined it. paramlist_id PARAMLIST). session_mode NUMBER. Call OPEN_FORM to create multiple–form applications.activate_mode). data_mode NUMBER.Shik Mahamood Ali 9 Specifies the unique ID Oracle Forms assigns when it creates the parameter list.session_mode. OPEN_FORM( OPEN_FORM( OPEN_FORM( OPEN_FORM( OPEN_FORM( REPLACE_MENU form_name). paramlist_id Specifies the unique ID that Oracle Forms assigns to the parameter list at the time it is created. form_name.paramlist_name). separate database session should be created for the opened form. Call_Form(’lookcust’. The data type of the ID is PARAMLIST. form_name Specifies the CHAR name of the form to open. paramlist_name Specifies the CHAR name of a parameter list to be passed to the opened form. form_name. form_name.NO_HIDE.activate_mode.QUERY_ONLY).session_mode). A COMMIT operation in any form will cause validation and commit processing to occur for all forms running in the same session. that is. form_name. The current form remains current. NO_ACTIVATE Opens the form but does not set focus to the form.DO_REPLACE. . OPEN_FORM Opens the indicated form. applications that open more than one form at the same time. Use the GET_PARAMETER_LIST function to return the ID to a variable of type PARAMLIST.
value). Description: The GET_APPLICATION_PROPERTY built–in returns information about the current Oracle Forms application. The value is always a character string. Form.FORM_STATUS becomes CHANGED only after at least one record in the form has been changed and the associated navigation unit has also changed.Shik Mahamood Ali 10 Replaces the current menu with the specified menu. The value of SYSTEM. SET_FORM_PROPERTY( formmodule_name. the_connect IN OUT VARCHAR2) IS BEGIN the_username := Get_Application_Property(USERNAME). SYSTEM. for use in calling ** another Tool. SET_FORM_PROPERTY Sets a property of the given form. */ PROCEDURE Get_Connect_Info( the_username IN OUT VARCHAR2. the_connect := Get_Application_Property(CONNECT_STRING). Indicates that the form contains only New records.SYSTEM. the_password := Get_Application_Property(PASSWORD). The value can be one of three character strings: CHANGED Indicates that the form contains at least one block with a Changed record.FORM_STATUS SYSTEM. Example 2: /* ** Built–in: GET_APPLICATION_PROPERTY ** Example: Capture the username and password of the ** currently logged–on user. .CURRENT_FORM SYSTEM. REPLACE_MENU also allows you to change the way the menu displays and the role. END. You must call this built–in once for each value you want to retrieve. END.Form_Status = ’CHANGED’THEN Commit_Form. NEW QUERY IF :System. PROCEDURE STORE_FORMNAME IS BEGIN :GLOBAL. The form contains at least one block with QUERY records and no blocks with CHANGED records. property. but does not make the new menu active. value).Calling_Form := :System. tm_name := Get_Application_Property(TIMER_NAME).FORM_STATUS represents the status of the current form. Indicates that a query is open. the_password IN OUT VARCHAR2.CURRENT_FORM represents the name of the form that Form Builder is executing. 2. property.Current_Form.System Variables 1. Syntax: SET_FORM_PROPERTY( formmodule_id.
All blocks are either single-record or multi-record blocks: A single-record block displays one record at a time. and delete rows within a database. 2. meaning that a query is currently being processed. the association between a data block and the database allows operators to automatically query. The value is always a character string. Control Blocks A control block is not associated with the database. In addition.MODE indicates whether the form is in Normal. END. Clear_Form.Shik Mahamood Ali END IF.Cursor_Item = ’EMP. update. SYSTEM. or transactional triggers. procedures. It provides a mechanism for grouping related items into a functional unit for storing. QUERY Indicates that the form is currently in fetch processing mode. Data blocks can be based on database tables. END IF. 3. Data Blocks Data blocks are associated with data (table columns) within a database. By default. views. NORMAL Indicates that the form is currently in normal processing mode. A multi-record block displays more than one record at a time. and the items in a control block do not relate to table columns within a database. or Fetch Processing mode. ENTER-QUERY Indicates that the form is currently in Enter Query mode. . Example: Assume that you want Oracle Forms to display an LOV when the operator enters query mode and the input focus is in a particular text item. BLOCKS Block is logical owner of items. A detail block displays detail records associated with a master record displayed in master block. displaying and manipulating records. insert. Enter Query. End if. The following trigger accomplishes that operation. 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.EMPNO’ and :System.Mode = ’ENTER–QUERY’ THEN IF NOT Show_Lov(’my_lov’) THEN RAISE Form_Trigger_Failure. Types of Blocks 1. /* ** When–New–Item–Instance Trigger */ BEGIN IF :System. MODE 11 SYSTEM.
. IF :System. 4. 3. NO_VALIDATE Form Builder flushes the current block without validating the changes." the current block. Form Builder sets the input focus to the first enterable item in the block you select from the LOV. property). END.Cursor_Block. performs a commit. and prints a message if ** the user chooses a new block out of the list to ** which to navigate. END IF. Clear_Block(No_Validate).Cursor_Block <> prev_blk THEN Message(’You successfully navigated to a new block!’). You must issue a call to the built-in once for each property value you want to retrieve. committing the changes. CLEAR_BLOCK built-in Causes Form Builder to remove all records from. DO_COMMIT Form Builder validates the changes. GET_BLOCK_PROPERTY Returns information about a specified block. or prompting the end user. FIND_BLOCK Searches the list of valid blocks and returns a unique block ID.Shik Mahamood Ali Block Built . 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. or "flush. Define the variable with a type of Block. GET_BLOCK_PROPERTY( block_name. NO_COMMIT Form Builder validates the changes and flushes the current block without performing a commit or prompting the end user. BLOCK_MENU built-in 12 Displays a list of values (LOV) containing the sequence number and names of valid blocks in your form. 2. */ DECLARE prev_blk VARCHAR2(40) := :System. property).ins 1. Example: /* ** Built–in: BLOCK_MENU ** Example: Calls up the list of blocks in the form when the ** user clicks a button. You must define an appropriately typed variable to accept the return value. Syntax: GET_BLOCK_PROPERTY( block_id. BEGIN BLOCK_MENU. and flushes the current block without prompting the end user.
NEXT_BLOCK Navigates to the first navigable item in the next enterable block in the navigation sequence 8. 7.DELETE_ALLOWED. Set_Block_Property(blk_id. Syntax: SET_BLOCK_PROPERTY( block_id. ELSE . top_rec := Get_Block_Property( bk_id.PREVIOUS_BLOCK Navigates to the first navigable item in the previous enterable block in the navigation sequence 9.Shik Mahamood Ali 13 ** Determine the (1) Current Record the cursor is in. If the target block is non-enterable . updates. TOP_RECORD). */ cur_rec := Get_Block_Property( bk_id. */ PROCEDURE Make_Block_Query_Only( blk_name IN VARCHAR2 ) IS blk_id Block. ** (2) Current Record which is visible at the ** first (top) line of the multirecord ** block. 6. property. 5. BEGIN /* Lookup the block’s internal ID */ blk_id := Find_Block(blk_name). Set_Block_Property(blk_id. ID_NULL Returns a BOOLEAN value that indicates whether the object ID is available. value).UPDATE_ALLOWED. and deletes to ** queried records in the block whose name is ** passed as an argument to this procedure.PROPERTY_FALSE). CURRENT_RECORD).PROPERTY_FALSE).INSERT_ALLOWED. SET_BLOCK_PROPERTY( block_name. value). /* ** If the block exists (ie the ID is Not NULL) then set ** the three properties for this block.SET_BLOCK_PROPERTY Sets the given block characteristic of the given block. Otherwise signal ** an error. GO_BLOCK GO_BLOCK navigates to an indicated block. property.PROPERTY_FALSE). Example: /* ** Built–in: SET_BLOCK_PROPERTY ** Example: Prevent future inserts. an error occurs. */ IF NOT Id_Null(blk_id) THEN Set_Block_Property(blk_id.
Item.System Variables 1. END IF. Record. Clear_Block.’). Record. If the current navigation unit is the form (as in the Pre. record.and Post. the value of SYSTEM. IF :System.and Post. 2.Shik Mahamood Ali 14 Message(’Block ’||blk_name||’ does not exist. or item (as in the Pre.Item. or the current data block during trigger processing. The following Key–CLRBLK trigger performs this function. END IF.CURSOR_BLOCK The value that the SYSTEM. END. 3. the value of SYSTEM.SYSTEM. The value is always a character string. Example: Assume that you want to create a trigger that performs a commit before clearing a block if there are changes to commit within that block. Indicates that the block contains only New records. the value of SYSTEM. Indicates that the block contains only Valid records that have been retrieved from the database. Block .SYSTEM.SYSTEM.BLOCK_STATUS SYSTEM. or item (as in the Pre. and Block triggers). The value can be one of three character strings: CHANGED NEW QUERY Indicates that the block contains at least one Changed record. RAISE Form_Trigger_Failure.CURRENT_BLOCK system variable represents depends on the current navigation unit: If the current navigation unit is the block. the value of SYSTEM. .CURSOR_BLOCK system variable represents depends on the current navigation unit: If the current navigation unit is the block.CURRENT_BLOCK is NULL. If the current navigation unit is the form (as in the Pre.and Post-Form triggers).and Post-Form triggers).CURRENT_BLOCK is the name of the block that Form Builder is processing or that the cursor is in.BLOCK_STATUS represents the status of a Data block where the cursor is located.CURSOR_BLOCK is NULL.CURSOR_BLOCK is the name of the block where the cursor is located. and Block triggers).CURRENT_BLOCK The value that the SYSTEM.Block_Status = ’CHANGED’ THEN Commit_Form. record.
MASTER_BLOCK This system variable works with its companion SYSTEM.TRIGGER_BLOCK represents the name of the block where the cursor was located when the current trigger initially fired. The following statement performs this function. When-Clear-Block. BEGIN curblk := :System. The value is always a character string. A Detail Block Can Be a Master You can create block relationships in which the detail of one master-detail link is the master for another link. END. using :SYSTEM. When-Database-Record. and on which master block of a master/detail relation. and the detail data block is based on the table with the foreign key. 4.Trigger_Block’)). The following trigger performs this function. When-Remove-Record MASTER-DETAIL RELATIONSHIP A master-detail relationship is an association between two data blocks that reflects a primaryforeign key relationship between the database tables on which the two data blocks are based. ELSIF curblk = ’ITEMS’ THEN Go_Block(’CUSTOMERS’). SYSTEM. 5. The master data block is based on the table with the primary key. SYSTEM. The value is NULL if the current trigger is a Pre. 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. Block – Based Triggers [Block Processing Trigger] When-Create-Record. DECLARE curblk VARCHAR2(30).CURSOR_BLOCK stored in a local variable.COORDINATION_OPERATION to help an On-Clear-Details trigger determine what type of coordination-causing operation fired the trigger.or Post-Form trigger.TRIGGER_BLOCK SYSTEM. A master-detail relationship equates to the one-tomany relationship in the entity relationship diagram. Go_Block(Name_In(’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. IF curblk = ’ORDERS’ THEN Go_Block(’ITEMS’). What Is a Relation? . ELSIF curblk = ’CUSTOMERS’ THEN Go_Block(’ORDERS’).Cursor_Block. END IF.
Property Use Non-Isolated Cascading Isolated Prevents the deletion of the master record when the detail records exist Deletes the detail records when a master record is deleted Deletes only the master record What Happens When You Modify a Relation? • • Changing the Master Deletes property from the default of Non-Isolated to Cascading replaces the On-Check-Delete-Master trigger with the Pre. a relation is automatically created. For example. S_ORD_S_ITEM. for example. Changing the Master Deletes property from the default of Non-Isolated to Isolated results in the removal of the On-Check-Delete-Master trigger.Shik Mahamood Ali 16 A relation is a Form Builder object that handles the relationship between two associated blocks. Like implicitly created relations. you can delete all corresponding line items when an order is deleted. or isolate deletion of a record in a master block when corresponding records exist in the detail block by setting the Master Deletes property. MASTER DELETES PROPERTY RESULTING TRIGGERS Non-Isolated (the default) On-Check-Delete-Master On-Clear-Details On-Populate-Details Cascading On-Clear-Details On-Populate-Details Pre-Delete Isolated On-Clear-Details On-Populate-Details . Explicit Relations If a relation is not established when default blocks are created. Master Deletes You can prevent. you can create your own by setting the properties in the New Relation dialog box. propagate. 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. This relation is named masterblock_detailblock. PL/SQL program units and triggers are created automatically when you explicitly create a relation.Delete trigger.
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. (Deferred False. To fetch the detail records. For example. and lengths from the database columns referenced in the SELECT statement. The columns in a query record group derive their default names. you can defer querying the line items for an order until the operator navigates to the item block. Deferred Without Auto Query When coordination-causing event occurs. the detail records are fetched immediately. 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.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 records in a query record group are the rows retrieved by the query associated with that record group. data types. the operator must navigate to the detail data block and explicitly execute a query. On-Populate-Details. When a coordination-causing event occurs. Oracle Forms does not automatically fetch the detail records. Non-query record groups can be created and modified only at runtime. 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. Non-query record group A non-query record group is a group that does not have an associated query. 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 . Query record groups can be created and modified at design time or at runtime. Default [Immediate] The default setting. Query record group A query record group is a record group that has an associated SELECT statement.
An unsuccessful query generates an ORACLE error number that corresponds to the particular SELECT statement failure. Sets the value for the record group cell identified by the given row and column.cell_value VARCHAR2) Sets the value for the record group cell identified by the given row and column. POPULATE_GROUP returns a 0 (zero). SET_GROUP_DATE_CELL (groupcolumn_id GroupColumn. array_fetch_size NUMBER). Form Builder automatically decrements the row numbers of all rows that follow a deleted row. Creates a record group with the given name. groupcolumn_name VARCHAR2. cell_value DATE). When rows are deleted. row_number NUMBER) Deletes the indicated row or all rows of the given record group. Executes the query associated with the given record group and returns a number indicating success or failure of the query. row_number Adds a row to the given record group. and they remain fixed at runtime. DELETE_GROUP_ROW (recordgroup_id RecordGroup. the appropriate memory is freed and available to Form Builder. query VARCHAR2) Populates a record group with the given query.column_type NUMBER. Populating Groups: POPULATE_GROUP (recordgroup_id RecordGroup). NUMBER). array_fetch_size NUMBER) Creates a non-query record group with the given name B] CREATE_GROUP_FROM_QUERY (recordgroup_name VARCHAR2. POPULATE_GROUP_WITH_QUERY (recordgroup_id RecordGroup. SET_GROUP_CHAR_CELL(groupcolumn_id GroupColumn. Upon a successful query. Modifying a group's structure: ADD_GROUP_COLUMN (recordgroup_name VARCHAR2. .row_number NUMBER. you define its structure and row values at design time. scope NUMBER. The record group is cleared and rows that are fetched replace any existing rows in the record group. query VARCHAR2. ADD_GROUP_ROW (recordgroup_name VARCHAR2. instead. Static record groups can be created and modified only at design time. Record Group built-in subprograms Creating and deleting groups: A] CREATE_GROUP (recordgroup_name VARCHAR2. The record group has columns representing each column you include in the select list of the query C] DELETE_GROUP (recordgroup_name VARCHAR2). scope NUMBER.Shik Mahamood Ali 18 A static record group is not associated with a query. row_number NUMBER. Deletes a programmatically created record group. column_width NUMBER) Adds a column of the specified type to the given record group. The rows that are retrieved as a result of a successful query replace any rows that exist in the group.
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). BEGIN /* ** Make sure the record group does not already exist. Returns the VARCHAR2 or LONG value for a record group cell identified by the given row and column. /* ** Populate group with a query . errcode NUMBER. /* Add two number columns to the record group */ gc_id := Add_Group_Column(rg_id. END IF. gc_id := Add_Group_Column(rg_id.cell_value NUMBER).Shik Mahamood Ali 19 SET_GROUP_NUMBER_CELL(groupcolumn_id GroupColumn. FIND_COLUMN (function) Example: /* ** Built–in: CREATE_GROUP ** Example: Creates a record group and populates its values ** from a query. row_number NUMBER). Getting cell values: GET_GROUP_CHAR_CELL (groupcolumn_id GroupColumn. NUMBER_COLUMN). create it and add the two ** necessary columns to it. /* ** If it does not exist. A cell is an intersection of a row and column. Sets the value for the record group cell identified by the given row and column. gc_id GroupColumn. row_number NUMBER. You must define an appropriately typed variable to accept the return value.*/ DECLARE rg_name VARCHAR2(40) := ’Salary_Range’. NUMBER_COLUMN). Searches the list of record groups and returns a record group ID when it finds a valid group with the given name. ’Emps_In_Range’. rg_id RecordGroup. */ IF Id_Null(rg_id) THEN rg_id := Create_Group(rg_name). ’Base_Sal_Range’. */ rg_id := Find_Group(rg_name). Define the variable with a type of RecordGroup.
’).COUNT(EMPNO) ’ ||’FROM EMP ’ ||’GROUP BY SAL–MOD(SAL.SHOW_LOV Displays a list of values (LOV) window at the given coordinates. Bell. LOV values are derived from record groups. LOV [ LIST OF VALUES ] An LOV is a scrollable popup window that provides the end user with either a single or multi-column selection list. independent of any specific text item. when the end user navigates to a text item with an associated LOV.Shik Mahamood Ali 20 */ errcode := Populate_Group_With_Query( rg_id. LOV values that are selected by the end user can be assigned to form items according to the return items you designate. The list of values remains displayed until the operator dismisses the LOV or selects a value. or programmatically. and FALSE if the operator Cancels and dismisses the list. 2.1000) ’ ||’ORDER BY 1’). RAISE Form_Trigger_Failure. LOV auto-reduction and search features allow end users to locate specific values. ’SELECT SAL–MOD(SAL. At design time. y). and returns TRUE if the operator selects a value from the list. x. LOV Properties . SHOW_LOV( lov_name. SHOW_LOV( lov_id.1000). LOV Built-in subprograms 1. an LOV can be attached to one or more text items in the form. BEGIN a_value_chosen := Show_Lov(’my_employee_status_lov’). SHOW_LOV( lov_name). y). x.LIST_VALUES LIST_VALUES displays the list of values for the current item. END. Example: /* ** Built–in: SHOW_LOV ** Example: Display a named List of Values (LOV) */ DECLARE a_value_chosen BOOLEAN. IF NOT a_value_chosen THEN Message(’You have not selected a value. END IF. SHOW_LOV( lov_id). Default Key for LOV – F9 LOVs provide the following functionality: LOVs can be displayed by end user request (when an LOV is available). as long as the input focus is in a text item that has an attached LOV.
giving the operator the option to explicitly select the remaining choice or dismiss the LOV. property NUMBER. 12. the focus remains in the text item after the operator makes a selection from the LOV. Automatic Skip (LOV) property Moves the cursor to the next navigable item when the operator makes a selection from an LOV to a text item. Long List It is used to append a ‘ where clause ‘ to the select statement.Shik Mahamood Ali 21 1.'new_group'). SET_LOV_COLUMN_PROPERTY Sets the given LOV property for the given LOV. property LOV). When Automatic Skip is set to No. property 5. Returns information about a specified list of values (LOV). When Automatic Confirm is set to No. GET_LOV_PROPERTY (lov_id.GROUP_NAME. In this dialog box any value can be entered. 8.Automatic Display property Specifies whether Form Builder displays the LOV automatically when the operator or the application navigates into a text item to which the LOV is attached.Automatic Refresh property Determines whether Form Builder re-executes the query to populate an LOV that is based on a query record group. 11. SET_LOV_PROPERTY(lov_id LOV. LOV. 10. 6.Validation from Lov to text item. 2. the LOV remains displayed. the LOV is dismissed automatically and column values from the single row are assigned to their corresponding return items. Set_LOV_Property('my_lov'.GROUP_NAME Specifies the name of the record group on which an LOV is based. 7.colnum NUMBER. 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 .value VARCHAR2).>If it is not specified then value from Lov cannot assigned to the block.Title property Specifies the title to be displayed for the object. 3. Sets the given LOV property for the given LOV. SET_LOV_COLUMN_PROPERTY (lov_id NUMBER. 4. from this value entered the where clause constructed. value NUMBER). .Automatic Select property Specifies what happens when an LOV has been invoked and the user reduces the list to a single choice when using auto-reduction or searching: When Automatic Confirm is set to Yes. When this property is true a dialog box appear. 9.Column Mapping This property is used to specify the return item.
END IF. list or name Specifies the parameter list. Data type – char – 2555 char maximum Global variables are visible across multiple forms Parameter values are not visible across multiple forms. It is passed between oracle products. The name of the parameter. Returns the current value and type of an indicated parameter in an indicated parameter list. key VARCHAR2. but before Form Builder returns to the normal event sequence. The data type of the key is VARCHAR2. 2. It can also passed between different oracle products. is of little value since it merely duplicates default Form Builder functionality. VARCHAR2). In the following example. This trigger. paramtype VARCHAR2. Adds parameters to a parameter list. GET_PARAMETER_ATTR (list VARCHAR2. 3. IF :customer. its type. Text Parameter It is passed between forms.id'). 5. DELETE_PARAMETER (list VARCHAR2. either by list ID or name. The value of the text parameter is a character string. using a Key-LISTVAL trigger allows you to add subsequent PL/SQL statements that execute after the LOV is displayed. 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. Creates a parameter list with the given name. key VARCHAR2.Shik Mahamood Ali 22 Key-LISTVAL Trigger: List_Values. The actual parameter can be either a parameter list ID of type PARAMLIST.CREATE_PARAMETER_LIST (name VARCHAR2).PROCEDURE DESTROY_PARAMETER_LIST (list VARCHAR2) Deletes a dynamically created parameter list and all parameters it contains. Each parameter consists of a key. or the VARCHAR2 name of the parameter list. But not between forms. key 4. Types 1. Parameter – Built Ins 1.id IS NULL THEN Go_Item ('customer. Data Parameter It is name of the record group present in the current form. key VARCHAR2) Deletes the parameter with the given key from the parameter list. ADD_PARAMETER (list VARCHAR2. However. 2.value VARCHAR2). . and an associated value. paramtype NUMBER. an IF statement is added to the previous trigger: Key-LISTVAL Trigger: List_Values.
The application looks for the module or document in the default paths defined for the called product. 6. Valid values are the name of a form module. BOOK specifies Oracle Book.Shik Mahamood Ali 23 list or name Specifies the parameter list to which the parameter is assigned. GRAPHICS specifies Oracle Graphics. Paramtype An OUT parameter of type NUMBER. Value An OUT parameter of type VARCHAR2. If the parameter is a data type parameter. SYNCHRONOUS specifies that control returns to Oracle Forms only after the called product has been exited. ASYNCHRONOUS specifies that control returns to the calling application immediately. TEXT_PARAMETER Indicates that the parameter's value is an actual data value. report. . or Oracle Book document. Valid numeric constants for this parameter are SYNCHRONOUS and ASYNCHRONOUS.list. paramtype NUMBER) Sets the type and value of an indicated parameter in an indicated parameter list. 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. commmode. Key The VARCHAR2 name of the parameter. document. The actual parameter you supply must be a variable of type NUMBER. location. product Specifies a numeric constant for the Oracle product you want to invoke: FORMS specifies a Runform session. display). REPORTS specifies Oracle Reports. document. If the called product is unavailable at the time of the call. execmode. Oracle Graphics display. commmode. and cannot be an expression. commmode Specifies the communication mode to be used when running the called product. or the VARCHAR2 name of the parameter list. display). key VARCHAR2. RUN_PRODUCT( product. If the parameter is a text parameter. Syntax: RUN_PRODUCT( product. The operator cannot work in the form while the called product is running. Form Builder returns a message to the end user.SET_PARAMETER_ATTR (list PARAMLIST. even if the called application has not completed its display.name. document Specifies the CHAR name of the document or module to be executed by the called product. the value is an actual text parameter. RUN_PRODUCT built-in Invokes one of the supported Oracle tools products and specifies the name of the module or module to be run. location. the value is the name of a record group. execmode. The actual parameter can be either a parameter list ID of type PARAMLIST.
*/ . or graph) generated by Oracle Graphics. always set execmode to RUNTIME. When you run Oracle Forms. */ pl_id := Get_Parameter_List(’tmpdata’). Valid constants for this property are FILESYSTEM and DB. (This parameter is only required when you are using an Oracle Graphics chart item in a form. bar chart.) 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. Valid numeric constants for this parameter are BATCH and RUNTIME. */ PROCEDURE Run_Emp_Report IS pl_id ParamList. either the file system or the database. To specify a parameter list ID. ** Presumes the Emp_Recs record group already ** exists and has the same column/data type ** structure as the report’s Emp_Query query. or NULL. list or name Specifies the parameter list to be passed to the called product. BEGIN /* ** Check to see if the ’tmpdata’ parameter list exists. Valid values for this parameter are the CHAR name of the parameter list. /* ** If it does. Data passing is supported only for master queries.) Note: You can pass text parameters to called products in both SYNCHRONOUS and ASYNCHRONOUS mode.Shik Mahamood Ali execmode 24 Specifies the execution mode to be used when running the called product. then delete it before we create it again in ** case it contains parameters that are not useful for our ** purposes here. Example: /* ** Built–in: RUN_PRODUCT ** Example: Call an Oracle Reports 2. passing the ** data in record group ’EMP_RECS’ to substitute ** for the report’s query named ’EMP_QUERY’. use a variable of type PARAMLIST. However.item_name. The name of the chart item must be specified in the format block_name. (SYNCHRONOUS mode is required when invoking Oracle Graphics to return an Oracle Graphics display that will be displayed in a form chart item. parameter lists that contain parameters of type DATA_PARAMETER (pointers to record groups) can only be passed to Oracle Reports and Oracle Graphics in SYNCHRONOUS mode.5 report. Note: You cannot pass a DATA_PARAMETER to a child query in Oracle Reports. execmode can be either BATCH or RUNTIME. When you run Oracle Reports and Oracle Graphics. location Specifies the location of the document or module you want the called product to execute. the ID of the parameter list. display Specifies the CHAR name of the Oracle Forms chart item that will contain the display (such as a pie chart.
’dept_query’. RAISE Form_Trigger_Failure. */ Add_Parameter(pl_id. RUNTIME. END IF. Add_Parameter(pl_id. RAISE Form_Trigger_Failure. /* ** Run the report synchronously.FILEYSTEM. ELSE Message(’Parameter list ’||pl_name||’ already exists!’). then add a data parameter to ** the list to associate named query ’DEPT_QUERY’ ** with record group ’DEPT_RECORDGROUP’. pl_name VARCHAR2(10) := ’tempdata’. . then ** attempt to create a new list. IF NOT Id_Null(pl_id) THEN Add_Parameter(pl_id. First ** make sure the list does not already exist. NULL). END IF. ’dept_recordgroup’).Shik Mahamood Ali 25 IF NOT Id_Null(pl_id) THEN Destroy_Parameter_List( pl_id ). BEGIN pl_id := Get_Parameter_List(pl_name). BEGIN pl_id := Get_Parameter_List(’tempdata’). END IF. ’empreport’. */ DECLARE pl_id ParamList. passing the parameter list */ Run_Product(REPORTS. END. IF Id_Null(pl_id) THEN Message(’Error creating parameter list ’||pl_name). DATA_PARAMETER. IF Id_Null(pl_id) THEN pl_id := Create_Parameter_List(pl_name). Example: /* ** Built–in: DELETE_PARAMETER ** Example: Remove the ’NUMBER_OF_COPIES’ parameter from the ** already existing ’TEMPDATA’ parameter list. */ DECLARE pl_id ParamList. and the record group named ** ’EMP_RECS’ in the form. END IF.DATA_PARAMETER.’EMP_QUERY’. END. Example: /* ** Built–in: ADD_PARAMETER ** Example: Add a value parameter to an existing Parameter ** List ’TEMPDATA’.’number_of_copies’. Example: /* ** Built–in: CREATE_PARAMETER_LIST ** Example: Create a parameter list named ’TEMPDATA’. /* ** Add a data parameter to this parameter list that will ** establish the relationship between the named query ** ’EMP_QUERY’ in the report.’EMP_RECS’). */ pl_id := Create_Parameter_List(’tmpdata’). Signal an error ** if the list already exists or if creating the ** list fails. END.’19’).TEXT_PARAMETER. pl_id. SYNCHRONOUS. /* ** Create the ’tmpdata’ parameter list afresh.
–– BATCH. The The The The The The Product to call name of the report definition communications mode Execution Mode Location of the reports document Handle to the parameter list –– –– –– –– –– Handle to the ParamList Name of Parameter in the Report Type of Parameter String Value for Parameter END. */ IF wc IS NOT NULL THEN Add_Parameter(pl. BEGIN pl_id := Get_Parameter_List(’tempdata’).’number_of_copies’). –– The Where Clause to Pass BEGIN /* ** Create a parameter list for parameter passing */ pl := Create_Parameter_List(’tmp’). END. –– ’rep0058.rdf’. wc ).Shik Mahamood Ali 26 */ BEGIN Delete_Parameter(’tempdata’. END IF. End. –– pl ). Example 2: PROCEDURE Run_Report_For_Last_Query IS pl ParamList. passing parameters in the ** parameter list. TEXT_PARAMETER. In this case the report definition has ** a parameter named ’the_Where_Clause’ that ** it’s expecting. /* ** If there is a Non–NULL Last Where clause to ** pass. /* ** Launch the report. . –– FILESYSTEM. ’the_Where_Clause’. */ Run_Product(REPORTS. –– SYNCHRONOUS. Example: /* ** Built–in: DESTROY_PARAMETER_LIST ** Example: Remove the parameter list ’tempdata’ after first ** checking to see if it exists */ DECLARE pl_id ParamList. add a text parameter to the parameter ** list to specify the parameter name and its ** value. 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. END IF. wc VARCHAR2(2000). –– /* Delete the parameter list */ Destroy_Parameter_List(pl).
COPY built-in Copies a value from one item or variable into another item or global variable.BLOCK_STATUS SYSTEM. .CURRENT_BLOCK s The value that the SYSTEM. 'Emp. Record.COORDINATION_OPERATION This system variable works with its companion SYSTEM. or the current data block during trigger processing. Destroy global variable System Variable 1. cur_val VARCHAR2(40).a’). Use the NAME_IN function to get the value of an item without referring to the item directly.System Variable It is used to track of runtime status condition. IF :emp. SYSTEM. COPY(NAME_IN(source).ename = 'smith' -.Local Variables The local variable is PL/SQL variable whose value is only accessible with in the trigger or user named sub Programs 2. and Block triggers).indirect reference 2. VARIABLES It is used to store values from form items.CURRENT_BLOCK system variable represents depends on the current navigation unit: If the current navigation unit is the block.CURRENT_BLOCK is the name of the block that Form Builder is processing or that the cursor is in. and on which master block of a master/detail relation. the value of SYSTEM. that the block contains only New records. record.Global Variable Whose value is accessible to trigger and subprograms in any modules – limit – 255 char length 3.Empno' ). The value can be one of three character strings: CHANGED NEW QUERY Indicates Indicates Indicates retrieved that the block contains at least one Changed record. Copy( cur_val.ename') = 'smith' -. SYSTEM.SYSTEM.NAME_IN The NAME_IN function returns the contents of an indicated variable or item. 1.Shik Mahamood Ali 27 Referencing Form Builder items indirectly 1.MASTER_BLOCK to help an OnClear-Details trigger determine what type of coordination-causing operation fired the trigger.BLOCK_STATUS represents the status of a Data block where the cursor is located.and PostItem. erase(‘global. 3. that the block contains only Valid records that have been from the database. destination).direct reference IF NAME_IN('emp. 2. or item (as in the Pre.
CURRENT_FORM represents the name of the form that Form Builder is executing. The value of SYSTEM.MODE indicates whether the form is in Normal.MASTER_BLOCK This system variable works with its companion SYSTEM.CURSOR_VALUE represents the value of the item where the cursor is located. 11.CURSOR_VALUE SYSTEM. The value is always a character string. SYSTEM. The value is always a character string.CURSOR_RECORD SYSTEM. The value can be one of three character strings: CHANGED Indicates that the form contains at least one block with a Changed record. item. SYSTEM. The value is a CHAR string in the following format: DD-MON-YYYY HH24:MM:SS 5. Indicates that the form contains only New records.CURSOR_ITEM SYSTEM. Indicates that a query is open.CURSOR_ITEM represents the name of the block and item. 7.FORM_STATUS represents the status of the current form.MODE s SYSTEM. The value is always a character string. SYSTEM.FORM_STATUS SYSTEM. The value is always a character string. the value of SYSTEM. block. This number represents the record's current physical order in the block's list of records.CURRENT_FORM SYSTEM.LAST_QUERY SYSTEM. The form contains at least one block with QUERY records and no blocks with CHANGED records. SYSTEM. SYSTEM.and Post-Form triggers). or Fetch Processing mode.CURRENT_DATETIME SYSTEM.FORM_STATUS becomes CHANGED only after at least one record in the form has been changed and the associated navigation unit has also changed. 6. 9. SYSTEM. The value is always a character string. NEW QUERY 10. SYSTEM. 4. Enter Query. 8.Details trigger determine what type of coordination-causing operation fired the trigger.Shik Mahamood Ali 28 If the current navigation unit is the form (as in the Pre.COORDINATION_OPERATION to help an On-Clear. 12.CURRENT_DATETIME is a variable representing the operating system date.CURSOR_RECORD represents the number of the record where the cursor is located.LAST_QUERY represents the query SELECT statement that Form Builder most recently used to populate a block during the current Runform session. . SYSTEM.CURRENT_BLOCK is NULL. The value is always a character string. and on which master block of a master/detail relation. where the input focus (cursor) is located. SYSTEM.
it represents the item where the cursor was located when the trigger began. meaning that a query is currently being processed. Indicates that the record's validation status is Changed and that the record does not exist in the database.TRIGGER_BLOCK SYSTEM. SYSTEM. 13.MOUSE_ITEM is :BLOCK2. The value is NULL if the current trigger is a Pre.RECORD_STATUS represents the status of the record where the cursor is located.TRIGGER_BLOCK represents the name of the block where the cursor was located when the current trigger initially fired.ITEM1. Indicates that the form is currently in Enter Query mode. PROPERTY CLASS This object is a named object that contains a list of properties and their associated settings.or Post-Form trigger. For example. Indicates that the form is currently in fetch processing mode.TRIGGER_ITEM represents the item (BLOCK. The Property Palette is where you set the properties of objects you create in form and menu modules. Indicates that the record's validation status is Valid and that it was retrieved from the database. 16.MOUSE_ITEM represents the name of that item as a CHAR value. SYSTEM. the value for SYSTEM. SYSTEM. The value can be one of four character strings: CHANGED INSERT NEW QUERY Indicates that a queried record's validation status is Changed. Indicates that the record's validation status is New.RECORD_STATUS SYSTEM. Property Window method Property class can not be change programmatically. if the mouse is in Item1 in Block2. SYSTEM. An object based on a property class can inherit the settings of any property in the class that is appropriate for that object. The value is always a character string. SYSTEM. Once you create a property class you can base other objects on it. 15. SYSTEM. 14. The value is always a character string.Shik Mahamood Ali NORMAL ENTER-QUERY QUERY 29 Indicates that the form is currently in normal processing mode. When referenced in a key trigger. There are 2 ways to creating property class a. then moves the mouse the platform is not a GUI platform.TRIGGER_ITEM SYSTEM.MOUSE_ITEM is NULL if: the mouse is not in an item the operator presses the left mouse button.MOUSE_ITEM If the mouse is in an item. b. Object Navigator method. VISUAL ATTRIBUTES .ITEM) in the scope for which the trigger is currently firing.
Visual attributes can include the following properties: Font properties: Font Name. White on Black It can be changed dynamically. 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. 3. including the type of object. and font settings. Font Weight Color and pattern properties: Foreground Color. Background Color Fill Pattern. Default Setting the Visual Attribute Group property to Default specifies that that the object should be displayed with default color. refer to the Form Builder documentation for your operating system. or when you want to specify custom editor attributes such as scroll bar and title. Visual attribute name is connected to an object by setting visual attribute name property Set_item_property(‘text1’.current_record_attribute. Font Size. and user-named editor. EDITOR This object enables the operator to edit text.’v1’). Font Width. You create a user-named editor when you want to display the editor programmatically with SHOW_EDITOR. When Visual Attribute Group is set to Default. they are custom VAT 3.Shik Mahamood Ali 30 Visual attributes are the font. Custom When the attribute of an objects are changed at design tome. Charmode Logical Attribute. 1. User-Named Editor A user-named editor has the same text editing functionality as the default editor. Font Style. pattern. Visual Attribute Types 1. much like styles in a word processing program. you can apply it to any object in the same module. System Editor The system editor to be used is defined by the FORMS60_EDITOR environment variable. There are three types of editor objects: default editor. 2. For information on environment variables and system editor availability. and the window manager. system editor. The actual settings are determined by a combination of factors. the individual attribute settings reflect the current system defaults. The editor specified must use the ASCII text format.EXE 2. and pattern properties that you set for form and menu objects that appear in your application's interface. FORMS60_EDITOR = C:\WINDOWS\NOTEPAD. color. Once you create a named visual attribute. Default Editor Default editor is invoked at runtime. A named visual attribute is a separate object in a form or menu module that defines a collection of visual attribute properties. the resource file in use. . 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.
14.X_POS).SYSTEM_EDITOR’). val. ed_id := Find_Editor( ed_name ). y.Shik Mahamood Ali 31 SHOW_EDITOR(editor_name. val VARCHAR2(32000). The EDIT_TEXTITEM procedure invokes the editor associated with the current text item in the form (the default editor. BEGIN itm_x_pos := Get_Item_Property(:System. 10. END. val. Pass the contents of the :emp.Cursor_Item. ed_name VARCHAR2(40). y. IF itm_x_pos > 40 THEN . or the current system editor).CHECKED) = ’TRUE’ THEN ed_name := ’system_editor’. SHOW_EDITOR takes message_in and message_out parameters that allow you to pass a text string in to the editor and to get the edited text string back when the operator accepts the editor. x. BEGIN mi_id := Find_Menu_Item(’PREFERENCES. result). ELSE ed_name := ’my_editor1’. Example: /* ** Built–in: SHOW_EDITOR ** Example: Accept input from the operator in a user–defined ** editor. height). ed_ok BOOLEAN.comments. END IF. END IF.comments := val.14) on the ** screen. 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. */ DECLARE ed_id Editor. width. ed_ok). Show_Editor( ed_id. The SHOW_EDITOR procedure displays a user-named editor at the specified display coordinates.comments item ** into the editor and reassign the edited contents if ** ’ed_ok’ returns boolean TRUE. message_in. mi_id MenuItem. IF Get_Menu_Item_Property(mi_id. a user-named editor. IF ed_ok THEN :emp. Edit_Textitem(x. Use the system editor if the user has ** checked the ”System_Editor” menu item under the ** ”Preferences” menu in our custom menu module. */ DECLARE itm_x_pos NUMBER. message_out. */ val := :emp. /* ** Show the appropriate editor at position (10.
and often are shown and hidden programmatically. 1.8). Stacked canvases obscure some part of the underlying content canvas. 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. 4.Shik Mahamood Ali ELSE END. HIDE_VIEW('a_stack'). property_false). and data retrieval is performed. While every new form automatically includes a default window named WINDOW1. and text items. This object represents a background entity on which you place interface items.Toolbar Canvas A toolbar canvas often is used to create toolbars for individual windows. There are four types of canvas objects: Content. Showing and hiding a canvas programmatically SHOW_VIEW('a_stack'). A single form can include any number of windows. A content canvas is the "base" view that occupies the entire content pane of the window in which it is displayed. tab canvases are displayed on top of a content canvas. Stacked. Dialog . You can create two types of toolbar canvases: horizontal or vertical. 2. 3. WINDOW A window is a container for all visual objects that make up a Form Builder application. You must define at least one content canvas for each window you create. including canvases. and Vertical Toolbar. while vertical toolbars are displayed along the far left edge of a window. property_true).20. CANVAS 32 Edit_TextItem(1. or SET_VIEW_PROPERTY('a_stack'. just under its menu bar.1. Like stacked canvases. END IF. visible. radio groups.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.Stacked Canvas A stacked canvas is displayed atop—or stacked on—the content canvas assigned to the current window.1. visible. Horizontal Toolbar. or SET_VIEW_PROPERTY('a_stack'. Horizontal toolbar canvases are displayed at the top of a window.8).20. partly obscuring it.Content Canvas The most common canvas type is the content canvas (the default type). You can display more than one stacked canvas in a window at the same time. Tab pages (that collectively comprise the tab canvas) each display a subset of the information displayed on the entire tab canvas. you can create additional windows as needed by inserting them under the Windows node in the Object Navigator. Edit_TextItem(60. such as check boxes.
REPLACE_CONTENT_VIEW built-in Replaces the content canvas currently displayed in the indicated window with a different content canvas. When-Window-Closed .Windows When-Window-Activated Window-Resized ALERT An alert is a modal window that displays a message notifying the operator of some application condition. When-Window-Deactivated . you can layer modeless windows so that they appear either in front of or behind other windows. Single Document Interface Although MDI is the default system of window management during Forms Runtime. . On most GUI platforms. MDI and SDI windows 1.'history'). REPLACE_CONTENT_VIEW (window_name VARCHAR2. Modal windows are often displayed with a platformspecific border unique to modal windows. Window Modality 1. Modeless Windows You can display multiple modeless windows at the same time. modal windows are "always-on-top" windows that cannot be layered behind modeless windows. 2. Hide on Exit property For a modeless window.Modal Windows Modal windows are usually used as dialogs. 2. */ BEGIN Replace_Content_View('employee_status'. When- . called the application window. view_name VARCHAR2). Use alerts to advise operators of unusual situations or to warn operators who are about to perform an action that might have undesirable or unexpected consequences. Form Builder also provides support for an SDI root window on Microsoft Windows. scroll. or iconify a modal window.Document windows always are displayed within the MDI application window frame. On some platforms. determines whether Form Builder hides the window automatically when the end user navigates to an item in another window. Multiple Document Interface MDI applications display a default parent window. containers typically used for modal dialogs that require immediate user interaction. Trigger . END. and have restricted functionality compared to modeless windows.Shik Mahamood Ali 33 Dialog Windows Dialog windows are free-floating. On some platforms. All other windows in the application are either document windows or dialog windows. and end users can navigate freely among them (provided your application logic allows it). ** Built-in: REPLACE_CONTENT_VIEW ** Example: Replace the 'salary' view with the 'history' ** view in the 'employee_status' window. end users cannot resize. for example.
Displays the given alert. Define the variable with a type of Alert. When the given alert is located. value VARCHAR2). VARCHAR2). and Note. al_button Number. SET_ALERT_PROPERTY (alert_id ALERT. Message severity is represented visually by a unique icon that displays in the alert window.property VARCHAR2. al_button := Show_Alert( al_id ). BEGIN al_id := Find_Alert('My_Error_Alert'). END. You must return the ID to an appropriately typed variable. Each style denotes a different level of message severity. 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. Searches the list of valid alerts in Form Builder. Changes the label on one of the buttons in an alert. property NUMBER. Changes the message text for an existing alert. and returns a numeric value when the operator selects one of three alert buttons. You define an object group when you want to package related objects for copying or sub classing in another module.button NUMBER. ID_NULL (Alert BOOLEAN). You define an object group when you want to package related objects so you can copy or subclass them in another module. the subprogram returns an alert ID. Caution. Returns a BOOLEAN value that indicates whether the object ID is available.Shik Mahamood Ali 34 There are three styles of alerts: Stop. ** Trigger: On-Error */ DECLARE err_txt VARCHAR2(80) := Error_Text. SET_ALERT_BUTTON_PROPERTY(alert_id ALERT. Set_Alert_Property(al_id. al_id Alert. ** Built-in: SET_ALERT_PROPERTY ** Example: Places the error message into a user-defined alert ** named 'My_Error_Alert' and displays the alert. FIND_ALERT (alert_name VARCHAR2). err_txt ). Using Object Groups • Blocks include: Items Item-level triggers Block-level triggers Relations • Object groups cannot include other object groups . message SHOW_ALERT (alert_id Alert). OBJECT GROUPS An object group is a container for a group of objects. You can use object groups to bundle numerous objects into higher-level building blocks that you can use again in another application. alert_message_text.
store. An object library can contain simple objects. Object libraries simplify the sharing of reusable components. Subclassing Subclassing is an object-oriented term that refers to the following capabilities: • Inheriting the characteristics of a base class (Inheritance) • Overriding properties of the base class (Specialization) OBJECT LIBRARY This object provides an easy method of reusing objects and enforcing standards across the entire development organization. and they support corporate. and program units. • Changes made to a copied object in the source module do not affect the copied object in the target module. They simplify reuse in complex environments. for a consistent look and feel • Reuse complex objects such as a Navigator Benefits of the Object Library • Simplifies the sharing and reuse of objects • Provides control and enforcement of standards • Eliminates the need to maintain multiple referenced forms SMARTCLASS . such as buttons and items. Reusing components enables you to: • Apply standards to simple objects. property classes. you can rapidly create applications by dragging and dropping predefined objects to your form. object groups.Shik Mahamood Ali 35 • Deleting: An object group does not affect the objects An object affects the object group Copying an Object Copying an object creates a separate. unique version of that object in the target module. by using Object Libraries. and personal standards. project. • • • • Is a convenient container of objects for reuse Simplifies reuse in complex environments Supports corporate. Objects can be used as standards (classes) for other objects. You can use the Object Library to create. and personal standards Simplifies the sharing of reusable components Object libraries are convenient containers of objects for reuse. project. maintain. Any objects owned by the copied object are also copied. Use copying to export the definition of an object to another module. and distribute standard and reusable objects. In addition. but they are protected against change in the library.
BEGIN SELECT ename INTO v_ename FROM emp WHERE empno = bind_value. or graphic modules Supports dynamic loading of program units FUNCTION locate_emp(bind_value IN NUMBER) RETURN VARCHAR2 IS v_ename VARCHAR2(15). If you frequently use certain objects as standards.PLX PL/SQL Library Module Binary PL/SQL Library Module Text PL/SQL Library Module Executable .Shik Mahamood Ali 36 A SmartClass is a special member of an Object Library. functions. A single library can contain many program units that can be shared among the Oracle Developer modules and applications that need to use them. report.MMT Menu Module Text . Reasons to share objects and code: Increased productivity Increased modularity Decreased maintenance Maintaining standards .MMX Menu Module Executable Form Builder Built-in Package . including procedures. Object Library members which are not SmartClasses can only be used to create new objects in form modules into which they are added. and alerts. RETURN(v_ename). and packages. it can be used to subclass existing objects in a form using the SmartClass option from the right mouse button popup menu. Unlike other Object Library members. END. you can mark them as SmartClasses by selecting each object in the object library and choosing Object—>SmartClass. such as standard buttons. date items. • Is an object in an object library that is frequently used as a class • Can be applied easily and rapidly to existing objects • Can be defined in many object libraries You can have many SmartClasses of a given object PL/SQL Libraries A library is a collection of PL/SQL program units.menu. You can mark many different objects that are spread across multiple object libraries as SmartClasses.PLL . A library: Is produced as a separate module and stored in either a file or the database Provides a convenient means of storing client-side code and sharing it among applications Means that a single copy of program units can be used by many form.PLD .MMB Menu Module Binary .
Shik Mahamood Ali
EXEC_SQL Provides built-ins for executing dynamic SQL within PL/SQL procedures
VBX Provides built-ins for controlling and interacting with VBX controls; this package works only in a 16-bit environment and is provided for backward compatibility WEB Provides built-ins for the Web environment OLE2 Provides a PL/SQL API for creating, manipulating, and accessing attributes of OLE2 automation objects SUBPROGRAM A subprogram can be either a procedure or a function. Built-in subprograms are therefore called in two distinct ways: • Built-in procedures: Called as a complete statement in a trigger or program unit with mandatory arguments. • Built-in functions: Called as part of a statement, in a trigger or program unit, at a position where the function’s return value will be used. Again, the function call must include any mandatory arguments. TRIGGER Triggers are blocks of PL/SQL code that are written to perform tasks when a specific event occurs within an application. In effect, a Form Builder trigger is an event-handler written in PL/SQL to augment (or occasionally replace) the default processing behavior. Every trigger has a name, and contains one or more PL/SQL statements. A trigger encapsulates PL/SQL code so that it can be associated with an event and executed and maintained as a distinct object.
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 Hierarchy property Specifies how the current trigger code should execute if there is a trigger with the same name defined at a higher level in the object hierarchy.
Shik Mahamood Ali The following settings are valid for this property:
Override Specifies that the current trigger fire instead of any trigger by the same name at any higher scope. This is known as "override parent" behavior. Before Specifies that the current trigger fire before firing the same trigger at the next-higher scope. This is known as "fire before parent" behavior. After Specifies that the current trigger fire after firing the same trigger at the next-higher scope. This is known as "fire after parent" behavior.
What are triggers used for?
Validate data entry Protect the database from operator errors Limit operator access to specified forms Display related field data by performing table lookups Compare values between fields in the form Calculate field values and display the results of those calculations Perform complex transactions, such as verifying totals Display customized error and information messages to the operator Alter default navigation Display alert boxes Create, initialize, and increment timers
Groups of triggers
When-triggers On-triggers Pre- and Post-triggers Key-trigger
Execute in addition to default processing Replace default processing Add processing before or after an event Change default processing assigned to a specific key
Trigger Categories Block-processing triggers o When-Create-Record o When-Clear-Block o When-Database-Record o When-Remove-Record
Shik Mahamood Ali Interface event triggers o When-Button-Pressed o When-Checkbox-Changed o When-Image-Activated o When-Image-Pressed o When-Radio-Changed o When-Timer-Expired o When –List-Changed o When –List-Activated o When –Tree-Note-Activated o When –Tree-Note-Expanded o When –Tree-Note-Selected o o o o o Key- [all] When-Window-Activated When-Window-Closed When-Window-Deactivated When-Window-Resized
Master-detail triggers o On-Check-Delete-Master o On-Clear-Details o On-Populate-Details Message-handling triggers o On-Error o On-Message Navigational triggers o Pre- and Post- Triggers o Pre-Form Pre-Block Pre-Record Pre-Text-Item Post-Text-Item Post-Record Post-Block Post-Form
When-New-Instance-Triggers When-New-Form-Instance When-New-Block-Instance When-New-Record-Instance When-New-Item-Instance
o o Pre-Query Post-Query
Shik Mahamood Ali Transactional triggers. o o o o o o o o o o o o o o o o o o o On-Count On-Delete. On-Insert. On-Lock. On-Logon. On-Logout. On-Select. On-Update. Post-Database-Commit. Post-Delete. Post-Forms-Commit. Post-Insert. Post – Select. Post-Update. Pre-Commit. Pre-Delete. Pre-Insert. Pre-Select. Pre-Update.
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
A. BLOCK-PROCESSING TRIGGERS Block processing triggers fire in response to events related to record management in a block.
removes all records from the block. This generally occurs only when the operator modifies the first item in a record. to set complex. An alternative is to use GET_RECORD_PROPERTY to obtain the record status. DECLARE CURSOR ship_dflt IS SELECT val FROM cust_pref WHERE Custid = :Customer. 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. but explicit cursor is more ** efficient.Ship_Method. calculated. the value of SYSTEM. stored in a preference table. For example. or navigates to the last record in a set while scrolling down. In a When-Clear-Block trigger. When-Clear-Block Perform an action whenever Form Builder flushes the current block. you might want to perform an automatic commit whenever this condition occurs.RECORD_STATUS is unreliable because there is no current record.Due_Date := SYSDATE + :Customer. Fires In • CREATE_RECORD WHEN-CREATE-RECORD TRIGGER This example assigns data-driven or calculated default values without marking the record as changed. The When-Clear-Block trigger does not fire when Form Builder clears the current block during the CLEAR_FORM event.Custid AND pref = 'SHIP'. FETCH ship_dflt INTO :Invoice. Used For • • Use a When-Clear-Block trigger to perform an action every time Form Builder flushes the current block.. */ :Invoice. or data-driven default values that must be specified at runtime. For example. 3. BEGIN /* ** Default Invoice Due Date based on Customer's ** Net Days Allowed value from the Customer block. CLOSE ship_dflt.. its value is always accurate. Fires In • • • CLEAR_BLOCK COUNT_QUERY ENTER_QUERY Clear_Block(No_Validate). 2. We could ** use SELECT. END.Net_Days_Allowed.INTO. */ OPEN ship_dflt.Shik Mahamood Ali 41 1. Used For • Perform an action whenever Form Builder attempts to create a new record in a block. and after the operator attempts to navigate out of the item. When-Database-Record Fires when Form Builder first marks a record as an insert or an update. when the operator presses the [Insert] key. For example. . that is. /* ** Default the shipping method based on this customers ** preference. Form Builder fires this trigger. Because GET_RECORD_PROPERTY requires reference to a specific record. rather than design time. When-Create-Record Fires when Form Builder creates a new record.
When-Remove-Record Fires whenever the operator or the application clears or deletes a record. or using the keyboard. or form level functionality. either with the mouse or through keyboard selection . For example. When-Button-Pressed Fires when an operator selects a button. such as When-Button-Pressed. END IF. Others. When-Checkbox-Changed Fires when an operator changes the state of a check box. */ IF :System. Perform an action whenever a record is cleared or deleted. END. by clicking with a mouse. This example executes a COMMIT_FORM if there are changes in the form. /* If the Form_Status is not back to 'QUERY' ** following a commit. fire only in response to operator input or manipulation. block.Form_Status = 'CHANGED' THEN Commit_Form. 4. either by clicking with the mouse.. BEGIN IF :System. to adjust a running total that is being calculated for all of the records displayed in a block. Some of these trigger. then the commit was not successful. Initiate an action when the operator toggles the state of a check box. 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.'). Fires In • • CLEAR_RECORD DELETE_RECORD B.. or for other item. like When-Window-Activated. END IF.Shik Mahamood Ali Used For • • 42 Perform an action whenever Form Builder changes a record's status to Insert or Update. Usage Notes • Use a When-Button-Pressed trigger to perform navigation. RAISE Form_Trigger_Failure. 2. can fire in response to both operator input and programmatic control. to calculate text item values.Form_Status <> 'QUERY' THEN Message('Unable to commit order to database.INTERFACE EVENT TRIGGERS Interface event triggers fire in response to events that occur in the form interface. 1. or using the keyboard.
Thus. So for all navigation triggers that fire before the When-Checkbox-Changed trigger.Update_allowed’. the value of the check box item remains as it was before the operator navigated to it. then the Date_Shipped item is enabled. 4. End. the When-Checkbox-Changed trigger is the first trigger to register the changed value of a check box item. End if. The above When_Image_Pressed trigger on the stimage item displays a image of the current student (in the stmast block) when the user clicks the image item. Begin If checkbox_checked(‘s_ord.Shik Mahamood Ali Usage Notes • 43 Use a When-Checkbox-Changed trigger to initiate a task dependent upon the state of a check box.JPG’. End. When-Image-Pressed Initiate an action whenever an operator clicks on an image item. .property_true). the internal value of that item does not change until navigation is completed successfully.filled’) then Set_Item_Property(‘s_ord. Begin READ_IMAGE_FILE(‘ST_’||TO_CHAR(:STMAST. • When an operator clicks in a check box. 3. 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. Else Set_Item_Property(‘s_ord. Double-click on an image item.date_shipped’.order_filled item prevents the date_shipped item from being updated if the user marks the order as filled ( checked on ). When-Image-Activated Initiate an action whenever the operator double-clicks an image item. Usage Notes • Use a When-Image-Pressed trigger to perform an action when an operator clicks or double clicks on an image item. When-Checkbox-Changed Trigger examples This trigger on the :S_ord.date_shipped’. Fires when an operator uses the mouse to: • Single-click on an image item.’STMAST:STIMAGE’).Update_allowed’.STID)||’.property_false).’JPG’. Note : That When-Image-Pressed also fires on a double-click.If the check box is set off.
or if the end user causes a procedure to be invoked which changes the value. then the payment type is set to cash. When no_data_found then Message(‘Invalid Student ‘). Declare . this trigger immediately confirms whether the customer has a good or excellent credit rating. or using the keyboard. Begin Exception End. For all navigation triggers that fire before the When-Radio-Changed trigger. For example. When-Radio-Changed Description A fire when an operator selects a different radio button in a radio group.) When an operator clicks an item in a radio group. or de-selects the currently selected radio button. The display style of a list item is determined by the List Style property. The When-List-Changed trigger is not fired if the value of the list is changed programmatically such as by using the DUPLICATE_ITEM built-in. When-List-Activated Trigger Fires when an operator double-clicks on an element in a list item that is displayed as a T-list. Select stname into :stname from the stmast where stid=:stid.Shik Mahamood Ali 44 5. either by clicking with the mouse. the When-List.Changed trigger will not fire if an end user duplicates the item using a key mapped to the DUPLICATE_ITEM built-in. not for dropdown lists or combo box style list items. 6. Thus. Usage Notes • A When-List-Activated trigger fires only for T-list style list items. • When-Radio-Changed Trigger examples When the user selects credit as the payment type for an order. if a When-List-Changed trigger is attached to a combo box style list item. 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. Populate student name based on the selected student id. In addition. Initiate an action when an operator changes the current radio button selected in a radio group item. Usage Notes • Use a When-Radio-Changed trigger to perform an action depending on the state of a radio group. the value of the radio group remains as it was before the operator navigated to it. If not. it fires each time the end user enters or modifies entered text. the When-Radio-Changed trigger is the first trigger to register the changed value of a radio group. the internal value of that item does not change until navigation is completed successfully. (De-selecting a radio button in a radio group sets the radio group value to NULL. When-List-Changed Trigger Description Fires when an end user selects a different element in a list item or de-selects the currently selected element. 7. operators use this technique in Enter Query mode to exclude a radio group from a query.
8. End if. Initiate an action when a programmatic timer expires. msg_3 VARCHAR2(80) := 'Ask for the order or repeat the close.payment_type=’CREDIT’ then Select credit_rate into v_credit from customer where custid=:s_ord. msg_2 VARCHAR2(80) := 'Move into your close. Usage Notes Timers are created programmatically by calling the CREATE_TIMER built-in procedure. If v_credit NOT_IN(‘GOOD’.timer_count = 1 THEN .'.custid. BEGIN :GLOBAL. in which sales calls are timed. End.timer_count := 1 BEGIN timer_id := FIND_TIMER('tele_timer'). msg_1 VARCHAR2(80) := 'Wrap up the first phase of your presentation'. The message box is displayed each time a repeating timer expires. message(‘Warning – Customer must pay cash‘). and message boxes are displayed to prompt the salesperson through each stage of the call. update item values. alert_id := FIND_ALERT('tele_alert'). • • Fires In • Process Expired Timer When-Timer-Expired Trigger examples Example The following example displays a message box each time a repeating timer expires. one_and_half NUMBER(5) := (90 * 1000).’EXCELLENT’) then :s_ord. alert_id ALERT. or transaction processing. or perform any task that should occur after a specified interval.' two_minutes NUMBER(6) := (120 * 1000). Begin If :s_ord. Use a When-Timer-Expired trigger to initiate an event. IF :GLOBAL. navigation. End if. • The When-Timer-Expired trigger can not fire during trigger. DECLARE timer_id TIMER. You can call GET_APPLICATION_PROPERTY(TIMER_NAME) in a When-Timer-Expired trigger to determine the name of the most recently expired timer.payment_type:=’CASH’. When-Timer-Expired Description Fires when a timer expires.Shik Mahamood Ali 45 v_credit customer.credit_rate%type. call_status NUMBER. The following example is from a telemarketing application.
Usage Notes: Use this trigger to perform the following types of tasks: . Thus. call_status := Show_Alert(alert_id). Fires when a window is made the active window. ELSIF call_status = ALERT_BUTTON2 THEN :GLOBAL. Note that on some window managers. :GLOBAL. NO_CHANGE). two_minutes.timer_count = 2 THEN Change_Alert_Message(alert_id. a window can be activated by. NO_CHANGE. ELSIF call_status = ALERT_BUTTON2 THEN :GLOBAL. navigating to an item in a different window always activates that window. END IF. This operation is independent of navigation to an item in the window. ELSE Change_Alert_Message(alert_id. NO_REPEAT).timer_count := 0. This occurs at form startup and whenever a different window is given focus. NO_CHANGE). call_status := Show_Alert(alert_id). one_and_half. but window activation can also occur independently of navigation. msg_3). call_status := Show_Alert(alert_id). END IF.timer_count := 0. ELSE Set_Timer(timer_id.timer_count := 0. IF call_status = ALERT_BUTTON1 THEN Delete_Timer(timer_id). say. ELSIF call_status = ALERT_BUTTON2 THEN :GLOBAL. msg_2). Next_Record. Next_Record. END IF.Shik Mahamood Ali 46 Set_Alert_Property(alert_id. Next_Record. ALERT_MESSAGE_TEXT. ELSE Set_Timer(timer_id. When-Window-Activated Initiate an action whenever an operator or the application activates a window. IF call_status = ALERT_BUTTON1 THEN Delete_Timer(timer_id). IF call_status = ALERT_BUTTON1 THEN Delete_Timer(timer_id). ELSE Set_Timer(timer_id. END. clicking on its title bar. msg_1). 9.timer_count = 2. END IF. ELSIF :GLOBAL.
Fires when a window is resized. 12. Example: Begin GET_WINDOW_PROPERTY( window_name. 11.When-Window-Closed Initiate an action whenever an operator closes a window with the window manager's Close command. End. PROPERTY_OFF). property). resizing the window programmatically fires the When–Window–Resized trigger. by way of the GET_WINDOW_PROPERTY built–in. VISIBLE. When-Window-Deactivated Initiate an action whenever a window is deactivated as a result of another window becoming the active window.) This trigger also fires at form startup. Set input focus in an item on the target window. • Keep track of the most recently fired window trigger by assigning the value from SYSTEM. when the root window is first drawn. either by the operator or programmatically through a call to RESIZE_WINDOW or SET_WINDOW_PROPERTY. Usage Notes: • Use this trigger to programmatically close a window when the operator issues the window–manager Close command. Audit the actions of an operator. 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. either by the operator or programmatically. • You can hide the window that contains the current item. • You can close a window with the HIDE_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’.Shik Mahamood Ali 47 • Capture initial settings of window properties. such as width. or y coordinate. x coordinate.EVENT_WINDOW to a variable or global variable. When-Window-Resized Initiate an action whenever a window is resized. It does not fire when a window is iconified. (Even if the window is not currently displayed. • Enforce navigation to a particular item whenever a window is activated. . SET_WINDOW_PROPERTY. 10 . and EXIT_FORM built–in subprograms. height. 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.
the trigger fires when operator presses a specific key or key-sequence. */ wn_id1 := Find_Window(Window1). w := Get_Window_Property(wn_id1.WIDTH). Example: /* ** Built–in: RESIZE_WINDOW ** Example: Set Window2 to be the same size as Window1 */ PROCEDURE Make_Same_Size_Win( Window1 VARCHAR2. h NUMBER. w NUMBER.Shik Mahamood Ali 48 • Maintain certain visual standards by resetting window size if the window was improperly resized.[ALL] ( KEY TRIGGERS ) Key Triggers have a one-to-one relationship with specific keys. w. Key Triggers and Function Keys KEY TRIGGER Key–CLRBLK Key–CLRFRM Key–CLRREC Key–COMMIT Key–CQUERY Key–CREREC Key–DELREC Key–DOWN Key–DUP–ITEM Key–DUPREC Key–EDIT Key–ENTQRY Key–EXEQRY Key–EXIT Key–HELP Key–LISTVAL Key–MENU Key–NXTBLK Key–NXT–ITEM Key–NXTKEY Key–NXTREC Key–NXTSET Key–PRINT Key–PRVBLK Key–PRV–ITEM Key–PRVREC Key–SCRDOWN Key–SCRUP ASSOCIATED FUNCTION KEY [Clear Block] [Clear Form] [Clear Record] [Accept] [Count Query Hits] [Insert Record] [Delete Record] [Down] [Duplicate Item] [Duplicate Record] [Edit] [Enter Query] [Execute Query] [Exit] [Help] [List of Values] [Block Menu] [Next Block] [Next Item] [Next Primary Key] [Next Record] [Next Set of Records] [Print] [Previous Block] [Previous Item] [Previous Record] [Scroll Down] [Scroll Up] . i. /* ** Resize Window2 to the same size */ Resize_Window( Window2. h := Get_Window_Property(wn_id1. h ).e. KEY. For example. Window2 VARCHAR2) IS wn_id1 Window. BEGIN /* ** Find Window1 and get it’s width and height. you can define a Key-EXIT trigger to replace the default functionality of the [Help] key.HEIGHT). Replace the default function associated with a function key. C. END.
however. END IF. Specifically. Key–Others Trigger A Key–Others trigger fires when an operator presses the associated key. The default master/detail triggers enforce coordination between records in a detail block and the master record in a master block. ELSE POST. 1. ’Do you really want to leave the form?’). Before you can attach key triggers to these keys. KEY-COMMIT TRIGGER AT FORM LEVEL: EMPLOYEES FORM BEGIN IF GET_APPLICATION_PROPERTY( CALLING_FORM ) IS NULL THEN COMMIT_FORM. Usage Notes: Use Key–Others triggers to limit an operator’s possible actions. You can attach Key–Fn triggers to 10 keys or key sequences that normally do not perform any Oracle Forms operations. Usage Notes: Use Key–Fn triggers to create additional function keys for custom functions. D. KEY-DELREC TRIGGER ON S_CUSTOMER BLOCK DELETE_RECORD. ALERT_MESSAGE_TEXT. use Key–Others triggers to perform the following tasks: • Disable all keys that are not relevant in a particular situation. KEY-EXIT AT FORM LEVEL SET_ALERT_PROPERTY (’question_alert’.Shik Mahamood Ali Key–UP Key–UPDREC 49 [Up] Equivalent to Record. Oracle Forms still displays the function key’s default entry in the Show Keys screen. 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. IF SHOW_ALERT (’question_alert’) = ALERT_BUTTON1 THEN EXIT_FORM.Key–Fn Trigger A Key–Fn trigger fires when an operator presses the associated key. • Perform one specific action whenever an operator presses any key. When this occurs.MASTER-DETAIL TRIGGERS Form Builder generates master/detail triggers automatically when a master/detail relation is defined between blocks. A Key–Others trigger overrides the default behavior of a Runform function key (unless one of the following restrictions apply). END IF. Lock command on the default menu 1. These keys are referred to as Key–F0 through Key–F9. 2. 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). . you or the DBA must use Oracle Terminal to map the keys to the appropriate functions. END.
MESSAGE-HANDLING TRIGGERS Form Builder automatically issues appropriate error and informational messages in response to runtime events. ERROR_TYPE. • When Immediate coordination is set. RAISE Form_Trigger_Failure. E. DBMS_ERROR_TEXT. ERROR_TEXT. In most cases. you can call the SET_BLOCK_PROPERTY(COORDINATION_STATUS) built–in. this causes the details of the instantiated master to be populated immediately. or DBMS_ERROR_CODE built–in function in an On–Error trigger to identify a specific error condition. END IF. Usage Notes: Oracle Forms creates the On–Clear–Details trigger automatically when you define a master– detail block relation.Shik Mahamood Ali 50 DECLARE the_sum NUMBER.’). BEGIN SELECT SUM(dollar_amt) INTO the_sum FROM po_distribution WHERE po_number = :purchase_order. 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. On–Error triggers should be attached to the form. END. Oracle Forms marks the blocks as needing to be coordinated. • When Deferred coordination is set and this trigger fires. Message handling triggers fire in response to these default messaging events. On-Clear-Details Fires when Form Builder needs to clear records in a block that is a detail block in a master/detail relation because those records no longer correspond to the current record in the master block. 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.total THEN Message(’PO Distributions do not reconcile. 3. Usage Notes Use an On–Error trigger for the following purposes: • • To trap and recover from an error To replace a standard error message with a custom message Use the ERROR_CODE. 2. Immediate coordination is the default. • Example: . 1. IF the_sum <> :purchase_order. On-Error Replace a default error message with a custom error message.number. Trapping certain errors at the block or item level can be difficult if these errors occur while Oracle Forms is performing internal navigation. such as during a Commit process. or to trap and recover from an error. rather than to a block or item.
for example. END. DECLARE lv_errcod NUMBER := ERROR_CODE. lv_errtxt VARCHAR2(80) := ERROR_TEXT.Shik Mahamood Ali 51 The following example checks specific error message codes and responds appropriately. lv_errtyp VARCHAR2(3) := ERROR_TYPE.. to replace a default message issued by Form Builder with a custom message. lv_errcod NUMBER := MESSAGE_CODE. Usage Notes: Use an On–Message trigger for the following purposes: • To trap and respond to an informative message • To replace a standard informative message with a custom message • To exclude an inappropriate message Example: The following example responds to an error message by displaying an alert that gives the user a message and gives the user the choice to continue or to stop: DECLARE alert_button NUMBER. END IF.. On-Message To trap and respond to a message. 2. lv_errtxt VARCHAR2(80) := MESSAGE_TEXT. lv_errtype VARCHAR2(3) := MESSAGE_TYPE. RAISE Form_Trigger_Failure.. ELSE . BEGIN IF lv_errcod = 40350 THEN alert_button := Show_Alert(’continue_alert’)... IF alert_button = ALERT_BUTTON1 THEN .. ELSIF (lv_errcod = 40zzz) THEN ** More tasks here */ ELSE Message(lv_errtyp||’–’||to_char(lv_errcod)||’: ’||lv_errtxt). ELSE Message(lv_errtyp||’–’||to_char(lv_errcod)||’: ’||lv_errtxt). END. RAISE Form_Trigger_Failure. END IF. . END IF. BEGIN IF (lv_errcod = 40nnn) THEN /* ** Perform some tasks here */ ELSIF (lv_errcod = 40mmm) THEN /* ** More tasks here */ .
or Date Shipped. 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). [ Set the initial value property to “Y”. This prevents attempts at very large queries.lineitem_count FROM S_ITEM WHERE ord_id = :S_ORD.id. Use it to check or modify query conditions. 2. This Pre-Query trigger on the S_ORD block only permits queries if there is a restriction on either the Order ID. Post-Query Perform an action after fetching a record.Shik Mahamood Ali F. Date Ordered. Post-Query fires for each record that is fetched into the block as a result of a query. such as looking up values in other tables based on a value in the current record. 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.name:=’%’||:S_customer. 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. . END IF. and displays this number as a summary value in the non base table item :Lineitem_count. B] [ exact_match – Check Box User can specify if or not a query condition for a customer name should exactly match the table value.QUERY-TIME TRIGGERS 52 Query-time triggers fire just before and just after the operator or the application executes a query in a block. This trigger is defined at block level or above. • To test the operator’s query conditions.’Y’)=’N’ then :S_Customer. 1. Begin End.exact_match. Fires once for each record fetched into the block.name || ‘%’. RAISE Form_Trigger_Failure. Make sure the user has given one of the two Columns which we have indexed in their search criteria. This Post-Query trigger on the S_ORD block selects the total count of line items for the current Order. SELECT COUNT(ord_id) INTO :S_ORD. otherwise fail the query with a helpful message A] IF :Employee. just before sending the SELECT statement to the database. Pre-Query Validate the current query criteria or provide additional query criteria programmatically.Ename IS NULL AND :Employee.’). Use it to perform calculations and populate additional items.Mgr IS NULL THEN Message(’Supply Employee Name and/or Manager Id ’||’for Query. ] IF nvl(:control.
For instance. A Post-Query trigger fires as each record is fetched (except array processing). FETCH lookup_payplan INTO :Employee.AND POST. for display in non–database items in the current block. CLOSE lookup_area. I ] PRE. 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. /* ** Lookup Area Descript given the Zipcode in ** the Employee Record just fetched. BEGIN /* Lookup the Payment Plan Description given the Payplan_Id in the Employee Record just fetched. END. A query fetched 10 records How many times does a PRE-QUERY Trigger and POST-QUERY Trigger will get executed? PRE-QUERY fires once.Area_Desc_Nondb. when the operator clicks on a text item in another block.Shik Mahamood Ali 53 Example: This example retrieves descriptions for code fields. Use it to perform calculations and populate additional items.*/ OPEN lookup_payplan.NAVIGATIONAL TRIGGERS Navigational triggers fire in response to navigational events.Payplan_Desc_Nondb. . but before the statement is actually issued.TRIGGERS Fire as Form Builder navigates internally through different levels of the object hierarchy. */ OPEN lookup_area. Pre-query trigger fires before pre-select trigger. Use it to check or modify query conditions. ** Use Explicit Cursor for highest efficiency. FETCH lookup_area INTO :Employee. navigational events occur as Form Builder moves the input focus from the current item to the target item.Zip. The pre-query trigger fires just before oracle forms issues the select statement to the database after the operator as define the example records by entering the query criteria in enter query mode. Use Explicit ** Cursor for highest efficiency. • • A Pre-Query trigger fires before a query executes. CLOSE lookup_payplan.Payplan_Id. DECLARE CURSOR lookup_payplan IS SELECT Payplan_Desc FROM Payplan WHERE Payplan_Id = :Employee. G. CURSOR lookup_area IS SELECT Area_Name FROM Zip_Code WHERE Zip = :Employee. POST-QUERY fires 10 times.
For instance. if the validation unit is Record.and Post-Navigation Triggers Fire? The Pre.navigation triggers do not fire if they belong to a unit that is smaller than the current validation unit. . Pre. such as at form startup. Example The Pre-Text-Item trigger fires just before entering a text item. To the user. 1.and Post. the input focus returns to its initial location (where it was prior to the trigger firing).navigation triggers fire during navigation.and Post. When Do Navigation Triggers Not Fire? The Pre.and Post-Text-Item triggers do not fire. it appears that the input focus has not moved at all.Shik Mahamood Ali 54 When Do Pre. IF not (DBMS_SESSION. that is just before entry to or just after exit from the object specified as part of the trigger name. Pre-Form Perform an action just before Form Builder navigates to the form from "outside" the form. What Happens When a Navigation Trigger Fails? If a Pre.IS_ROLE_ENABLED(’ADMINISTRATIVE’) or (DBMS_SESSION.or Post navigation trigger fails.IS_ROLE_ENABLED(’TECHNICAL’) THEN MESSAGE(’You are not authorized to run this application’).
property_false). Pre-Text-Item Perform an action before Form Builder navigates to a text item from the record level. during navigation from one block to another. 55 2. The following trigger prevents the user from entering a new record given some dynamic condition and the status of SYSTEM. Usage Notes: . Pre-Block Perform an action before Form Builder navigates to the block level from the form level. enabled. 3. Record the current value of the text item for future reference. Fires during the Enter the Block process. Pre-Record Perform an action before Form Builder navigates to the record level from the block level. SET_ITEM_PROPERTY(’CONTROL. RAISE form_trigger_failure. IF (( dynamic–condition) AND :System.RECORD_STATUS evaluating to NEW.stock_button’. Usage Notes: • Fires during the Enter the Record process.Record_Status = ’NEW’) THEN RAISE Form_Trigger_Failure. END IF. Post-Form Perform an action before Form Builder navigates to "outside" the form. • Use a Pre–Record trigger to keep a running total. 5. 4. such as when exiting the form. END IF. Usage Notes: Use a Pre–Block trigger to: • Allow or disallow access to a block • Set variable values Disabling stock_button when leaving CONTROL block: begin End. Fires during the Leave the Form process. based on other items previously entered into the same record. and • store that value in a global variable or form parameter. during navigation to a different record.Shik Mahamood Ali PAUSE. when a form is exited. Usage Notes: Use a Pre–Text–Item trigger to perform the following types of tasks: • Derive a complex default value.
Example . For example. for example. Usage Notes: • • Use a Post–Block trigger to validate the block’s current record. NEXT_BLOCK. cur_blk VARCHAR2(80) := :System. BEGIN lst_itm := cur_blk||’. Example: /* ** Built–in: NEXT_RECORD ** Example: If the current item is the last item in the ** block. enabled. including INSERT_RECORD. The Leave the Record process can occur as a result of numerous operations. DELETE_RECORD. if you want to set a visual attribute for an item as the operator scrolls down through a set of records. Post-Record Manipulate a record when Form Builder leaves a record and navigates to the block level. 7.Shik Mahamood Ali 56 You can use a Post–Form trigger for the following tasks: • To clean up the form before exiting.Cursor_Item.’||Get_Block_Property(cur_blk. 6.Cursor_Block.cmdsave’. the Post–Record trigger fires whenever the operator or the application moves the input focus from one record to another. use a Post–Form trigger to erase any global variables that the form no longer requires. etc. property_false).LAST_ITEM). the record that had input focus when the Leave the Block event occurred. Post-Block Manipulate the current record when Form Builder leaves a block and navigates to the form level. that is. Specifically. lst_itm VARCHAR2(80). ELSE Next_Item. PREVIOUS_BLOCK. IF cur_itm = lst_itm THEN Next_Record. you can do so from within this trigger. You might also use this trigger to test a condition and prevent the user from leaving a block based on that condition. For example. Fires during the Leave the Record process. if validation fails in the form. CREATE_RECORD. Set_item_property (‘control. • To display a message to the operator upon form exit. NEXT_RECORD. 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. 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. This trigger does not fire when the form is exited abnormally.
by including the following code in your When-New-Form-Instance trigger: 1a. DEFAULT_WHERE. When-New-Form-Instance Perform an action at form start-up.where_cls). 1b. :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. WIDTH).height_win_inventory := GET_WINDOW_PROPERTY(’win_inventory’. Fires during the Leave the Item process for a text item. Specifically. When-New-Form-Instance Trigger at Form Level . END. EXECUTE_QUERY. :GLOBAL. when the form returns to a quiet state to wait for operator input. ’'GLOBAL. these triggers fire just after Form Builder moves the input focus to a different item. BEGIN DEFAULT_VALUE(’’. 1d. When Do When-New. when the ORDERS form is run.where_cls’). Specifically. :GLOBAL. Post-Text-Item Manipulate an item when Form Builder leaves a text item and navigates to the record level. 57 8. 1. END.WIDTH). :GLOBAL. BEGIN EXECUTE_QUERY. II] WHEN-NEW-INSTANCE-TRIGGERS Fire at the end of a navigational sequence that places the input focus on a different item. Perform a query of all orders. (Occurs after the Pre-Form trigger fires).Shik Mahamood Ali END IF. END.width_win_order := GET_WINDOW_PROPERTY(’win_order’. Example The When-New-Item-Instance trigger fires immediately after navigation to a new instance of an item. EXECUTE_QUERY.:GLOBAL.HEIGHT).width_win_inventory := GET_WINDOW_PROPERTY(’win_inventory’.HEIGHT). 1c.height_win_order := GET_WINDOW_PROPERTY(’win_order’. this trigger fires when the input focus moves from a text item to any other item. SET_BLOCK_PROPERTY(’prod_lov_blk’.
When-New-Record-Instance Perform an action immediately after the input focus moves to an item in a different record. WINDOW_STATE. DECLARE htree ITEM. when an operator presses [Down] to scroll through a set of records. If the new record is in a different block.DELETE_ALLOWED. The example locates the hierarchical tree first. ’Summit Sporting Goods Application’). Oracle Forms fires this trigger each time the input focus moves to the next record. v_ignore NUMBER. Example The following example of a When-New-Block-Instance trigger conditionally sets the DELETE ALLOWED property to FALSE. rg_emps). Example The Cursor arrives in each record of the S_Item block. fires after the When-New-Block-Instance trigger. TITLE. NULL.Shik Mahamood Ali 58 BEGIN SET_WINDOW_PROPERTY( forms_mdi_window. Example This code could be used in a WHEN-NEW-FORM-INSTANCE trigger to initially populate the hierarchical tree with data. PROPERTY_FALSE). to_char(empno) ’ ||' from emp ' ||'connect by prior empno = mgr ' ||’start with job = ’’PRESIDENT’’’). Ftree. v_ignore := Populate_Group(rg_emps). rg_emps := Create_Group_From_Query('rg_emps'. For example. Usage Notes: Use a When–New–Record–Instance trigger to perform an action every time Oracle Forms instantiates a new record.Set_Tree_Property(htree. END IF.RECORD_GROUP. each time Oracle Forms instantiates a new record in the block. BEGIN htree := Find_Item('tree_block. but before the When-New-Item-Instance trigger. IF GET_APPLICATION_PROPERTY(username) = ’SCOTT’ THEN SET_BLOCK_PROPERTY(’S_ITEM’. Usage Notes: Use a When–New–Block–Instance trigger to perform an action every time Oracle Forms instantiates a new block. SET_WINDOW_PROPERTY( forms_mdi_window. level. 3. 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. a record group is created and the hierarchical tree is populated. rg_emps RECORDGROUP.htree3'). Ftree. ename. in other words. END. if one exists . MAXIMIZE ). Then. and populates the product_image item with a picture of the products. END. 2.’select 1.
Empno IS NOT NULL THEN . Perform an action immediately after the input focus moves to a different item.mode = 'ENTER-QUERY') THEN Exit_Form.Shik Mahamood Ali 59 1] Declare Filename varchar2(20). If Filename= ‘ No file’ then Null. 2] Built–in: CLEAR_ITEM .UPDATE_ALLOWED. :global.date_shipped’).’DD’) <> ’01’ THEN Clear_Item. Call_Form(’clerk_timesheet’). End if End.Job = ’CLERK’ THEN Break. The When-New-Item-Instance trigger is especially useful for calling restricted (navigational) built-ins.product_image’). fires after the When-New-Block-Instance trigger.When-New-Item-Instance Fires when the input focus moves to an item.] BEGIN IF (:global.order_filled’)THEN SET_ITEM_PROPERTY(’S_ORD. Begin Filename:=get_product_image(:S_ITEM.Example: Clear the current item if it does not represent ** the first day of a month.*/ BEGIN IF :Emp. END IF. 1] IF CHECKBOX_CHECKED(’S_ORD.a Example: Brings up the debugging window for a particular ** value of the ’JOB’ item anytime the user changes records. 3]. If the new item is in a different block. when Form Builder is ready to accept input in an item that is different than the item that previously had input focus. 2] 1. END IF. END. Specifically.date_shipped’. BEGIN IF TO_CHAR(:Emp. BEGIN IF :Emp. 3. it fires after navigation to an item. GO_ITEM(’S_ORD.’S_ITEM. property_true). Usage Notes Use a When-New-Item-Instance trigger to perform an action whenever an item gets input focus. Break. Else Read_Image_File(filename. 4. END. END IF.PRODUCT_ID). Message(’This date must be of the form 01–MON–YY’).cancel_query = 'Y' and :system. END.Hiredate.cancel_query = 'N'. END IF.’tiff’.
then all records in the form are validated. If an item has been changed and is not yet marked as valid. Validation occurs at item. End if. H.Range (Lowest-Highest Allowed Value) . such as a Commit operation. then Form Builder first performs standard validation checks to ensure that the value conforms to the item’s properties. For example.Cursor_Item = ’EMP. then control is passed back to the appropriate level. then the status of each item in the record is checked. END IF. or default processing. it is set to valid.Employee_Id := :Emp.EMPNO’ and :System. If validation fails. 4]. then is the item null?) . END IF.Shik Mahamood Ali 60 :Global.Data type .Format mask . 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. Standard checks include the following: . When the record passes these checks. if you commit (save) changes in the form.Mode = ’ENTER–QUERY’ IF NOT Show_Lov(’my_lov’) THEN RAISE Form_Trigger_Failure. and a When-Validate-Record trigger is then fired. • 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. Validation occurs at: • Item level: Form Builder records a status for each item to determine whether it is currently valid. Clear_Block(No_Validate). END. so that the operator can make corrections. if present. record. programmatic control. Form Builder checks to see whether the record is valid. The following trigger accomplishes that operation. If not. • Block and form level: At block or form level. and form levels.Required (if so. Form Builder performs validation checks during navigation that occurs in response to operator input.Validate from List (see later in this lesson) • Record level: After leaving a record. These checks are carried out before firing any When-Validate-Item triggers that you have defined. all records below that level are validated. END. When Does Validation Occur? Form Builder carries out validation for the validation unit under the following conditions: . BEGIN THEN IF :System. block. VALIDATION TRIGGERS Validation triggers fire when Form Builder validates data in an item or record. unless you have suppressed this action.Empno.
• The Defer_Required_Enforcement property postpones enforcement of the Required property from item validation to record validation. This includes when changes are committed. At validation time. Example . Form Builder then automatically uses the item value as a non case-sensitive search string on the LOV contents. The trigger fires after standard item validation. Form Builder marks the changed item as Valid and does not re-validate it. When an item has the Required property set to Yes. but is a partial value of the LOV value. • If no match is found. the LOV is not displayed. depending on the circumstances: • If the value in the text item matches one of the values in the first column of the LOV. so that the operator must choose. Do this by setting the Validate from List property to Yes for the item. and processing continues normally. When-Validate-Item Trigger You have already used this trigger to add item-level validation. • It is possible to write a When-Validate-Item trigger that changes the value of an item that Form Builder is validating. by default Form Builder will not allow navigation out of the item until a valid value is entered. it fires as the last part of item validation for items with the New or Changed validation status. Using LOVs for Validation When you attach an LOV to a text item by setting the LOV property of the item. While this behavior is necessary to avoid validation loops. If validation succeeds. block. Form Builder displays the LOV and uses the text item value as the search criteria to automatically reduce the list. and input focus is returned to the item if the trigger fails. validation succeeds. • If the item value causes multiple records to be found in the LOV. it does make it possible for your application to commit an invalid value to the database. The item then passes this validation phase. you can optionally use the LOV contents to validate data entered in the item. When – Validate -Item Fires during the Validate the Item process. Usage Notes • Use a When-Validate-Item trigger to supplement Form Builder default item validation processing. Validation Triggers • Item level When-Validate-Item • Block level When-Validate-Record 1.Shik Mahamood Ali 61 • The [Enter] key is (ENTER command is not necessary mapped to the key that is physically labeled Enter) pressed or the ENTER built-in procedure is run (whose purpose is to force validation immediately). then the full LOV contents are displayed to the operator. The validation unit is discussed in the next section. The default validation unit is item. Setting the Defer_Required_Enforcement property to Yes allows the operator to move freely among the items in the record. • If the item’s value causes a single record to be found in the LOV. • The operator or a trigger navigates out of the validation unit. or form by the designer. then the full LOV column value is returned to the item (providing that the item is defined as the return item in the LOV). Specifically. but can also be set to record. The following events then occur.
RAISE Form_Trigger_Failure.Shik Mahamood Ali 62 The SELECT. Duplicate entries in COMMPLAN table!'). when the operator has left a new or changed record. it's more convenient to check the combination of them once at the record level. If validation succeeds. the chance this code will ** be reusable in other forms we write is pretty low because of dependency on block and item ** names. it does make it possible for your application to commit an invalid value to the database. Example The following example verifies that Start_Date is less than End_Date. Because Form Builder has already checked that required items for the record are valid.Commcode. /* Method 1: Hardcode the item names into the trigger.TRANSACTIONAL TRIGGERS Transactional triggers fire in response to a wide variety of events that occur as a form interacts with the data source. BEGIN SELECT description INTO :Employee. When-Validate-Record Trigger This trigger fires after standard record-level validation. This code presumes both date items are mandatory and that neither will be NULL.*/ BEGIN IF :Experiment. END.Data_Found THEN Message('Invalid Commission Plan.Start_Date > :Experiment. Since these two text items have values that are related. When-Validate-Record must be defined at block level or above. When – Validate -Record Fires during the Validate the Record process. it fires as the last part of record validation for records with the New or Changed validation status. RAISE Form_Trigger_Failure. Use a When-Validate-Record trigger to supplement Form Builder default record validation processing. in the order they were entered. Transaction processing includes two phases: • Post: – Writes record changes to base tables – Fires transactional triggers • Commit: Performs database commit . END IF. While this behavior is necessary to avoid validation loops. 2. EXCEPTION WHEN No. Form Builder marks the record and all of the fields as Valid and does not re-validate. you can use this trigger to perform additional checks that may involve more than one of the record’s items. RAISE Form_Trigger_Failure. END. Use <List> for help').. 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.INTO statement must return an error if more than one row is retrieved that matches the criteria. Specifically.Commplan_Desc FROM commplan WHERE commcode = :Employee. ** Structured this way. This implies PL/SQL may attempt to fetch data twice from the table in question to insure that there aren't two matching rows. rather than check each item separately.. WHEN Too_Many_Rows THEN Message('Error. I.End_Date THEN Message('Your date range ends before it starts!').
then: 6 Issue an SQL-COMMIT statement.Fire the Post-Insert trigger. before base table blocks are processed.Fire the Post-Delete trigger. 4 Validate the block (for all blocks in sequential order).Check the record uniqueness. It fires once for each record that is marked for delete. anytime a database commit is going to occur.Fire the Pre-Delete trigger. such as setting up special locking requirements. Usage Notes • Use a Pre-Delete trigger to delete the detail record of a master record. set up special locking Pre-Commit Fires once during commit processing. 7 Fire the Post-Database-Commit trigger. even if there are no changes to post. .Delete the row from the base table or fire the On-Delete trigger. Pre-Delete Journaling. . 5 Fire the Post-Forms-Commit trigger. If it is an updated record: Fire the Pre-Update trigger. Pre-Commit: Fires once if form changes are made or uncommitted changes are posted 2.) Usage Notes: Use a Pre–Commit trigger to perform an action. . Fire the Post-Update trigger. fires if there are changes to base table items in the form or if changes have been posted but not yet committed (This trigger always fires in case of uncommitted posts. If the current operation is COMMIT.Copy Value From Item. For all deleted records of the block (in reverse order of deletion): . before a row is deleted. Commit Triggers Uses 1. implement foreign-key delete rule Fires during the Post and Commit Transactions process. 3 Fire the Pre-Commit trigger. . Pre-Commit Check user authorization. Check the record uniqueness Update the row in the base table or fire the On-Update trigger. For all inserted or updated records of the block in sequential order: If it is an inserted record: .Shik Mahamood Ali Errors result in: • Rollback of the database changes • Error message The Commit Sequence of Events 63 The commit sequence of events (when the Array DML size is 1) is as follows: 1 Validate the form. .Insert the row into the base table or fire the On-Insert trigger.Fire the Pre-Insert trigger. 2 Process save point. . .
and then writes a row into an auditing table. It fires once for each record that is marked for insert. CLOSE next_ord.id FROM SYS. PRE-DELETE TRIGGER -DECLARE CURSOR C1 IS SELECT ’anything’ FROM S_ORD WHERE customer_id = :S_CUSTOMER.dummy. /* ** Make sure we populated a new order id ok. Note: The Insert Allowed and Keyboard Navigable properties on :S_ORD. RAISE form_trigger_failure. FETCH C1 INTO :GLOBAL.dual.id. If you use this method. */ OPEN next_ord.NEXTVAL FROM dual. recording the new upper value for the sequence. • Use Post-Insert to update the sequence table. flagging creation of a new order..OrderId. */ . automatically generated columns. FETCH next_ord INTO :Order. which will be written to the ID column when the row is subsequently inserted. IF C1%FOUND THEN MESSAGE(’There are orders for this customer!’). END IF. Pre-Insert Fires during the Post and Commit Transactions process. Generate sequence numbers. then two transactional triggers are usually involved: • Use Pre-Insert to select the next available number from the sequence table (locking the row to prevent other users from selecting the same value) and increment the value by the required amount. END. BEGIN OPEN C1.id should be No. check constraints Usage Notes: Use a Pre–Insert trigger to perform the following tasks: • change item values • keep track of the date a record is created and store that in the record prior to committing Example:1 This Pre-Insert trigger on the S_ORD block assigns an Order ID from the sequence S_ORD_ID. journaling. so that the user does not enter an ID manually.. Final checks before row deletion 3.nextval INTO :S_ORD. Begin SELECT S_ORD_ID.Shik Mahamood Ali 64 • Use a Pre-Delete trigger to prevent the deletion of a record if that record is the master record for detail records that still exist. ** but explicit cursor is more efficient. before a row is inserted.INTO. End.. ELSE CLOSE C1.. BEGIN /* ** Fetch the next sequence number from the ** explicit cursor directly into the item in ** the Order record. You can also assign sequence numbers from a table. Example:2 This example assigns a primary key field based on a sequence number. DECLARE CURSOR next_ord IS SELECT orderid_seq. Could use SELECT.
username. ’New Order’. FETCH old_value INTO old_discount.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.oper_desc. /* ** If the old and current values are different. END. 5.CustId.. before a row is updated.CustId. CLOSE old_value..OrderId IS NULL THEN Message(’Error Generating Next Order Id’). END IF. username. DECLARE old_discount NUMBER.SYSDATE ). On-Commit .INTO but choose an explicit cursor for efficiency. e. We need to do this since the value of :Customer. ** ’Changed Discount from 13. timestamp ) VALUES ( :Customer. auto-generated columns.OrderId.g. It fires once for each record that is marked for update.5% to 20%’ */ oper_desc := ’Changed Discount from ’|| TO_CHAR(old_discount)||’% to ’|| TO_CHAR(new_discount)||’%’. We could use SELECT.Shik Mahamood Ali 65 IF :Order. timestamp ) VALUES ( :Order. 4. */ OPEN old_value. oper_desc VARCHAR2(80). Pre-Update Fires during the Post and Commit Transactions process. END. operation. /* ** Insert the audit record with timestamp and user */ INSERT INTO cust_audit( custid. CURSOR old_value IS SELECT discount_pct FROM customer WHERE CustId = :Customer. check constraints Usage Notes: Use a Pre–Update trigger to audit transactions. implement foreign-key update rule. including timestamp and username making the change. BEGIN /* ** Fetch the old value of discount percentage from the database by CustomerId. RAISE Form_Trigger_Failure. Example: The following example writes a row into an Audit Table showing old discount and new discount for a given customer.Discount_Pct.SYSDATE ).USER. /* ** Insert a row into the audit table */ INSERT INTO ord_audit( orderid. USER. END IF. operation. 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. new_discount NUMBER := :Customer. Journaling.
the commit operation behaves normally. On-Insert Fires during the Post and Commit Transactions process when a record is inserted. /* ** otherwise. it fires after the Pre–Delete trigger fires and before the Post–Delete trigger fires. Description When called from an On-Insert trigger. On-Delete Fires during the Post and Commit Transactions process. Example: This example disables the commit operation when running against a datasource that does not support transaction control. If the application is running against ORACLE. 6. include a call to the INSERT_RECORD built-in. no action is performed */ END. This built-in is included primarily for applications that will run against a non-ORACLE datasource. To perform the default Form Builder processing from this trigger. call to the COMMIT_FORM built–in. include a call to the DELETE_RECORD built–in.Empno. • To perform the default processing from this trigger. It fires once for each row that is marked for insertion into the database. when Form Builder would normally insert a record in the database. Syntax PROCEDURE INSERT_RECORD. Example: This example updates the employee table to set the Termination_Date. to delete a record from your form or from the database. BEGIN IF Get_Application_Property(DATA_SOURCE) = ’ORACLE’ THEN Commit_Form. END IF. Specifically. replacing the actual database delete of a given row. Usage Notes • • Use an On-Insert trigger to replace the default Form Builder processing for handling inserted records during transaction posting. Specifically. . By default. The trigger fires once for each row that is marked for deletion from the database. END. and deletes have been posted to the database. Usage Notes: • • Use an On–Delete trigger to replace the default Oracle Forms processing for handling deleted records during transaction posting. rather than actually deleting the employee from the database. that is. BEGIN UPDATE emp SET termination_date = SYSDATE WHERE empno = :Emp. 7. 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. this operation occurs after all records that have been marked as updates. it fires after the Pre-Insert trigger fires and before the Post-Insert trigger fires.Shik Mahamood Ali 66 Fires whenever Oracle Forms would normally issue a database commit statement to finalize a transaction. inserts. inserts the current record into the database during Post and Commit Transactions processing. To perform the default Oracle Forms processing from this trigger.
/* ** Otherwise. updates. initiates the default Form Builder processing for updating a record in the database during the Post and Commit Transaction process. . • The Update Changed Columns Only and Enforce Column Security properties affect UPDATE statements. • Form Builder uses and retrieves ROWID.. On-Update Fires during the Post and Commit Transactions process. • Locking statements are not issued. and deletes have been posted to the . */ ELSE Insert_Record. do the right thing. .. base_column. This builtin is included primarily for applications that run against a non-ORACLE data source. after the database commit occurs. Specifically.) UPDATE base_table SET base_column = :base_item. it fires after the Pre–Update trigger fires and before the Post–Update trigger fires. 8.. END. include a call to the UPDATE_RECORD built–in.. perhaps based on a parameter. When called from an On-Update trigger.Using_Transactional_Triggers = 'TRUE' THEN User_Exit('my_insrec block=EMP').Shik Mahamood Ali 67 /* ** Built-in: INSERT_RECORD ** Example : Perform Form Builder standard insert processing ** based on a global flag setup at startup by the ** form. :base_item. END IF..WHERE ROWID = :ROWID DELETE FROM base_table WHERE ROWID = :ROWID DML Statements Issued During Commit Processing Rules: • DML statements may fire database triggers. base_column = :base_item.. ** Trigger: On-Insert */ BEGIN /* ** Check the global flag we setup at form startup */ IF :Global. Begin UPDATE RECORD. End.) VALUES ( :base_item. 9. DML Statements Issued During Commit Processing INSERT INTO base_table ( base_column. when Oracle Forms would normally update a record in the database. Usage Notes: • • Use an On–Update trigger to replace the default Oracle Forms processing for handling updated records during transaction posting.. It fires once for each row that is marked for update in the form. Note that the Post-Forms-Commit trigger fires after inserts. Post – Database Commit Description Fires once during the Post and Commit Transactions process. To perform the default Oracle Forms processing from this trigger.
Did_DB_Commit = 'FALSE'). anytime a database commit is about to occur. but before the transaction has been finalized by issuing the Commit. Post – Form .Shik Mahamood Ali 68 database. RETURN (:System.Form_Status = 'QUERY' AND :Global. END. or deletes.'Global. or deletes.Did_DB_Commit'). It fires once for each row that is deleted from the database during the commit process. form or block Usage Notes: . END. If there are records in the form that have been marked as inserts.Commit Fires once during the Post and Commit Transactions process. after a row is deleted.Did_DB_Commit = FALSE').Did_DB_Commit := 'FALSE'. Usage Notes Use a Post-Database-Commit trigger to perform an action anytime a database commit has occurred.Form_Status = 'QUERY'AND :Global. Usage Notes • • Use a Post-Forms-Commit trigger to perform an action. END. uncommitted changes 10. 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. /* FUNCTION recs_posted_and_not_committed RETURN BOOLEAN IS BEGIN Default_Value('TRUE'. Post-Database-Commit Determines if commit was successful. Example /* ** FUNCTION recs_posted_and_not_committed ** RETURN BOOLEAN IS BEGIN Default_Value('TRUE'. 11. END. updates. Form Builder fires the Post-Forms-Commit trigger immediately. The Post-DatabaseCommit Trigger fires after Form Builder issues the Commit to finalize the transaction. updates. */ BEGIN :Global.'Global.Did_DB_Commit := 'FALSE'. without posting changes to the database. such as updating an audit trail.Did_DB_Commit'). Post-Forms-Commit Checks complex multirow constraints Example This example can be used in concert with the Post-Database-Commit trigger to detect if records have been posted but not yet committed. If the operator or the application initiates a Commit when there are no records in the form have been marked as inserts. determines if there are posted. Post – Delete Fires during the Post and Commit Transactions process. */ BEGIN :Global. RETURN (:System.
Example .id. Post-Insert trigger: Begin INSERT INTO LOG_TAB (LOG_VAL.Shik Mahamood Ali 69 Use a Post–Delete trigger to audit transactions. Usage Notes: Use a Post–Update trigger to audit transactions.:GLOBAL. End.id.along with a time stamp and the user who performed the update.1 Begin INSERT INTO delete_audit (id.insert_tot := TO_CHAR(TO_NUMBER(:GLOBAL.id. It fires once for each row that is updated in the database during the commit process. RAISE form_trigger_failure. LOG_USER) VALUES(:S_DEPT. This Post-Update trigger writes the current record ID to the UPDATE_AUDIT table. just after a record is inserted.insert_tot)+1). include EXCEPTION section in trigger. Gather statistics on applied changes.2 Begin Delete from S_ORD SET WHERE id = :S_ORD. 12. Example . 13. USER ).1 Begin . Example 2 To handle exceptions. End.||SQLERRM).username). after a row is updated. Example . END IF. IF SQL%NOTFOUND THEN MESSAGE(’Record not found in database’). who_did_it)VALUES ( :S_ORD. Else Messafe(SQL%rowcount|| “ rows Deleted”). End. Post – Update Fires during the Post and Commit Transactions process. Example 1 Keeping an Audit Trail :GLOBAL. Write changes to nonbase tables. • • • Use a Post-Insert trigger to audit transactions. It fires once for each record that is inserted into the database during the commit process. timestamp. EXCEPTION WHEN OTHERS THEN MESSAGE(’Error! ’. Post – Insert Fires during the Post and Commit Transactions process. SYSDATE.
and then writes a row into an auditing table.SYSDATE ). parse. This example assigns a primary key field based on a sequence number. End. 15. FETCH next_ord INTO :Order. timestamp.id. BEGIN /** Fetch the next sequence number from the Explicit cursor directly into the item in the Order record. username. timestamp ) VALUES ( :Order. END. Query Processing Triggers Uses 14.1 . RAISE Form_Trigger_Failure. Example . 70 INSERT INTO update_audit (id.LAST_QUERY Fires after Form Builder has constructed the block SELECT statement based on the query conditions. 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 Fires when Form Builder would normally execute the open cursor. SYSDATE.NEXTVAL FROM dual. parse. On . Usage Notes • Use an On-Select trigger to open and execute the database cursor.OrderId. and execute phases.OrderId IS NULL THEN Message(’Error Generating Next Order Id’). /** Insert a row into the audit table INSERT INTO ord_audit( orderid. Pre – Select Fires during Execute Query and Count Query processing.OrderId. after Form Builder constructs the SELECT statement to be issued. RAISE form_trigger_failure.USER. IF SQL%NOTFOUND THEN MESSAGE(’Record not found in database’).INTO. operation.’New Order’. Could use SELECT. use this trigger when you are retrieving data from a non-ORACLE data source. but before the statement is actually issued. END IF.2 Begin UPDATE S_ORD SET date_shipped = SYSDATE WHERE id = :S_ORD.. END IF. 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. To perform the default Form Builder processing from this trigger.id. Note that the SELECT statement can be examined in a Pre-Select trigger by reading the value of the system variable SYSTEM. ** but explicit cursor is more efficient. • Example .Shik Mahamood Ali USER ). Specifically. */ OPEN next_ord. to identify the records in the database that match the current query criteria. and execute phases of a query. include a call to the SELECT_RECORDS built-in. On-Select replaces open cursor. CLOSE next_ord. End. IF :Order. who_did_it)VALUES ( :S_ORD. DECLARE CURSOR next_ord IS SELECT orderid_seq. flagging creation of a neworder.
j LOOP /* ** Try to get the next row. Post-Select Trigger Description Fires after Form Builder has constructed and issued the block SELECT statement. ELSE /* ** Perform the default Form Builder task of opening the query.. End. It fires before any records are actually retrieved through fetch processing.) • On-Fetch continues to fire until: – It fires without executing CREATE_QUERIED_RECORD. :Emp.rowid := emprow. END LOOP.Get_Next_Row(emprow). 'Query.EMPNO.Shik Mahamood Ali 71 In the following example. to perform a query against a database. . emprow emp%ROWTYPE. */ EXIT WHEN NOT MyPackage. */ Select_Records.ENAME. the On-Select trigger is used to call a user exit. 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. On–Fetch: DECLARE j NUMBER := Get_Block_Property(blk_name. The trigger will fire once for each record that is to be fetched. BEGIN FOR ctr IN 1. 15. – The query is closed by the user or by ABORT_QUERY. END IF.ename := emprow. but before it fetches the records The Post-Select trigger fires after the default selection phase of query processing. IF form_fatal OR form_failure THEN raise form_trigger_failure.' and a built-in subprogram. IF Form_Failure OR Form_Fatal THEN ABORT_QUERY. RECORDS_TO_FETCH).ROWID. – It raises FORM_TRIGGER_FAILURE. :Emp. 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. Begin IF Get_Application_Property(DATASOURCE) = 'DB2' THEN User_Exit ( 'Query' ). :Emp. SELECT_RECORDS. 16. END IF. Create_Queried_Record. or after the successful execution of the On-Select trigger.empno := emprow.
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.DNAME')). In such a case. When the On-Count trigger completes execution. END. Set_Block_Property('DEPT'. 72 16. END. Form Builder issues the standard query hits message: FRM-40355: Query will retrieve <n> records. the message reports 0 records identified. Example 2 /* ** Built-in: COUNT_QUERY ** Example: Display the number of records that will be retrieved ** by the current query. Decide whether to use this Built-in or a user ** exit based on a global flag setup at startup by the form. include a call to the built-in. • 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.Shik Mahamood Ali END IF. DECLARE j NUMBER. Example .Name_In('DEPT.QUERY_HITS. On – Count Fires when Form Builder would usually perform default Count Query processing to determine the number of rows that match the query conditions Fires when Form Builder would normally perform default Count Query processing to determine the number of rows in the database that match the current query criteria. • To perform the default Form Builder processing from this trigger. perhaps based on a parameter. Example 3 /* ** Built-in: COUNT_QUERY ** Example: Perform Form Builder count query hits processing.1 This example calls a user-named subprogram to count the number of records to be retrieved by the current query criteria. * Trigger: On-Count */ .j). Usage Notes • Use an On-Count trigger to replace default Count Query processing in an application running against a non-ORACLE data source. • If you are replacing default processing. BEGIN j := Recs_Returned('DEPT'. and sets the Query_Hits property appropriately. Count_Query. */ BEGIN END.
call the GENERATE_SEQUENCE_NUMBER built-in.hits).Using_Transactional_Triggers = 'TRUE' THEN /* ** User exit returns query hits count back into the ** CONTROL. */ ELSE Generate_Sequence_Number. 17. Count_Query. END IF. */ Set_Block_Property(:System. • To perform the default Form Builder processing from this trigger. do the right thing. perhaps based on a parameter. do the right thing. . /* ** Deposit the number of query hits in the appropriate ** block property so Form Builder can display its normal ** status message. Suppress or override this functionality with an On-Sequence-Number trigger. /* ** Otherwise. ** Trigger: On–Sequence–Number */ BEGIN /* ** Check the global flag we setup at form startup */ IF :Global. /* ** Otherwise.QUERY_HITS. 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.Using_Transactional_Triggers = ’TRUE’ THEN User_Exit(’my_seqnum seq=EMPNO_SEQ’).Shik Mahamood Ali BEGIN 73 /* ** Check the global flag we set during form startup */ IF :Global.Trigger_Block. */ ELSE END. Replaces the default series of events that occurs when Form Builder interacts with the database to get the next value from a SEQUENCE object defined in the database.On-Sequence-Number Trigger Description Fires when Form Builder would normally perform the default processing for generating sequence numbers for default item values.:control. */ User_Exit('my_count'). Form Builder queries the database to get the next value from the SEQUENCE whenever the Create Record event occurs.HITS item. Usage Notes • When a SEQUENCE is used as a default item value.
and free memory. 19. specifically. END. By default. close cursors. The On-Close trigger fires automatically when the ABORT_QUERY built-in is called from an On-Select trigger.'). Usage Notes To perform the default processing from this trigger. CLOSE chk_unique. IF tmp IS NOT NULL THEN Message('This department already exists. tmp VARCHAR2(1). END. Form Builder. .Shik Mahamood Ali END IF. On-Check-Unique Trigger 74 Description During a commit operation. or when the operator or the application aborts the query. Form Builder checks for unique primary key values only if one or more items that have the Primary Key item property have been modified. RAISE Form_Trigger_Failure. BEGIN OPEN chk_unique. If a duplicate row is found. It fires once for each record that has been inserted or updated. Form Builder closes a query when all of the records identified by the query criteria have been fetched. call the CHECK_RECORD_UNIQUENESS built-in. Usage Notes • • Use an On-Close trigger after using the On-Select or On-Fetch triggers. the On-Check-Unique trigger fires when Form Builder normally checks that primary key values are unique before inserting or updating a record in a base table. FETCH chk_unique INTO tmp. by default. In the case of an update. On-Check-Unique Trigger examples The following example verifies that the current record in question does not already exist in the DEPT table. Replaces the default processing for checking record uniqueness. to close files. 18. For a record that has been marked for insert. END IF. When a block has the PRIMKEYB property set to Yes. 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 displays message FRM-40600: Record has already been inserted. DECLARE CURSOR chk_unique IS SELECT 'x' FROM dept WHERE deptno = :dept. The On-Close trigger augments the normal Form Builder "close cursor" phase of a query.deptno. On-Close Trigger Description Fires when an operator or the application causes a query to close. Form Builder always checks for unique primary key values.
END IF. ELSE on_or_off := PROPERTY_ON.ENABLED. Only users with the user-defined SUPERUSER role can change these number fields. call the ENFORCE_COLUMN_SECURITY built-in. Form Builder makes the corresponding base table items in the form non-updateable by setting the Update Allowed item property Off dynamically. to roll back a . 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 NUMBER. unless the SUPERUSER role is enabled.on_or_off). itm_id := Find_Item('Emp. For columns to which the operator does not have update privileges. END. 20.UPDATEABLE. Set_Item_Property(itm_id. Set_Item_Property(itm_id. Form Builder performs this operation at form startup. On-Rollback Trigger Description Fires when Form Builder would normally issue a ROLLBACK statement. Set_Item_Property(itm_id. Usage Notes To perform the default processing from this trigger.Shik Mahamood Ali 75 Example The following example releases memory being used by a user-defined data access method via the transactional triggers. 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. BEGIN IF NOT role_is_set('SUPERUSER') THEN on_or_off := PROPERTY_OFF. processing each block in sequence. END. Set_Item_Property(itm_id. 21. itm_id := Find_Item('Emp. BEGIN IF NOT my_data source_open('DX110_DEPT') THEN my_datasource_close('DX110_DEPT').Comm'). By default.Sal'). END IF.on_or_off).on_or_off).on_or_off).ENABLED.UPDATEABLE. Example The following example sets salary and commission text items in the current block to disabled and non-updateable. DECLARE itm_id Item.
DECLARE connected BOOLEAN:=FALSE. particularly to a nonORACLE data source. ** Trigger: On-Rollback */ DECLARE sp_name VARCHAR2(80). To perform default Form Builder processing from this trigger. To perform the default Oracle Forms processing from this trigger. You can supply a NULL command to this trigger to bypass the connection to a data source. END. ISSUE_ROLLBACK examples /* ** Built-in: ISSUE_ROLLBACK ** Example: Perform Form Builder standard Rollback processing. (NULL = Full Rollback)*/ sp_name := Get_Application_Property(SAVEPOINT_NAME). J. BEGIN /* Get the name of the savepoint to which Form Builder needs to ** rollback. 2. if you want to create an application that does not require a data source. . ** Decide whether to use this built-in based on a ** global flag setup at startup by the form. include a call to the LOGON built–in.Shik Mahamood Ali 76 transaction to the last savepoint that was issued. Usage Notes Use an On-Rollback trigger to replace standard Form Builder rollback processing. Pre-Logon Trigger Fires just before Form Builder initiate a logon procedure to the data source. • • • Pre–Logon and Post–Logon triggers fire as part of the logon procedure. include a call to the ISSUE_ROLLBACK built-in. Usage Notes Use a Pre-Logon trigger to prepare the form for the logon procedure. ** perhaps based on a parameter. On-Logon Trigger Fires once per logon when Oracle Forms normally initiates the logon sequence.LOGON TRANSACTION TRIGGERS 1. END IF . Usage Notes: Use an On–Logon trigger to initiate a logon procedure to a non–ORACLE data source. /* ** Check the global flag we setup at form startup */ IF :Global. ELSE Issue_Rollback(sp_name).Using_Transactional_Triggers = 'TRUE' THEN User_Exit('my_rollbk name='||sp_name).
'YYYYMMDDHH24MISS')). END. IF FORM_SUCESS THEN Connected:=TRUE. Pre-Logout Trigger Fires once before Form Builder initiate a logout procedure. END IF. cs VARCHAR2(30). User_Exit('LogCrypt '|| USER||' ' ||TO_CHAR(SYSDATE. RAISE FORM_TRIGGER_FAILURE. which for security reasons is outside the database. IF NOT CONNECTED THEN MESSAGE(‘Too many tries’). 3. pw:=GET_APPLICATION_PROPERTY( PASSWORD ). pw VARCHAR2(30). BEGIN 77 SET_APPLICATION_PROPERTY(CURSOR_STYLE. END IF. Tries:=tries-1. un NUMBER. pw || ‘@’ || CS . BEGIN END. WHILE CONNECTED = FALSE AND tries > 0 LOOP LOGON_SCREEN. 4. LOGON( un. un:=GET_APPLICATION_PROPERTY( USERNAME ). FALSE ). END LOOP. Usage Notes • • Use a Pre-Logout trigger to prepare the form for logging out from the data source. If you call certain built-ins from within one of the Logout triggers.’DEFAULT’). particularly a non-ORACLE data source. The successful execution of the On-Logon trigger. the COPY built-in cannot be called from a Pre-Logout trigger . the results are undefined. cs:= GET_APPLICATION_PROPERTY( CONNECTION_STRING ). Example This example calls a user exit to log the current username and time to an encrypted audit trail file on the file system. POST-LOGON TRIGGER Description Fires after either of the following events: • • The successful completion of Form Builder default logon processing.Shik Mahamood Ali tries NUMBER:=3. For example.
which for security reasons is outside the database.’YYYYMMDDHH24MISS’)). When-Mouse-Click Trigger . 5. you cannot call the COPY built-in from a Pre-Logout trigger because Pre-Logout fires after the Leave the Form event. For example. Usage Notes • • • Use an On-Logout trigger to replace the default logout processing either from the RDBMS or from a non-ORACLE data source. BEGIN User_Exit(’LogCrypt ’||USER||’ ’ || TO_CHAR(SYSDATE. Post-Logout Trigger Description Fires after either of the following events: • • Form Builder successfully logs out of ORACLE. END. the results are undefined. Because the form is no longer accessible. The successful execution of the On-Logout trigger. 6. If you call certain built-ins from within one of the Logout triggers. Because the form is no longer accessible at this point. This example calls a user exit to log the current username and time to an encrypted audit trail file on the file system. the results are undefined. the COPY operation is not possible.MOUSE TRIGGERS 1. For example.Shik Mahamood Ali 78 because Pre-Logout fires after the Leave the Form event. J. 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. a COPY operation is not possible. To perform the default Form Builder processing from this trigger. On-Logout Trigger Fires when Form Builder normally initiates a logout procedure from Form Builder and from the RDBMS. a COPY operation is not possible. • If you call certain built-ins from within one of the Logout triggers. Because the form is no longer accessible. 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.
when the mouse is clicked within any item in the block 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. Usage Notes Use the When-Mouse-Click trigger to perform an action every time the operator clicks the mouse within an item and/or canvas. When-Mouse-DoubleClick Trigger Description Fires after the operator double-clicks the mouse if one of the following events occurs: • • • if attached to the form. 2. when the mouse is double-clicked within any item in the block if attached to an item. when the mouse is clicked within any canvas or item in the form if attached to a block. when the mouse is clicked within the item Three events must occur before a When-Mouse-Click trigger will fire: • • • Mouse down Mouse up Mouse click Any trigger that is associated with these events will fire before the When-Mouse-Click trigger fires.Shik Mahamood Ali Description 79 Fires after the operator click the mouse if one of the following events occurs: • • • if attached to the form. when the mouse is double-clicked within the item Six events must occur before a When-Mouse-DoubleClick trigger will fire: • • • • • • Mouse Mouse Mouse Mouse Mouse Mouse down up click down up double-click Any trigger that is associated with these events will fire before the When-Mouse-DoubleClick trigger fires. When-Mouse-DoubleClick Trigger examples Example . when the mouse is double-clicked within any canvas or item in the form if attached to a block.
For example. assume that the mouse has entered Canvas_One causing the When-Mouse-Enter trigger to fire which in turn causes Alert_One to appear. However. The user is able to scroll the canvas to see the items. if the operator clicks the mouse. Changing a tooltip's property in a When-Mouse-Enter trigger cancels the tooltip before it is ever shown. Do not use the When-Mouse-Enter trigger on a canvas that is larger than the window. Finally. Be careful when calling a modal window from a When-Mouse-Enter trigger. 3. so the user is never able to click on those items. Further. when the mouse is pressed down within any canvas or item in the form if attached to a block. the trigger fires and returns focus to the previous target.Shik Mahamood Ali 80 Assume that an application requires Behavior A when the operator clicks the mouse and Behavior B when the operator double-clicks the mouse. but appear side by side on the screen. Canvas_One and Canvas_Two do not overlap each other. 4. Doing so may cause the modal window to appear unnecessarily. For example. when the mouse is pressed within the item Usage Notes • Use a When-Mouse-Down trigger to perform an action every time the operator presses down the mouse button within an item and/or canvas. when the mouse is pressed down within any item in the block if attached to an item. a product information window must appear. Iconic buttons and items on the canvas below the initial window cannot be selected. When-Mouse-Enter Trigger Description Fires when the mouse enters an item or canvas if one of the following events occurs: • • • if attached to the form. when the mouse enters any item in the block if attached to an item. Note: The mouse down event is always followed by a mouse up event. as soon as the mouse enters that area. Canvas_One and Canvas_Two. when the mouse enters any canvas or item in the form if attached to a block. assume that your When-Mouse-Enter trigger causes Alert_One to appear whenever the mouse enters Canvas_One. Assume also that your application contains two canvases. . an online help window must appear. 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. assume that Alert_One displays within Canvas_Two's border. When-Mouse-Down Trigger Description Fires after the operator presses down the mouse button if one of the following events occurs: • • • if attached to the form. If the operator double-clicks the mouse.
SHOW_VIEW(’cv_help’).CURSOR_ITEM. HIDE_VIEW(’cv_help’). WHEN-MOUSE-ENTER at Form Level begin IF :SYSTEM. any When-Mouse-Leave triggers associated with this event will fire. End. .save_item_name := :SYSTEM. when the mouse leaves any item in the block if attached to an item. when the mouse leaves any canvas or item in the form if attached to a block. When-Mouse-Leave Trigger Description Fires after the mouse leave an item or canvas if one of the following events occurs: • • • if attached to the form. GO_ITEM(’s_ord.MOUSE_CANVAS = ’CV_ORDER’ THEN :control. 6. 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. when the mouse moves within any item in the block if attached to an item. Alert_One will appear again unnecessarily if the operator subsequently enters Canvas_One with the mouse.show_help_button begin End. when the operator moves the mouse out of Canvas_Two.show_help_button := ’?’. The When-Mouse-Move trigger may have performance implications because of the number of times this trigger can potentially fire. GO_ITEM(:GLOBAL. when the mouse moves within any canvas or item in the form if attached to a block.Shik Mahamood Ali 81 When the operator dismisses the message box. This may not be the desired behavior. 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.save_item_name). 5.id’). When-Mouse-Move Trigger Description Fires each time the mouse moves if one of the following events occurs: • • • if attached to the form. END IF. In addition. End. WHEN-MOUSE-LEAVE trigger on control. begin :GLOBAL.
the scope of a user-named trigger is the definition level and below. you must call the EXECUTE_TRIGGER built–in procedure. The mouse up event is always associated with the item that received the mouse down event. User-Named Trigger A user–named trigger is a trigger that you define yourself in a form. Create a user-named trigger to execute user-named subprograms defined in a form document from menu PL/SQL commands and user-named subprograms. which is defined in a different document. as shown here: Execute_Trigger(’my_user_named_trigger’). As with all triggers. rather than for Item_Two. (User-named subprograms defined in a form cannot be called directly from menu PL/SQL. K.OTHER TRIGGERS 1. but then releases the mouse on Item_Two. It is most practical to define user-named triggers at the form level. when the mouse up event is received within any canvas or item in form attached to a block. the trigger defined at the lowest level has precedence. For example. and then call explicitly from other triggers or user–named subprograms. call the EXECUTE_TRIGGER built-in to execute a usernamed trigger. When more than one user-named trigger has the same name. If the operator presses down the mouse on Item_One. which in turn calls the user-named subprogram defined in the current form. Usage Notes User-named PL/SQL subprograms can be written to perform almost any task for which one might use a user-named trigger. To execute a user–named trigger. Note: You can write user–named PL/SQL subprograms to perform almost any task for which you might use a user–named trigger.Shik Mahamood Ali 7. the mouse up trigger will fire for Item_One. When-Mouse-Up Trigger 82 Description Fires each time the operator presses down and releases the mouse button if one of the following events occurs: • • • if a if if attached to the form.) In the menu PL/SQL. If no such key . assume that there is a When-Mouse-Up trigger attached to Item_One. when the mouse up event is received within any item in a block attached to an item. Each user–named trigger defined at the same definition level must have a unique name. DO_KEY built-in Executes the key trigger that corresponds to the specified built-in subprogram. 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.
/* ** Built-in: ISSUE_SAVEPOINT ** Example: Perform Form Builder standard savepoint processing. then the specified subprogram executes. BEGIN /* Get the name of the savepoint Form Builder needs to issue */ sp_name := Get_Application_Property(SAVEPOINT_NAME). if no On-Savepoint trigger were present. include a call to the ISSUE_SAVEPOINT built-in. In an On-Savepoint trigger.Shik Mahamood Ali 83 trigger exists. use the EXECUTE_TRIGGER built-in: EXECUTE_TRIGGER('KEY_F11'). /* Otherwise. In an On-Rollback trigger . the Savepoint_Name application property returns the name of the next savepoint that Form Builder would issue by default. Form Builder issues savepoints at form startup. do the right thing. To accept a specific key name. Do_Key('Execute_Query'). ** Trigger: On-Savepoint */ DECLARE sp_name VARCHAR2(80). ** Decide whether to use this built-in based on a global flag setup at startup by the form. */ ELSE . Usage Notes To perform default Form Builder processing from this trigger. Savepoint_Name returns the name of the savepoint to which Form Builder would roll back. When Savepoint Mode is Off. DO_KEY restrictions DO_KEY accepts built-in names only. the On-Savepoint trigger never fires.Using_Transactional_Triggers = 'TRUE' THEN User_Exit('my_savept name='||sp_name).perhaps based on a parameter. Suppress default savepoint processing by setting the Savepoint Mode form document property to Off. not key names: DO_KEY(ENTER_QUERY). This behavior is analogous to pressing the corresponding function key. 2. /* Check the global flag we setup at form startup */ IF :Global. DO_KEY examples /* ** Built-in: DO_KEY ** Example: Simulate pressing the [Execute Query] key. Form Builder does not issue savepoints and. */ BEGIN END.consequently. and at the start of each Post and Commit Transaction process. Syntax PROCEDURE DO_KEY (built-in_subprogram_name VARCHAR2). By default. On-Savepoint Trigger Fires when Form Builder would normally issue a Savepoint statement.
In other words. The Post-Query trigger does not have the restrictions of the Post-Change trigger. you can use the On–Lock trigger to speed processing by bypassing all lock processing. For example. END IF. you must include a Post-Query trigger in addition to your When-Validate-Item trigger. such as when an operator presses a key to modify data in an item. Usage Notes: • Use an On–Lock trigger to replace the default Oracle Forms processing for locking rows. Decide whether to use default processing or a user exit by consulting a global flag setup at startup by the form. You can use Post-Query to make changes to the fetched database values. the trigger fires only the first time the operator tries to modify an item in the record. the trigger fires once. • When the On–Lock trigger fires as a result of an operator trying to modify data. END. See "Usage Notes" below. In this case. 3. Post-Change Trigger 84 Fires when any of the following conditions exist: • • • The Validate the Item process determines that an item is marked as Changed and is not NULL. If you want to circumvent this situation and effectively get rid of the Post-Change trigger. /* ** 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. 3.perhaps based on a parameter. Form Builder fetches a non-NULL value into an item. Usage Notes • • The Post-Change trigger is included only for compatibility with previous versions of Form Builder. On-Lock Trigger Fires whenever Oracle Forms would normally attempt to lock a row. and the item is not NULL. not by way of Open Gateway. Its use is not recommended in new applications. if you are designing an application for use on a single–user system. include a call to the LOCK_RECORD built–in. The trigger fires between the key press and the display of the modified data. • Use this trigger to lock underlying tables for non–updateable views.Shik Mahamood Ali Issue_Savepoint(sp_name). use On–Lock if you are accessing a non–ORACLE data source directly. Form Builder marks the corresponding items and records as changed. The trigger does not fire during subsequent modifications to items in the same record. • To perform the default Oracle Forms processing from this trigger. ** Trigger: On-Lock */ BEGIN . for every row that is to be locked. Also. An operator returns a value into an item by making a selection from a list of values. Given such changes.
8. DECLARE TabEvent varchar2(80). 7. This trigger is called when a query operation is necessary.) Actions defined for this trigger are performed before the pop-up menu is displayed. and the system variable SYSTEM. (In a Microsoft Windows environment. the query stored procedure has to use those values to filter the data.Non_Oracle_Datasource = 'TRUE' THEN User_Exit('my_lockrec block=EMP'). Think of this as an On-Query trigger that is called by the system instead of doing default query operations. Example: This is an example of a procedure that can be called when Oracle Forms fires the When–Custom–Item–Event Trigger. The system variable SYSTEM. any of the items may be used. Pre-Popup-Menu Trigger This trigger is called when a user causes a pop-up menu to be displayed. 5. TabNumber Number.CUSTOM_ITEM_EVENT_PARAMETERS stores a parameter name that contains the supplementary arguments for an event that is fired by a VBX control. /* ** Otherwise. Lock_Record. . do the right thing. Usage Notes Use this trigger to enable or disable menu items on a pop-up menu before it is displayed. Think of this as an On-Update trigger that is called by the system instead of doing default update operations. but the Query Data Source Columns property must be set so that those items can be passed to the query stored procedure.CUSTOM_ITEM_EVENT stores the case–sensitive name of the event that occurred. Then. Usage Notes When constructing a query. When-Custom-Item-Event Trigger Fires whenever a VBX control sends an event to Oracle Forms. This trigger is called when a update operation is necessary. This means that the enter query mode does not happen automatically unless you specify it. this occurs when a user presses the right mouse button.Shik Mahamood Ali 85 /* ** Check the global flag we set up at form startup */ IF :Global. END. Usage Notes: Use a When–Custom–Item–Event trigger to respond to a selection or change of value for a VBX control. Query-Procedure Trigger Automatically created by Form Builder when the query data source is a stored procedure. */ ELSE END IF. 6. Update-Procedure Trigger Automatically created by Form Builder when the update data source is a stored procedure.
BEGIN tp_nm := GET_CANVAS_PROPERTY('emp_cvs'. . else SET_WINDOW_PROPERTY(win_id. tp_id := FIND_TAB_PAGE(tp_nm). but the trigger will not fire if an end user presses [Next Item] (Tab) to navigate from one field to another field in the same block. form Use a When–Form–Navigate trigger to perform actions when any cross form navigation takes place without relying on window activate and window deactivate events.’CurrTab’). DECLARE win_id WINDOW := FIND_WINDOW(’WINDOW12’).WINDOW_STATE.MINIMIZE). BEGIN if (GET_WINDOW_PROPERTY(win_id. 9. Usage Notes • Use a When-Tab-Page-Changed trigger to perform actions when any tab page is changed during item or mouse navigation. it does not respond to implicit navigation. tp_id TAB_PAGE. 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 BEGIN TabEvent := :system. */ IF (UPPER(TabEvent) = ’CLICK’) THEN TabNumber := VBX.MAXIMIZE). but on different tab pages.WINDOW_STATE. END. 10. end if. tp_lb VARCHAR2(30). and use the user– defined Goto_Tab_Page procedure to navigate to the selected page.WINDOW_STATE) = ’MAXIMIZE’ THEN SET_WINDOW_PROPERTY(win_id. Goto_Tab_Page(TabNumber). topmost_tab_page). label). • When-Tab-Page-Changed fires only when tab page navigation is explicit. tp_lb := GET_TAB_PAGE_PROPERTY(tp_id. END IF. This is an example of a procedure that can be called when Oracle Forms fires the When–Form– Navigate Trigger.custom_item_event. When-Form-Navigate Trigger Fires whenever any peer form navigation takes place. Example /* Use a When-Tab-Page-Changed trigger to dynamically change a tab page's label from lowerto upper-case (to indicate to end users if they already have ** navigated to the tab page): */ DECLARE tp_nm VARCHAR2(30). • When-Tab-Page-Changed does not fire when the tab page is changed programmatically. /* ** After detecting a Click event. identify the ** tab selected. END. the trigger will fire when the mouse or keyboard is used to navigate between tab pages.Get_Property(’TABCONTROL’. For example.
'VACATION'). Combines the features found in list and text items. allowing the operator to view and select undisplayed values. Only end-user action will generate an event. or combo box DESCRIPTION Combo Box Appears initially as a single field (similar to a text item field). Only end-user action will generate an event.TRIGGER_NODE is the node the user clicked on. When-Tree-Node-Expanded Trigger Fires when a node is expanded or collapsed. • Defining list items A list item displays a predefined set of choices that LIST ITEM Poplist Text List are mutually exclusive can be displayed as either a poplist. 11. Only enduser action will generate an event. a vertical scroll bar appears.TRIGGER_NODE returns a value of type NODE. END IF. Unlike the poplist or the text list style list items.TRIGGER_NODE returns a value of type NODE. the combo box style list item will display fixed values and accept one operator-entered value. 'SALARY'). When the text list contains values that cannot be displayed (due to the displayable area of the item). No programmatic action will cause the When-Tree-Node-Selected trigger to fire. The user can enter text directly into the combo field or click the list icon to display a list of available values. 12. Usage Notes • • SYSTEM. a list of available choices appears. ELSE null. When the operator selects the list icon. . The combo box list item appears as an empty box with an icon to the right. Appears as a rectangular box which displays a fixed number of values. No programmatic action will cause the When-Tree-Node-Expanded trigger to fire. SYSTEM. END. 13. No programmatic action will cause the When-Tree-Node-Activated trigger to fire.Shik Mahamood Ali 87 IF tp_lb LIKE 'Sa%' THEN SET_TAB_PAGE_PROPERTY(tp_id.TRIGGER_NODE is the node the user clicked on. ELSIF tp_lb LIKE 'Va%' THEN SET_TAB_PAGE_PROPERTY(tp_id. SYSTEM. When-Tree-Node-Selected Trigger Fires when a node is selected or deselected. Usage Notes • SYSTEM.TRIGGER_NODE returns a value of type NODE. SYSTEM. text list.TRIGGER_NODE is the node the user clicked on. label. When-Tree-Node-Activated Trigger Fires when an operator double-clicks a node or presses Enter when a node is selected. Usage Notes • • SYSTEM. label.
Shik Mahamood Ali 88 .