iSelfSchooling - Case Studies (FORMS II)

The FORM section consists of 16 user requirements that we will call Hands-On Oracle Form Builder. In these Hands-On, your client is a company that keeps track of its customers’ orders. You have been assigned to develop a customer order data entry application based on their requirements.

These are designed to challenge your skills in developing user’s friendly applications.

Assuming, you as a developer gathered the requirements during prototyping sessions with the client, using the Rapid Application Development (RAD) model.

Hands-On Form Builder (Internet Applications Tool)

Hands-On 07(Forms) - Manuscript

New functional requirements came in from the users. They need a horizontal toolbar to have on their Form. The toolbar should contain all the frequently used options. This will make ease of use of some options.

The following are the list of all the frequently used functions they expect to use:

Move to previous record,
Move to next record,
Add new record,
Delete current record,
Save work, and
Exit the application.

See Figure 9.

Your tasks are:

1- Adding more functionality to the application.
2- Create a horizontal Toolbar.
3- Create push button for above frequently used functions list.
4- Create and compile triggers for each push button created on step 3.
5- Run and test all user functional requirements.

FYou will learn how to: create and use horizontal toolbar, create and use the push button item, create the "WHEN-BUTTON-PRESSED" trigger, write and compile trigger, use tab canvas, use “object navigator,” use “Data Blocks,” use “Layout Editor,” use “Property Palette,” use “Run Form,” and “Execute Query.”

Figure 9

Hands-On 08(Forms) - Manuscript

On pervious Hands-On, your users only see the horizontal toolbar canvas instead of the Customer, Orders, and Items canvases. They have to drag the window in order to see their “Customer Order” application. They complain that it is cumbersome to drag the window in order to use the application. You have been assigned to fix this problem. The requirement from your client is: to make sure your layout was properly sized so your client doesn't need to drag or expand the window size.

See Figure 10.

Your tasks are:

1- Make sure the canvas was sized properly.
2- Run and test all user functional requirements.

FYou will learn how to: size your canvas, change the horizontal toolbar canvas, use tab canvas, use “object navigator,” use “Data Blocks,” use “Layout Editor,” use “Property Palette,” use “Run Form,” and “Execute Query.”

Figure 10

Hands-On 09(Forms) - Manuscript

On the "Orders" tab, your client wants to see the most recent or last customer orders. They ask you to sort the customer orders list based on their order’s date. They like to have two radio buttons to allow them to manipulate the order of displayed records by order date.

You have been assigned to create two radio buttons, Labeled "Ascending" and

"Descending" to sort displayed record order by "order date."

See Figure 11.

Your tasks are:

1- Create a Radio Group.
2- Create two Radio Buttons associated with step 1 (Radio Group).
3- Label the first Radio Button “Ascending.”
4- Label the second Radio Button “Descending.”
5- Run and test all user functional requirements.

FYou will learn how to: create and use PRE-QUERY trigger, set dynamically block property on a table's data block and execute the query using trigger, use tab canvas, use “object navigator,” use “Data Blocks,” use “Layout Editor,” use “Property Palette,” use “Run Form,” and “Execute Query.”

Figure 11

Hands-On 10(Forms) - Manuscript

It is very cumbersome for your users to assign a new customer ID to a new customer. It requires to find what the last customer ID was entered into their system; then they increment it by 1 and use that number for a new customer ID. This is not very a professional way of doing business particularly if you have multiple transactions to enter.

You have been assigned to solve this problem and automate this process. They ask you to add a sequence number to customer ID (CUSTID) starting with 200 and incremented by 1. So, your customer ID would start from 200, 201, 202, and so on.

See Figure 12.

Your tasks are:

1- Create a sequence number to generate a unique customer ID.
2- Assign the generated sequence number to each customer each time a new customer is added to a table.
3- Run and test all user functional requirements.

FYou will learn how to: create sequence object, create and use "PRE-INSERT" trigger, use tab canvas, use “object navigator,” use “Data Blocks,” use “Layout Editor,” use “Property Palette,” use “Run Form,” and “Execute Query.”

Figure 12

Hands-On 11(Forms) - Manuscript

Your client wants to have another application Form to query, insert, delete, and update their product price. They want to open the Form from their “Customer Order” application.

It is their requirement that the window size for product price should be small enough to fit on a small portion of their application. Also, it is part of their requirement to have a Push Button to click in order to open and run the product price application from the “Items” tab canvas. You should modify their application to provide such request.

See Figure 13.

Your tasks are:

1- Create the product price Form.
2- Test all it’s user functional requirements, such as insert, delete, and update.
3- Create a Push Button on the “Items” tab canvas to open the Form that created from step 1.
4- Create and compile trigger to call the Form that was created from step 1.
5- Run and test all user functional requirements.

FYou will learn how to: call another Form, create and compile triggers, use tab canvas, use “object navigator,” use “Data Blocks,” use “Layout Editor,” use “Property Palette,” use “Run Form,” and “Execute Query.”

Figure 13

Hands-On 12(Forms) - Manuscript

Now, your client desires it would be better if they could get specific history of product price rather than entire product price table. They want you to add more functionality to their application to display only current history of product price information.

Note: The current product would be defined by where the position of your cursor is.

You have been assigned to modify their application to query only history of product price information for a product rather than entire table.

See Figure 14.

Your tasks are:

1- Automate the “product price” application to query only a history of product price.
2- Pass product ID as a parameter between these two Form applications.
3- Run and test all user functional requirements.

FYou will learn how to: use and assign global variable, pass global variable from one Form to another, use global variable to execute query base on its parameter, create and use the "WHEN-NEW-FORM-INSTANCE" trigger, use tab canvas, use “object navigator,” use “Data Blocks,” use “Layout Editor,” use “Property Palette,” use “Run Form,” and “Execute Query.”

Figure 14