E-forms will support setting the X-UA-Compatible value in meta tags. However, this setting should be thoroughly tested in a testing environment before being implemented system-wide.
E-Form templates are written in HTML. HTML code can be written directly in a program such as Notepad®, or in an HTML editor, such as Microsoft Expression Web.
E-Form Templates contain input fields that are mapped to document Keyword Types and other system values. E-Forms can also contain information that is not mapped to keywords or stored in the database. This information is stored with the form and is available for viewing, though the system does not search documents based on this text.
The following limitations apply when configuring E-Form templates:
-
When mapping fields in a form that contain either keyword data or non-keyword data, the "name" attribute must be used in order to store data.
-
If you have more than one field with the same name property (e.g. <input name="Text1" /> and <input name="Text1" />), the first instance overwrites the value in any subsequent instances.
-
An E-form document will continue to use the HTML template revision that was used when the E-Form was created.
Information entered into properly configured form fields is saved as Keyword Values or system values on the E-Form. The most important aspect of forms creation is the proper mapping of form fields to document Keyword Types or system values. For more information, see Mapping Form Fields to Keyword Types.
The method of identifying Keyword Types and system values in the HTML form depends on the HTML editor. In the following example, the map code for the Keyword Type PO Number is mapped in Microsoft Expression Web:
