Now that selecting elements, element options, and field groups have been discussed, the elements found in the Form Elements accordion can be reviewed in detail.
This is a text box input with optional label. A dialog box requires you to choose the field to which it will be mapped when you place the element. You may select any existing field or create one.
Note that sometimes a text box is not a text box. If the mapped field is augmented by a type ahead or dropdown Datalink through the Content Type, then an input element matching the Datalink is used instead of an actual text box.
The label element is just a label. It has no associated input or field map, and the label is not in a container. It is used to display static text, like instructions, on a form.
This element includes an optional overall label and a set of radio buttons, each with individual labels and values. When presented to a user, he or she may select any one of the options.
The field chooser dialog appears when this element is placed, through which a field is mapped. The value specified here in the form designer corresponding to the selected choice is stored in the mapped field at run time. The labels are displayed next to each radio button in the form. In many cases, the values will differ from the labels. For instance, you may show options with user-friendly descriptive labels but store abbreviated or numeric values, which are more conveniently processed in workflow.
Initially, the element includes three choices, each with a label and a value.
The label is displayed on the form, and the value is stored in the mapped field. All values therefore must be compatible with the field type: i.e. you can’t store, “text” in a Date field.
You can remove or add choices with the and symbols, respectively.
Clicking a radio button in the Value accordion designates the default selection.
The Field Layout selection allows you to arrange the choices Side by Side (horizontally) instead of in one column (vertically), as shown here.
Note that only the label of this element may be resized. The individual choices are automatically sized to their respective labels, and the element container is automatically sized to its content. Thus, you cannot select the container or each option individually.
The “Predefined Value” is the default state of the checkbox when a new form instance is created. The Help Text is displayed as a tooltip when the user moves the mouse over the element.
The Checkboxes element is similar to the Multiple Choice element in many respects. It must be mapped to a field. It combines an optional master label with a collection of input elements with individual labels and values. There are initially three checkboxes, but you may add or delete. All of the values must be compatible with the type of the mapped field. One Column and Side by Side layouts are available.
No part of the element can be resized except for its master label, so the container and the individual choices cannot be selected.
In this example, the mapped field is an Integer so the default values are all integers.
The distinction between Checkboxes and Multiple Choice is that the former is not restricted to one selection; the user may check none, one, two… or all of the checkboxes.
When no box is checked, no value at all is stored for the mapped field. When multiple boxes are checked, multiple values are stored for the field. Thus, in the example above, if a user checks Phone and Email, two distinct values (1 and 4) are stored for the mapped field.
Workflow designers partial to bitifield operations can combine integer or long checkbox values into a single field using the Sum operation in the Aggregate Task. If doing so, ensure that only powers of 2 (i.e. 1, 2, 4, 8, 16, 32, etc.) are used as individual values.
The Dropdown element is a label and a dropdown input (a Select element in HTML). The dropdown must be mapped to a List type field.
The choices displayed are driven by the specified list.
Like the Text Box, if the mapped field is set to use a dropdown or type ahead DataLink via the Content Type, then the DataLink determines the choices and the type of input element displayed.
The section break is a horizontal line optionally with a label above it. It has no field map and no input. It may be resized as desired. If expanded vertically, it will appear as a rectangular box rather than a line.
The Name element is a short-cut for creating a field group, called “Name”, which includes two text fields called “First Name” and “Last Name”, and then placing that field group element onto the form. It is the equivalent of creating the two fields manually on the Fields admin page, then creating the Field Group, and placing it. If the field group already exists, it just places the element.
Similar to “Name”, this is a short-cut for creating a field group (if it doesn’t already exist) and placing it on the form. The “Address” field group has the six text fields shown here, arranged (by default) as shown below.
This element is simply a Text Box pre-configured for the standard Title field.
This element is a multiline Text Box (a TextArea in HTML) pre-configured for the standard Keywords field.
The element includes a label, which may be hidden, and a value area that will render basic HTML markup, such as a bulleted list. One of the Settings in the Verify Field Group Task allows the result to be formatted with HTML, and this is how such a result is displayed in a form.
When selected, only the label is resizable. The width of the container will adjust to the width of the label, and at runtime, the height of the container will adjust to the value of the Status field.
Similar to the Text Box element, the Number element prompts for a field to which it will map. The field must be a numeric type (Decimal, Integer, or Long).
This variation of the Text Box element is labeled, “Email” as a convenience when placing this commonly used input on a form.
This is another Text Box variation with an alternate label.
Likewise, this is a Text Box variation with an alternate label.
Like Number, this is a specialized input element. A Date field must be mapped to it. A date picker will be available when a user is filling in this element on a form document.
Like Date, except that it maps to Date/Time fields and provides a date/time picker.
Like the Dropdown element, the ComboBox is a label and a list-driven input, and it must be mapped to a List type field.
A user may choose from the list or enter their own value, ignoring the choices.
Like Text Box and Dropdown elements, the behavior of the ComboBox changes when the mapped field is driven by a type ahead or dropdown DataLink. The DataLink determines the type of input element displayed and the choices available therein.
Use the image element to include a logo or other picture on the form. It is not mapped to a field. Rather, an image must be specified here in the designer. You can choose an image previously uploaded or upload a PNG or JPEG file.
The element can be resized and the image will be stretched to fit it. Be mindful of aspect ratio; you don’t want logos or other images to appear too tall or short.
Add this element to allow form-fillers to add additional content to a form, such as receipts to an expense report.
When a user fills in the form, the File Upload element will initially have one “Choose File” button. If a file is selected, another appears, allowing multiple files to be uploaded (attached) to the form in one operation.
The file(s) are uploaded when the form is saved and are added as additonal content items to the end of the document.
Note that after saving the form, the name(s) of the files will no longer appear in the File Upload. Further, attached content will not appear when the form is in “Form Edit” mode. The attached files will be visible when the user leaves Form Edit mode.
Attached content is queued for rendering, so that in most cases, it can be viewed in the DocStar image viewer after a short period of time.
See Technical Details at the end of this guide for more information on content items and forms.
The Created On element is preconfigured to display the Created On property.