Contact IT Support

 

 

 

 

 

 

Form Fields in Formstack

Formstack includes a wide range of customizable field types that allow you to collect data efficiently and accurately. Selecting the right field type improves clarity, reduces errors, and helps ensure a better experience for the individual completing the form.

Whether you are building a survey, service request, registration form, or internal workflow, this guide explains the types of fields available and how to use them effectively in the KAUST environment.

Common Field Types and When to Use Them

Short Answer
Used for single-line inputs such as name, building number, course code, or document title.
Example: Lab Safety Officer Name

Long Answer
Used for comments, justifications, or open feedback.
Example: Describe the nature of the research project

Email
Automatically validates that the input is in email format.
Example: PI Email Address

Phone Number
Formats numeric entries and allows country code options if enabled.
Example: Emergency Contact Number

Dropdown
Displays a list of predefined options. Allows one selection.
Example: Select your academic division (e.g., BESE, CEMSE, PSE)

Checkboxes
Allows the selection of multiple options.
Example: Select the lab equipment you need access to

Radio Buttons
Displays a list of options where only one can be selected.
Example: Are you a student, faculty member, or staff?

File Upload
Lets form responders attach files such as CVs, travel documents, or signed forms.
Example: Upload a scanned copy of your purchase request

Date and Time
Captures dates, times, or both. Can be configured to prevent selection of past dates.
Example: Preferred date for facility tour

Number
Restricts the input to numeric values only.
Example: Number of devices to be ordered

Signature
Captures digital signatures using mouse or touch input.
Example: Requestor Signature on Equipment Booking Form

Section Header
Divides long forms into logical sections. Helps with visual structure and readability.
Example: "Section 2: Project Details"

Hidden Field
Used to store values that are not visible to the responder, such as workflow flags, identifiers, or source tracking.
Example: Auto-populated KAUST ID or form origin

Fillable Table
Allows structured, repeatable data entry in table format.
Example: List team members, their roles, and badge numbers

Tips for Using Fields Effectively

  • Use Labels Clearly: Always provide a descriptive field label. For example, instead of "Name", use "Full Name of Researcher".
  • Use Help Text to Reduce Errors: Add brief instructional text beneath the field for clarification. For example: "Please enter your KAUST email only".
  • Minimize Required Fields: Only make fields required if they are essential. Too many required fields can cause drop-offs or frustration.
  • Group Fields Logically: Use Section Headers to separate parts of a form, such as “Personal Details”, “Project Information”, and “Attachments”.
  • Use Conditional Logic When Needed: Hide or reveal fields based on earlier answers. For example, only show a funding code field if “Faculty” is selected as the role.
  • Avoid Placeholder-Only Labels: Placeholders are not a substitute for labels. Always use a proper label above each field.
  • Be Mindful of File Upload Limits: Each uploaded file must be under 25 MB. For larger files, consider using OneDrive.