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