|JD Edwards EnterpriseOne Tools Development Tools: Form Design Aid Guide
Release 8.98 Update 4
Part Number E14706-02
|PDF · Mobi · ePub|
This chapter contains the following topics:
Similar to find/browse forms, parent/child browse forms are used to query business views (BVs) and select records from BVs for operations. However, instead of a default grid control, parent/child browse forms contain a default parent child control instead.
These events can occur on the parent/child browse form during runtime:
Dialog is Initialized
Post Dialog is Initialized
Grid Record is Fetched
Write Grid Line-Before
Write Grid Line-After
Last Grid Record Has Been Read
XAPI Subscribe Event
This section discuses how runtime processes parent/child browse forms.
When a parent/child browse form is called, runtime initializes these items in this order:
Error handling process
Business view columns (BCs)
Form controls (FCs)
Event rules (ER) structures
This flowchart illustrates the tasks that runtime performs after initializing these objects to complete dialog initialization:
Data selection and sequencing occurs at the control level and ultimately leads to the population of the parent/child control, provided runtime encounters no errors.
The Find button is a standard button on parent/child forms that appears by default. When the user clicks it, runtime fires the Button Clicked event. If no errors exist in the filter fields, runtime performs data selection and sequencing for the grid and tree controls. After reloading the grid and tree with the fetched data, runtime fires the Post Button Clicked event.
Select is a standard item that is automatically placed on parent/child browse forms. No default processing exists for Select on parent/child browse forms. It acts as a user-defined item.
The Close button is a standard button on parent/child forms that appears by default. When the user clicks it, runtime fires the Button Clicked and Post Button Clicked events in immediate succession. If no errors occur, runtime attempts to close all of the modeless child forms, if any exist. If any of these child forms cannot be closed, the Close button process is terminated. Otherwise, runtime fires the End Dialog event and initiates the dialog close process.
Parent/Child can be closed either by the user (typically by clicking the Close button) or by the system. After performing any control-level close processing that might need to occur, runtime closes the form. If the event has not already occurred, runtime fires the End Dialog event. Then it performs these tasks in this order:
Load form interconnect data from BCs for database commit.
Terminate error and thread handling.
Free all form structures.
Destroy the window.