|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:
A headerless detail form is used to update and enter records that have information that is common to all records in a selected group. This form type (as well as the header detail form type) is referred to as a transaction form.
These property values are particularly significant in the design of the headerless detail form:
The fetch property is important because of its effect in data display during runtime. You must enable Fetch on Grid Businessview to populate the grid. Similarly, enable Update on Grid Businessview to enable the commitment of modified grid records.
These events can occur on the headerless detail form during runtime:
Dialog is Initialized
Post Dialog is Initialized
Grid Record is Fetched
Last Grid Record Has Been Read
Clear Screen Before Add
Clear Screen After Add
Write Grid Line-Before
Write Grid Line-After
XAPI Subscribe Event
This section discusses how runtime processes headerless detail forms. This section discusses form-level runtime processing only. Much of the runtime processing for the headerless detail "form" actually occurs on the level of the grid control, however.
When a headerless detail 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:
This list discusses how runtime clears the form in preparation to display retrieved data:
If the form was called in Copy mode, clear the key (primary index) controls for which the Do not clear after add option was enabled.
If the form was not called in Copy mode, clear all FCs for which the Do not clear after add option has been disabled.
Fire the Clear Screen Before Add event.
Fire the Post Dialog is Initialized event.
The Find button is a standard button on headerless detail 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 control. After reloading the grid with the fetched data, runtime fires the Post Button Clicked event.
OK is a standard button on headerless detail forms that appears by default. It causes runtime to validate the information on the form and update or add it to the database through JDEKRNL function calls.
This flowchart illustrates the initial tasks that constitute runtime processing for the OK button:
This flowchart expands on how runtime populates the grid during OK button processing:
This flowchart illustrates how runtime processes any mode changes during OK button processing:
This flowchart illustrates how runtime completes the form close process during OK button processing:
The Delete button is a standard button on headerless detail forms that appears by default. The actual delete from the database does not occur at this point. Runtime verifies the intention to delete when the user clicks the Delete button, and then commits the deletion when the user clicks the OK button. Consequently, if the user clicks the Cancel button, the records are not purged from the database.
The Cancel button is a standard button on headerless detail 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 cancels any media objects that might be open. Also, if a manual transaction is in process, runtime attempts to cancel it as well. Then, runtime fires the End Dialog event and initiates the dialog close process.
Headerless detail can be closed either by the user (typically by clicking the OK or Cancel buttons) 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 BC for database commit.
Terminate error and thread handling.
Free all form structures.
Destroy the window.