With a form created and fields in place, you can customize each field to make them more customized and tailored to your needs including:
- Mapping to system fields
- Defaulting a values
- Conditionally displaying fields
Settings & Descriptions
|Active/Inactive: Active fields display as expected. Inactive fields are grayed out in the Form Builder and are not available when the form is filled out, both externally and administratively.
|Allows for selection of different field display options (depending on current selection).
|Displays the title of the field and can be edited using HTML.
|When checked, the title of the field will not display.
|Only available for free-text fields. Displays inside of text fields until registrants begin to enter information/text.
|Maps to a system field in Slate. Custom fields can be accessed by selecting Fields from the first dropdown.
The Safe / Unsafe setting for a person-scoped field determines how the field can be updated if an application in an active period exists for a record.
Suppose a person-scoped field is configured as Safe. In that case, the field value is not updated by a safe source import or a safe form submission if the record has an application in an active period.
Learn more about how safe and unsafe behavior can affect your records here.
|This setting allows incoming NULL values, the form field being empty, to clear out any value already stored in this field for the corresponding registrant/record.
|Will be pre-populated when a system field is selected above. If this isn't a field that requires mapping to the Person Record, an export key can be entered to enable querying on this field data.
|Specifies the kind of data expected to be entered into the field. Will affect how the data can be used in calculations.
|Adjusts the width of the form field presentation.
|Ensures that data is entered and formatted consistently (e.g., restrict a GPA form field to only numeric data with two digits following the decimal point, currency with a thousand separator, or email address format).
|Sets field character limit.
|Sets field word limit.
|Max Length Countdown
|When a character or word limit is set, it can display the remaining characters or words that a registrant has before reaching the maximum.
Allows entry of prompts for non-mapped fields and displays system prompts for mapped fields.
|Autosuggest can be used to data points such as school information so that a form is easier to complete and errors in data entry may be avoided. Since a dataset stores school information, this data can facilitate form completion by prospective students by enabling the Autosuggest feature.
|Default Value Formula
Auto-populates the form value from a previously selected export set in the form.
|Presets the form field's value to a specific prompt from the prompt list associated with the form field.
|Sets a column width on a form field.
|Defines the layout of the form field on the form.
Here is a truth table for the different option combinations:
|The field will not display publicly to form registrants. When submitted administratively by a user, there will be a warning but the user can still submit the form.
|Form can only be submitted if a value is set through script, autosuggest, or a default value.
|Hidden will be given precedent over Required
|Disabled will be given precedent over Required
|Displays value internally but does not allow editing
|The value of the Hidden field will only populate if the form is submitted administratively
|Displays value internally but does not allow editing or store value
|Hidden already cannot be edited and also are not displayed internally or externally
|Disabled already cannot be edited and also does not store value
|Do Not Use - field cannot be seen, be edited, or store a value
Here are a few use cases for some of the combinations:
- Required + Internal: any high priority internal field
- Required + Read Only: visible calculation field if not all calculation inputs are required
- Internal + Read Only: information needed to submit the form administratively