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