Appearance
Text and contact inputs
Use text and contact fields to collect a typed answer. The original reference is being replaced with task guides that show the configuration process for each field.
All of these fields share the editor’s basic label, internal-name, appearance, required, uniqueness, range, and custom-error controls where they are supported. Configure the field by selecting it and opening Edit.
Short Text
Use Short Text for a concise answer, such as a reference number, job title, city, or short description.
Settings
| Setting | What it does | Guidance |
|---|---|---|
| Label | Names the answer you need. | Use a specific question: What is your employee ID? |
| Placeholder | Shows example or hint text inside an empty input. | Use a format hint, not the entire question: For example, EMP-1042. |
| Accepted data type | Limits the answer to a supported format when configured. | Use only when a free-text answer would create a real processing problem. |
| Minimum / maximum length | Limits the number of characters. | Use for known identifiers; do not impose arbitrary limits on names or descriptions. |
| Minimum / maximum value | Limits a numeric answer when that validation is appropriate. | Prefer a number-oriented field strategy when users are entering quantities. |
| Required Field | Requires an answer before submission. | Turn on only when the answer is essential. |
| Unique Value | Requires an unused value. | Use for a registration code or reference that must not be repeated. Test it against real submission behavior first. |
| Custom error text | Replaces the standard validation message. | Say what is expected and how to fix it. |
Long Text
Use Long Text when a respondent needs space to explain, describe, or provide several sentences.
Settings
Long Text uses the same core settings as Short Text, but its placeholder should set the expected level of detail. For example: Please describe the issue, including when it started and what you expected to happen.
Use a maximum length only when a downstream system, review process, or policy requires one. If brevity matters, tell respondents the target length in the label or help text rather than surprising them with an unexplained limit.
Email
Use Email when the answer must be an email address. It provides email-oriented validation, so it is safer than asking for an email address in a generic text field.
Settings
| Setting | What to do |
|---|---|
| Label | Make the purpose clear: Email address for confirmation. |
| Placeholder | Use an obviously fictional example, such as name@example.com. |
| Accepted data type | Keep the email format validation when collecting an email address. |
| Required Field | Use when you cannot complete the task without a reply address. |
| Unique Value | Use only when one email address must correspond to one submission, and explain this to respondents. |
| Custom error text | Example: Enter an email address in the format name@example.com. |
Do not assume a syntactically valid email address proves that the respondent owns it. If ownership matters, use an appropriate confirmation or authentication process.
Phone Number
Use Phone Number for telephone details. It can show a country-appropriate sample when a manual placeholder has not been provided.
Settings
| Setting | What to do |
|---|---|
| Label | State why you need it and, if useful, when you may call. |
| Placeholder | Provide a local-format example only when it helps. A manually entered placeholder takes precedence over an automatic sample. |
| Required Field | Make it required only when telephone contact is necessary. |
| Custom error text | Explain the required format or ask for the country code when that is required. |
Avoid using a placeholder as the only explanation of an international format. Put the real instruction in the label or nearby explanatory text, because placeholder text disappears as the respondent types.
Website
Use Website when you need a web address. The field can be configured with URL-oriented validation.
Settings
| Setting | What to do |
|---|---|
| Label | Say what page you need: Company website or Portfolio URL. |
| Placeholder | Show a complete example such as https://www.example.com/. |
| Accepted data type | Use URL validation when the answer must be a web address. |
| Required Field | Leave optional unless the form cannot be processed without it. |
| Custom error text | Example: Enter a full website address, beginning with https://. |
Test checklist for every text/contact field
- [ ] The label makes sense without relying on placeholder text.
- [ ] The internal name is stable and meaningful.
- [ ] A valid answer is accepted.
- [ ] An invalid answer is rejected only when validation is intentional.
- [ ] The error message tells the respondent how to recover.
- [ ] A phone or email requirement has a clear business reason.
- [ ] No actual personal data was used while testing.