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.
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.
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: -
Most of the posts in this blog cater solutions/suggestions/workaround to issues for specific tools release or JDE E1 version and are just information only. Please be carefule while applying it in your environment. JDEthread will not be responsible for any data loss or spec corruption (if any).