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