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