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