Form Templates can have multiple views. A view is a file that is an alternative version of the default Form based on the Form Template. You can create a view when you want to customize a Form for a specific purpose. For instance, you can create a custom view that hides a field that you do not want to use. After you create a custom view, you can view it or specify which users or groups receive this view by default when they access the Form.

Like Form Templates, views are files (in either HTML or PDF format) that you add to Content Server like any other object.

	Note: You can add views to a template only if your Content Server installation includes the Web Forms module, the PDF Forms module, or the eForms module. If you add a version to a Form Template that has different fields than the original, you must update any views associated with the Form Template to make them conform to the new version.

Specifying the View Type

When adding a view, you are prompted to specify the view type.

Using <Read Only> and <Print> Views

There are two custom view types that add functionality to the Forms module, <Read Only> and <Print>.

A <Read Only> view enables users to view a Form, but prevents them from making changes. Before you create the Form, you must configure the permissions to be read-only on the Form Template on which the Form is based.

Adding the <Print> view to a Form Template adds a Print Form command to the Functions menu of Forms created with the template. This function sends Form data to a view that you design specifically to be printed.

	Note: When adding these view types to a Template, you must name them using the angle brackets (< >).

Specifying Optional Fields

User information

Content Server automatically fills in some fields with the data that it stores about the user who opens the Form. For example, for the Form field LL_UserLogin, Content Server supplies the current user's Content Server user name when the Form is opened.

The following names for user data fields are reserved (all are case sensitive):

• LL_UserLogin, the user's login name

• LL_UserFirstName, the user's first name

• LL_UserMiddleName, the initial of the user’s middle name

• LL_UserLastName, the user's last name

• LL_UserFullName, the user's full name

  	Note: The value of the LL_UserFullName field is based on the following user properties for the current user: First Name, Middle Initial, and Last Name. If values are not entered for each user property, LL_UserFullName displays the values that are entered. For example, LL_UserFullName might display a user’s first name and middle initial, or just a middle initial or last name. If no values are entered for First Name, Middle Initial, and Last Name, LL_UserFullName is blank.

• LL_UserTitle, the user's title

• LL_UserMailAddress, the user's email address

• LL_UserContact, the user's phone number and extension

• LL_UserGroupName, the department to which the user belongs

	Important: Content Server always returns data for the current user in the reserved fields. If you want to store this information in Content Server, allow the Form to be edited later, and maintain a list of each user who edits the information, design a Form that contains the logic to store the data in another field by copying or appending the data in the LL_UserLogin field. If you try to store the user data by creating a field on the Form Template named LL_UserLogin, the value in that field will be overwritten with the current user's Content Server user name each time the Form is edited.

Form template information

Content Server automatically fills in some fields with data that it stores about the Form template. You can use the replacement tag LL_TEMPLATEID in text fields where you want the Object ID of the form template to appear as the default value when the form opens.