Power Forms
Power Forms
A power form is a web application form that enables users to view multiple,
interrelated views of data, grids, and tab pages on one form and to pass logic
among them. The tab pages can have their own business views, and these business
views can communicate with each other and can update data based on selection and
changes that occur in other business views on the form. Power forms are designed
for advanced end users.
Advantages:-
Multiple views on a form.
Multiple grids on a form.
Multiple tab controls on a form.
Tab pages with their own business views.
Business views that communicate with each other and are updated based on selection
and data changes that occur in other views on the same form.
Power Form Types
The types of power forms are:
• Power Browse.
• Power Edit.
• Reusable Browse subform.
• Reusable Edit subform.
Power Browse Form
Similar to a Find/Browse form, a Power Browse form is designed only for browsing
data. Editing capabilities are not available on this form.
Power Edit Form
Similar to a Headerless Detail form, a Power Edit form is designed for browsing
and manipulating data.
Reusable Browse and Edit Subforms
Reusable subforms are discrete objects in the system that represent one data
view. Reusable subforms are referenced through other applications with aliases.
Subforms own the data flows between the interface and the database.
Power Form Performance
Power forms work best when you use an object-oriented design to create them. When
you design modifications or applications, you need to identify objects (subforms),
how the objects interact with each other (business logic or actions), and when
their attributes (variables or fields) interact or change (states). This design
is necessary to minimize the data passed between parent and child forms.
Power Form Key Standards
When using Power forms and subforms to create an interactive application, follow
these key standards:
• Do not implement search and edit use cases on the same form.
• Avoid toolbars on Power forms.
If your application includes a hierarchical layout of subforms and these subforms
include push buttons, do not use the toolbar. Hide the toolbar and provide form and
subform level push buttons instead. Toolbars should be avoided as much as possible
in 8.12 applications
• Follow a standard naming convention.
For example: <Application Title> - <Verb> <Object Name> for Requisition Inquiry -
Search for Requisitions.
• Title all subforms, unless they contain tabs.
• Name grids so that the displayed information is clearly identified, unless the
grid appears alone on the form.
Power Form Types
The Power Browse and Power Edit forms have extended functionality when subforms
are embedded or referenced. Using power forms to create applications has many
advantages. For example, applications are usually characterized by a sequence of
forms. Typically, a user launches an entry form and then, to update information or
find related data, must navigate through a series of interconnected forms. Power
forms eliminate these navigations by enabling the developer to place subforms on
power forms.
The general properties of Power forms are:
• All regular controls except a parent-child control can be placed on a power form.
• Multiple tab controls are permitted.
• The maximize grid feature is supported for all grids.
• Power forms contain both vertical and horizontal scroll bars.
• Only power forms can contain subforms.
• Power forms run only on the web.
Power Browse Form
The Power Browse form enables:
• View-only.
• Subforms.
Power Browse forms with a business view should always have a grid with at least one
column.
Power Edit Form
The Power Edit form enables:
• Data modification.
• Data browsing.
• Subforms.
Power Edit forms without a business view have the characteristics of a Headerless
Detail form. Power Edit forms with a grid enable users to update and enter multiple
records simultaneously.
The Power Edit form enables:
• Data modification.
• Data browsing.
• Subforms.
Power Edit forms without a business view have the characteristics of a Headerless
Detail form. Power Edit forms with a grid enable users to update and enter multiple
records simultaneously.
Subform Types
The two subform types are:
• Standard subforms.
• Reusable subforms
Subforms can exist as discrete objects in the system. You can place the subform
itself on a power form; this action is referred to as embedding. You can also
reference an existing subform on a power form with an alias; this action is
referred to as reusing. Typically, you reuse subforms that are designed to appear
on numerous forms, such as the display of address book information. In this way,
you can more easily standardize the interface.
