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