The Order Entry application contains several forms. The inventories form uses an LOV that is based on a record group that queries the Warehouses table to return a warehouse ID. Several of the forms use LOVs that are based on the same query. You decide to centralize the creation of the record group to the entry form of the application, which opens all the other forms, for example, to open the inventories form, there is a When-Button Pressed trigger on the inventories button with the following code;

OPEN _FORM ('inventories');

in a When-New-Form-instance trigger for the entry form, you create the warehouse_rg record group by

using the CREATE_GROUP_QUERY built in with the following arguments:

('warehouse_rg' , 'SELECT ALL WAREHOUSE.WAREHOUSE_ID, WAREHOUSE.WAREHOUSE_NAME FORM WAREHOUSE order by warehouse_name);

You also populate the record group in this trigger.

What must you do to make this record group available to the inventories form and the other forms?

A. in the When-New-Form-instance trigger for the entry form, add a values for the SCOPE argument of CREATE_GROUP_QUERY.

B. in the entry form, move the record group code to the end of the When-Button-Pressed triggers for the buttons that open other forms, so that the record group is created and populated immediately after OPEN_FORM is called.

C. in the entry form, move the record group code to the beginning of the When-Button-Pressed triggers for the button that open other forms, so that the record group is created and populated just before OPEN_FORM is called.

D. in the When-Button_Pressed triggers of the entry from the buttons that open other forms, add a value for the SESSION argument of OPEN_FORM.

E. in the other forms, refer to the record group as: global.warehouse_rg.

In Forms Builder, the iconic buttons on the form are blank, but when you click Run Form the form appears in the browser with Images in the iconic buttons.

What are two things that you can check to track the source of this problem?

A. forms Builder runtime preferences

B. the UI_ICON setting in the operating system

C. the iconpath setting in the Forms registry file

D. the UI_ICOM_EXTENSION setting in the operating system

E. the iconextension setting in the Forms registry file

F. the FORMS_PATH setting in the Forms environment file

G. the classpath setting in the operating system

You are planning the alerts that are needed for your Human Resources application. You wish to display the following in alerts:

*

A message to inform the user about being at the just record

*

A warning about a potential conflict with the data just entered

*

A message to display a validation error to the user

*

A warning that the salary is out of range and that asks whether the user wants to correct it

You want the note symbol ( ) to appear on alerts that display only informative messages, the

warning symbol to appear on messages where you will allow the user to continue despite some data problem, and the alarm boll symbol to appear where the user will not be allowed to continue without correcting the situation that caused the alert to be displayed.

You want to define the minimum number of alerts possible and customize them at run time.

Which alerts should you define?

A. One Note style alert and caution style alert

B. One Note style alert and one Stop style alert

C. On Caution style alert and one stop style alert

D. On Note style alert, one Caution style alert, and one Stop style alert

E. Two Caution style alerts and one Stop style alert

On the Employees form, you do not want the cursor to enter the Employee_Id text item, which is the first item in the first block on the form. You code a Pre-Text-item trigger for that item that uses the GO_ITEM built-in to navigate to the next item.

What happens when you run the form from Forms Builder?

A. You receive a compilation error.

B. The form starts to run, but immediately closes. So If an error message Is displayed, you are unable to see it.

C. The form runs, but as soon as it appears, you receive a runtime error.

D. The form runs, but as soon as you perform any navigation, a runtime error occurs.

E. The form runs with no problem.

You have designed a form with two content canvases. The window for the first canvas was created implicitly, and you have not changed its default properties.

You want users to be able to navigate between the canvases easily while viewing both simultaneously. Therefore, you create a second window, changing only its name from the default properties.

However, when you test the form, you find that you are unable to close either window. What must you do to provide this functionality?

A. Change the second window to a modal window.

B. Code a When-Window-Closed trigger for each window.

C. Set Close Allowed to Yes for both windows.

D. Set Hide on Exit to Yes for both windows.

View the Exhibit.

The Summit menu is attached to the Orders form. The Toggle Autoquery menu item is a check box that

toggles whether a query is automatically performed when the Orders form is first invoked. If the check box

is deselected, users must manually query.

In addition to using the menu, users want to be able to toggle the autoquery preference directly from the

form. You add a button named Toggle Autoquery with the following When-Button- Pressed trigger:

DECLARE

mi_id MENUITEMS;

BEGIN

mi_id ;=FIND_ITEM ('Preferences.AutoQuery')

/* Determine the current checked static of the AutoCommit menu checkbox item And toggle the checked

state*/

IF GET_ITEM_PROPERTY (mi_id, CHECKED) = 'TRUE' THEN

SET_ITEM_PROPERTY (mi_id, CHECKED, PROPERTY_FALSE);

ELSE

SET_ITEM_PROPERTY (mi_id, CHECKED, PROPERTY_TRUE);

END IF;

END;

However, the trigger does not compile. What three changes must you make so that the trigger compiles

successfully?

A. Change FIND_ITEM to FIND_MENU_ITEM.

B. Change 'preferences.AutoQuery' to 'orders.preferences.AutoQuery'.

C. Change 'preferences.AutoQuery' to 'AutoQuery'.

D. Change 'preferences.AutoQuery' to 'ORDERS.PREFERENCES>AUTOQUERY'.

E. Change 'preferences.AutoQuery' to 'AUTOQUERY'.

F. Change GET_ITEM_PROPERTY to GET_MENU_ITEM_PROPERTY

G. Change SET_ITEM_PROPERTY to SET_MENU_ITEM_PROPERTY

H. Change PROPERTY_FALSE to 'FALSE'.

I. Change PROPERTY_TRUE to 'TRUE'.

The Orders form has three blocks: Orders, Orders_Items, and inventories. It also has a button labeled Next

Block with a When-Pressed trigger.

IF :SYSTEM.cursor_block = 'orders' THEN

GO_BLOCK('order_items');

ELSIF :SYSTEM.cursor_block = 'order_items' THEN

GO_BLOCK('inventories');

ELSIF :SYSTEM.cursor_block = 'inventories' THEN

GO_BLOCK ('orders');

END IF;

The button is not functioning correctly; it does not cause navigation to occur. What must you do to fix the

issue?

A. Change all occurrences of :SYSTEM.cursor_block to :SYSTEM.trigger_block.

B. Use system variables in the GO_BLOCK statements.

C. Change the block names to uppercase in the GO_BLOCK statements.

D. Change the block names to uppercase in the condition (IF ...THEN) statements.

E. instead of naming the block to navigate to, replace the GO_BLOCK built-in with NEXT_BLOCK

F. Move the code to a PL/SQL program unit.

There are certain errors that are specific to the Salary item on the Employees form. You want to trap these errors only when the user navigates from the Salary item.

You have a form-level On-Error trigger that traps errors that apply to the form in general, but yon additionally code an item-level On-Error trigger for the Salary item.

When testing the form, you find that the general errors are not trapped when you navigate from the Salary item. What can you do to correct this problem?

A. Call the form level On-Error trigger from the item-level On-Error trigger.

B. Call the item-level On-Error trigger from the form-level On-Error trigger.

C. Change the Execution Hierarchy property for the item-level On-Error trigger.

D. Change the Execution Hierarchy property for the form-level On-Error trigger.

E. Move all the code to a PL/SQL program unit and call it from both the form level and item level On-Error triggers.

To troubleshoot a problem with a form, you have added a call to the MESSAGE () built-in at the beginning of the When-Validate-Item trigger of the Customer_Id then in the Orders Block of the Orders form. The message simply states that the trigger is firing.

You run the form, make a change in Customer_Id, and then tab out of the item but the message does not appear. What are two possible causes for this problem?

A. The form is in Enter-Query mode.

B. The item is using an LOV for validation.

C. The validation unit of the form needs to be changed.

D. The MESSAGE () built-in is not allowed in validation triggers.

E. There is a syntax error in the call to the MESSAGE() built-in.

F. Validation for the Customer_Id item failed.

Which three statements are true about the PL/SQL Packages panel in the Forms debugger?

A. You can select an option button to view server packages.

B. You can view packages only while the runtime process executes PL/SQL.

C. You can view the values of variables that are defined in the package specification.

D. You ran select an option button to view the packages that have not yet been instantiated.