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