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