This chapter contains the following topics:
When you create forms, consider the recommended performance guidelines, which ensure that the forms perform optimally.
Use these guidelines as standards to increase performance for all form types:
Limit the number of columns in the grid to the minimum that is required by the application.
Limit the number of columns in the business view to the minimum that is required by the application.
Limit the number of form controls, whether hidden or visible, to the minimum needed by the application.
Use event rule variables as work fields instead of hidden form controls.
On form and grid controls, disable the data dictionary functions that are not required, such as edits and default values.
This guideline applies to both hidden and visible controls.
Limit the amount of input and output performed for each grid row to the minimum that is required for the application.
Use the Stop Processing system function whenever feasible to skip the processing of unnecessary event rules.
For temporary data storage, use the most efficient method that is available at the time.
For example, consider the relative efficiency of cache, linked lists, and work files.
If performance diminishes when you load data into a form, use media object system functions to edit and display attachments instead of enabling automatic media object functionality.
When you use media object system functions, you do not need to verify whether an attachment exists before you can display a bitmap. When you use automatic media object functionality, you must verify whether an attachment exists before you display a bitmap.
Use this guideline as a standard to increase performance for Browse (Find/Browse, Parent/Child, and Power Browse) forms.
Ensure that the sort order on the grid partially or completely matches both an index that is defined in JD Edwards EnterpriseOne software and a logical that is defined on the IBM i.
The logical AND index must contain at least all of the fields in the grid sort. The fields selected for the grid sort must be in the same sequence as the logical AND index fields. The index or logical might include additional fields that are not included in the grid sort. For example, in a partial match, the grid sort can be KIT, MMCU, and the logical and index can include KIT, MMCU, TBM, and BQTY.
Use this guideline as a standard to increase performance for header detail and headerless detail forms.
Ensure that the sort order on the grid partially or completely matches both an index that is defined in JD Edwards EnterpriseOne software and a logical that is defined on the IBM i.
The logical and index must contain at least all of the fields in the grid sort. The fields selected for the grid sort must be in the same sequence as the logical and index fields. The index or logical might include additional fields that are not included in the grid sort. For example, in a partial match, the grid sort can be KIT, MMCU; and the logical and index can include KIT, MMCU, TBM, and BQTY.