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