Defining form views for the customizable home page
- Use a display-only form designed for this purpose.
To optimize performance when the home page loads, avoid using a new view of a large and complex existing form. - For performance reasons, minimize the form size, using as few fields and workflow definitions as possible. Add a single field to hold the data that will appear in the home page panel.
For example, add a table field to display records from another form, or a data visualization field to display a flashboard. - Use chunking for table fields.
- Use field types that respond well to resizing. These include table fields, tree fields, view fields, data visualization fields, and panel holder fields.
- In the Appearance properties for the form view, set the Layout Style property to Fill. This allows the field contents to expand and shrink as the panel changes size.
If the field is a panel holder, make sure that the Layout Style property for the panel showing the main data content of the form is also set to Fill. - In the view properties, set the Results Banner and Web Toolbar properties to Hidden.
- Avoid creating forms for the customizable home page that support user data editing. The panel display size is variable, and pop-up editors can be clipped by the panel that is hosting the form.
- Avoid using workflow that fires on window open, load, or display. Doing so can cause unneeded queries to the AR System server. If multiple items of data are needed to render the form, use a Service workflow action call to combine these queries into a single call to the server.
- Use workflow to automatically populate data in the display-only form.
Alternatively, add a Refresh button to the form to allow the user to update the data manually.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*