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