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