Defining and managing form views

A form view is what users see when they open a form in a browser. Form views are versions of an original form and can exist only after the initial creation of a regular form. (For information about creating regular forms, see Defining-forms-to-hold-and-display-data.)

Every form has one default view. As an administrator, you can create additional views of the same form, each defined for a unique purpose, locale, or view type. You specify default views to determine which view of a form opens in a browser. An administrator might define views for the following environments:

  • Different locale—Views for specific languages or regions.
  • Different user roles—Customized views for requesters, frontline staff, backline staff, or managers.
  • Hardware dependencies—Views that allow for the size of a monitor, such as laptop or desktop. This is useful for legacy systems without scalable fonts.
  • Purposes other than a form—Views that are used only when invoked as a dialog box using an active link.

Related topics

Defining-application-menus

Defining-forms-to-hold-and-display-data

This section covers topics related to defining and managing form views. Topics include:

Action

Reference

Learn to select a form view. 

Learn to create a form view.

Learn to modify a form view.

Learn to set and define form view properties.

Learn to arrange fields in a form view.

Learn to add or remove a field from form views.

Use layout to set the tab order of fields in a form view.

Use Developer Studio through the product library.

Learn about displaying a AR System form in a portlet.


For additional information specific to web views, see Creating-and-managing-fields.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*