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