Registration forms are built from form elements — each element maps to a question type that controls how the field renders on the checkout page and what kind of answer it accepts. Every element can optionally map its answer to a Salesforce object field.
🖼️ In the Forge app: The element type picker in the form builder, showing all available question types.
Text Inputs
| Element type | Input rendered | Typical use | Notes |
|---|---|---|---|
| Text (Short) | Single-line text field | First name, company, badge name | Max 255 characters; maps to most standard Contact/Lead text fields |
| Text (Long) | Multi-line textarea | Dietary requirements, accessibility needs, bio submission | No character limit enforced in Forge; SF field limits apply |
| Single-line field with email format validation | Alternate email, company email for receipt | Forge validates format client-side and server-side before saving | |
| Phone | Single-line field with phone format hint | Mobile number for event day updates | Stored as plain text; no international format enforcement by default |
| Number | Numeric input | Guest count, table number, years of experience | Accepts integers and decimals; maps to SF Number/Currency fields |
| URL | Single-line field with URL validation | Speaker website, LinkedIn profile, portfolio link | Validates that the input begins with http:// or https:// |
Choice Inputs
| Element type | Input rendered | Typical use | Notes |
|---|---|---|---|
| Picklist (Dropdown) | Single-select dropdown menu | T-shirt size, meal preference, track selection | Options are defined in the element settings; can also map to a SF picklist field to inherit its values |
| Multi-Select Picklist | Checkbox group allowing multiple selections | Session interests, dietary restrictions (select all that apply) | Answers stored as semicolon-delimited string to match Salesforce multi-picklist format |
| Radio Buttons | Mutually exclusive radio button group | How did you hear about us?, Registration type | Renders as large tap targets on mobile; prefer over Picklist for fewer than 6 options |
| Checkbox (Single) | A single boolean checkbox | Consent to recording, agree to terms | Checked = true; maps to a SF Checkbox field |
| Big List Lookup | Searchable lookup with typeahead, powered by Salesforce data | Company/organization lookup, Salesforce Account lookup | Requires a SF object and display field to be configured; best for large datasets (100+ options) |
Date and Time
| Element type | Input rendered | Typical use | Notes |
|---|---|---|---|
| Date | Date picker (calendar popover) | Arrival date, travel date, date of birth | Stored as ISO date string; renders in the browser locale format |
| Date/Time | Combined date and time picker | Preferred meeting time, appointment slot | Stored in UTC; displayed in the event timezone |
Layout and Static Content
| Element type | What it renders | Typical use | Notes |
|---|---|---|---|
| Section Header | A styled heading that divides the form into labelled sections | Group related fields visually | Not a data field — answer is never captured; no SF mapping |
| Static Text / HTML | Rich-text content block rendered inline in the form | Terms and conditions text, instructional copy, event-specific notices | Not a data field — answer is never captured; supports basic HTML |
| File Upload | A file picker accepting common document and image formats | Headshot upload, portfolio PDF, certification document | Files are stored in Salesforce against the Attendee record; size limits apply per org |
Salesforce Field Mapping
Every data-capture element can optionally map its answer to a field on the Attendee, Contact, or Lead record in Salesforce. Mapping is configured in the element's settings panel under the 'Salesforce Mapping' section.
| Setting | What it does |
|---|---|
| Maps to Object | Selects the Salesforce object to write the answer to (Attendee, Contact, or Lead) |
| Maps to Field | The specific API field on that object that will receive the answer |
| Required | When checked, the form cannot be submitted without an answer to this question |
| Hidden | The element is included in the form submission but not displayed to the registrant — useful for pre-populating known field values |
| Read-Only | Displays the current SF field value but does not allow the registrant to edit it |
:::(Note) (Form Element Salesforce Mapping)
Form elements and their Salesforce mappings are stored as conference360__Form_Element__c records. The Maps_To_Object__c and Maps_To_Field__c fields store the target object API name and field API name. Forge writes answers to both the Attendee record and the mapped Contact/Lead field on submission.
:::
Answers to questions that capture personal data (name, email, address) are stored only in Salesforce — never in Forge's Postgres database. Do not use Hidden or Static Text elements to echo back PII in confirmation messages.
Visibility Rules on Elements
Any form element can be shown or hidden based on answers to earlier questions in the same form. Rules are built in the element's Visibility tab and are evaluated in real time as the registrant fills out the form. This is the same rule engine used for ticket visibility, powered by bt_base__Rule__c and bt_base__Rule_Condition__c records.