Oracle Form Builder: Writing and Debugging Code

Audience

Application developers database administrators designer/developers and technical support professionals. Prior to taking this course participants should be familiar with SQL and PL/SQL or have taken courses 61110 61111 61112 and 60113. In addition participants should have taken the first two parts of the Oracle Form Builder series courses 61211 and 61212.

Objective

• Identify the descriptions of the communication formats used by Form Builder.
• Write codes to detect errors suppress system messages create alerts and control alerts at runtime.
• Run a form module in Debug mode.
• Identify the concepts related to debugging a PL/SQL code.
• Debug a PL/SQL code.
• Identify the process involved in querying a data block.
• Write triggers to query a data block.
• Manipulate the query process.
• Perform validation and navigate within a form by using triggers and builtins.
• Identify the concepts related to transaction processing.
• Customize a Form Builder application by writing different types of commit triggers and overriding the default transaction processing.
• Write a flexible code by using system variables and builtins and by referencing objects directly or indirectly.

Topics Include

Unit 1: Runform Messages and Alerts

• Match the communication formats used by Form Builder with their descriptions.
• Write the code for detecting an error by using built-ins.
• Write the code to control system messages by using system variables.
• Write the code to explicitly fail a trigger by using the FORM_TRIGGER_FAILURE exception.
• Identify the uses of the Error triggers.
• Create an alert by using the Create icon in the Object Navigator.
• Write the code to control an alert at runtime by using the built-in sub programs.

Unit 2: Debugging PL/SQL Code

• Run a form module in the Debug mode by using the Debug Mode toolbar button in the Object Navigator.
• Match the PL/SQL Debugger components with the tasks that they enable.
• Set a breakpoint in code by using the Source pane of the Forms Debugger window.
• Identify the user-defined debug actions that occur automatically during debugging.
• Match the debug commands with their functions.
• Debug PL/SQL code to identify the cause of an error by using the Forms Debugger window.

Unit 3: Query Processing

• Sequence the events that take place when a query is initiated on a data block.
• Identify the sources for the different clauses of the default SELECT statement.
• Write the code for a Pre-Query trigger at the data block level.
• Write the code for a Post-Query trigger at the data block level.
• Implement query array processing in a Form Builder application.
• Write a code for a trigger to fire in the Enter Query mode by using the SYSTEM.MODE variable.
• Match the transactional triggers that override default query processing in Form Builder with their characteristics.
• Match the block properties with the associated built-ins that can be used to manipulate query information.

Unit 4: Validation and Navigation

• Sequence the steps of the validation process used by Form Builder.
• Set the Validation Unit property of a form by using the pop-up menu.
• Validate a value entered in an item by using a List Of Values (LOV).
• Write the code for a trigger to validate user inputs at different levels.
• Match the built-ins for validation with their functions.
• Sequence the Form Builder navigation units according to their navigation hierarchy.
• Match the navigation properties with their characteristics.
• Match the navigation trigger types at different levels with their uses.
• Write the code for the When-New-Object-Instance trigger at different levels.
• Specify the built-ins used for navigation given their functions.

Unit 5: Transaction Processing

• Identify the events that take place during the different phases of transaction processing.
• Sequence the events that take place during commit processing.
• Match the different types of commit triggers with the conditions under which they fire.
• Match the different types of commit triggers with their common uses.
• Write a Pre-Delete trigger to implement a validation before the deletion of a row.
• Write a Pre-Insert trigger to assign sequence numbers to records.
• Write a Post-Update trigger to record audit information about the changes applied to base tables.
• Write the code to test the result of a DML operation in a trigger by using the attributes of PL/SQL implicit cursors.
• Identify the rules followed by Form Builder while issuing DML statements during commit processing.
• Write an On-Logon trigger to override the default logon process.
• Identify the different ways to run Form Builder against non-Oracle data sources.
• Match the commit status values returned by different system variables with their implications.
• Write the code to manipulate the commit status of a record by using built-ins in the code.
• Implement array DML processing in a Form Builder application.

Unit 6: Writing Flexible Code

• Identify the benefits of writing flexible code.
• Write the code to determine which block should have the input focus by using system variables in the code.
• Write the code to perform an action based on the status of the current block by using system variables in the code.
• Write the code to obtain information about the current application by using the GET_APPLICATION_PROPERTY built-in.
• Write the code to modify the properties of an item in the current application by using the SET_ITEM_PROPERTY built-in.
• Identify the benefits of referencing objects by using their object IDs.
• Reference an object within the initial PL/SQL block by using its internal ID.
• Reference a local object outside the initial PL/SQL block by using its internal ID.
• Identify the characteristics of the built-in subprograms used to indirectly refer to objects.

Duration

8

Minimum Requirements

The CDROM version of this course requires:

• At least a 486DX 33Mhz CPU.
• Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
• At least 8MB RAM.
• At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).
• At least a double speed CDROM drive.
• An MPC compliant sound card with attached speakers or headphones is recommended (Currently only the CDROM version supports audio).

• At least a 486DX 33Mhz CPU.
• Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
• At least 8MB RAM and 22MB available hard disk space or file server space.
• At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).

Media

CDROM