Creating form views

To duplicate a form view

1. Open a form in Developer Studio.
2. Select the appropriate form view by clicking its tab at the bottom of the form editor.
3. Select Form > Duplicate View.
4. In the Copy View dialog box, select the View Type and click OK.
   • Standard—A view that can be displayed in a browser.
   • Web - Alternate—A view that uses fixed field positioning.
     Web - Alternate views are available for special purposes and for backward compatibility with previous releases. These views are not needed in version 6.3 and later versions. Use them for compatibility with earlier versions of the Mid Tier. If there is a Web - Alternate, that view is selected first for a browser, unless the Standard view is the default preference set in the Mid Tier Configuration Tool. For more information, see Configuring-general-mid-tier-settings.
5. Click the form view tab at the bottom of the form editor to select the new view.

6. In the Properties tab, modify the properties listed in the following table, as appropriate.

   Property	Description
   View ID	A unique identifier for a form view. This value is automatically generated by AR System and can be changed to a different unique identifier before saving the form view for the first time.
   Label	The label for the view. The Label, Locale, and View Type fields together define a unique identifier for the view. The client uses the label to identify the user's preferred view. For more information, see AR-System-installed-forms. When a view is created, a label is assigned automatically to the new view. You can change the label. There is no enforced convention for specifying labels, but it is helpful to make the name descriptive and indicative of the view's function consistently across forms. For example, you might create a "Manager" view for all forms in an application. Labels can be as many as 80 characters, including spaces. Names can include double-byte characters, but avoid using numbers at the beginning of the name. Note:If you want a specific view (other than the default set in Developer Studio) to be displayed in a browser by using a URL, make sure the label is unique.
   Locale	Defines the view's locale. When a view is created, the Locale field is empty. If left blank, the locale of the user's operating system is assumed for the view. To specify a locale for a view, click the cell for the Locale field and select the preferred locale from the list. The Locale field associates a language and country dialect with a view following the format: language_country. Selecting only the language includes all variations of that language. Conversely, selecting fr_CA (French, Canada) defines a view for Canadian French speakers, while selecting fr includes all French speaking countries. Different views for different locales should have the same Label, and the correct locale for the user is automatically opened.
   View Type	The view type that was selected from the Manage Views - Copy View To dialog box when copying the view. Choices are: Standard (Recommended) Web - Alternate (Fixed) This field cannot be modified.
   Master View for Server Processing	Defines if the view is used for processing to retrieve field labels and selection value aliases (not database values). A view that has the property value as true is returned by the server when an alias needs to be returned for a form, for example, in the object list. Certain tools (such as data dictionary menus, active links that display a list, and application commands) query the data in forms and use these labels and aliases. For example, the ODBC driver might use field labels and selection field aliases to generate reports. Similarly, report qualifiers are validated using these labels and aliases. Important: ODBC drivers are not supported in SaaS environments. For on-premises deployments, we do not recommend using ODBC drivers. To specify the view that should be used as the master for a particular locale, click the cell for the Master field, and select True from the list. You can set only one view per locale. It is best to specify as Master the view that contains most, if not all, of the fields and aliases required for processing. If no view is specified as the master, the default view is used. If neither a master or default view exist, the system selects a view at random.

   The Label, Locale, and View Type properties do not need to contain unique values, but the combination of the three fields must be unique to each view.

7. To set a default view, click in the form editor and select Form > Set Default View.
8. In the Choose Default View dialog box, select a view from the View Label list, and click OK.
   The default view is the view displayed to a user when a request for a form is made and no user preferences is set. An exception to this rule is seen in a browser; if no user preference is set but the configuration preference is set to a web view, the web view is chosen.
9. To open a view, click its tab at the bottom of the form editor.

10. Select File > Save to save the form with the new form view created.

    To create a blank form view with no core fields, select Form > Create New View instead of Form > Duplicate View.

To change which view is displayed in the form editor

You can set any view as the default view. Use the following procedure to change which view is currently displayed.