TX Forms Quick Reference: Field Types and Content Blocks Glossary
Input Field Types
|
Field Type |
Desription |
Common Uses |
Configurable Options |
|---|---|---|---|
| Address Widget | Group of fields: Street, City, State, ZIP, Country | Mailing/Other Address | Auto-maps to appropriate Salesforce fields, Required, Conditional Logic |
| Autocomplete | Suggests possible matches as the user types. | School Name | Required, Answer List, Filter Field, Filter Value, Conditional Logic |
| Validated email address input | Contact Email | Required, Enable Email validation, Conditional Logic | |
| Number | Numeric-only field, with optional decimals | SAT Score, GPA |
Min/Max Values, Required, Conditional Logic |
| Phone Number | US/international phone number | Mobile, Home Phone |
Required, Max Length, Conditional Logic |
| Picklist (Single) | Dropdown or radio buttons for a single choice | Program Interest, State |
Values, Required, Conditional Logic, Option Groups |
| Picklist (Multi) | Checkboxes or multi-select dropdowns | Source |
Values, Required, Conditional Logic, Option Groups |
| Text | Single-line input for brief text | Name, City, Nickname |
Required, Max Length, Conditional Logic |
| Text area | Multi-line input for extended answers | Comments, Additional Info |
Required, Max Length, Conditional Logic |
Visibility and Logic Features
|
Feature |
Description |
|---|---|
| Conditional Visibility | Show/hide fields or sections based on user responses |
| Default Values | Set preset values via URL parameters |
| Required | Mark field as mandatory before submission |
Special Function Blocks
|
Block Type |
Description |
Common Uses |
Notes |
|---|---|---|---|
| Hidden Field | Field that isn’t shown to user but collects/stores data. | Source Tracking | Accepts default values not user-editable |
| Display Text | Read-only text block with optional HTML formatting. | Instructions, Info Notices | Supports rich text, links, bolding, etc. |
| Disclaimer | Legal, privacy, or policy info requiring user acknowledgment. | Privacy Policies, FERPA | Appears as a non-interactive text block |
| Divider | Thin horizontal line separating sections visually. | Grouping, Aesthetic Spacing | No configuration required |
| Upload | Enabled user to upload a file. | Resume, CV | Define accepted File Types |
Access and Submission Controls
|
Setting |
Purpose |
Example Use Case |
|---|---|---|
| reCAPTCHA | Prevents bot/spam form submissions | All public-facing forms |
| Access Key | Requires a code to unlock and submit the form | Internal use only, invite-only forms |
| Confirmation Message | Displayed upon form submission | “Thank you for your interest!” |
| Redirect URL | Sends user to another webpage after submission | Event confirmation page, tracking link |
Data Mapping Considerations
- Each input field must map to a Salesforce field on a standard or custom object.
- You can map fields to:
- Contact
- Contact Child Objects (available in the picklist after the Contact [Student] object).
- Multi-object forms require careful planning—avoid mapping fields to multiple objects with overlapping purposes.