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