Article Content
| Overview |
| Validation Rules |
| Length Constraints |
| User Account Requirements |
| Navigation |
| Creating an Email Address Field |
Overview
An Email Address field type allows users to store validated email addresses.
The Email Address field type can be used in the following features and functionalities:
- App export and import
- App tagging
- Bulk assessment launch
- Configurable forms
- Data Audit Trail
- Data grid
- Data import
- Data Warehouse
- Merge duplicate objects
- Messaging workflow action
- Object creation
- Org copies
- Org export and import
- Relationship tables
- Report exports
- Report tables
- Translations
Single Line and Multi Line Text fields storing email addresses can be converted to Email Address fields, as long as the existing field is not being used in an unsupported location. The email address validation will be triggered the first time the field is edited by a user, post conversion. If the email address is in an invalid format, users will no longer be able to save the value. Please refer to the Editing a Plain Text Field article for further information.
|
Warning: Converting a Single Line and Multi Line Text field to an Email Address field cannot be reversed. |
Validation Rules
The following format validation rules will be enforced for Email Address fields:
-
Local Part Syntax: The local part is the text before the @ symbol. It can be formatted in two ways:
-
Standard/Unquoted (the local part isn’t in quotation marks): Uses letters, numbers, and common symbols (!#$%&'*+/=?^_{|}~-).
- Dots/periods (.) can’t be at the start or end of the local part
- You can’t have two dots/periods (.) in a row in the local part
Extended/Quoted (the local part is in quotation marks): Uses letters, numbers, spaces, and special characters (including common symbols).
-
Standard/Unquoted (the local part isn’t in quotation marks): Uses letters, numbers, and common symbols (!#$%&'*+/=?^_{|}~-).
-
Local/Domain Split: The domain is the text after the @ symbol. It must be a valid Fully Qualified Domain Name (FQDN) which is made up of labels for the hostname (e.g. mail), domain name (e.g. resolver) , and top-level domain (e.g. com). This also includes alternative/root domains (e.g. resolver.com). Its format is:
Each label must be separated by a dot/period (.) (e.g. resolver.com)
Labels can only contain letters, numbers, and hyphens
Labels can’t start of end with a hyphen
The last label (top-level domain) must be at least 2 characters long.
Length Constraints
The email address must follow these length constraints:
The total email address cannot be more than 254 characters
The local part (before the @) cannot be more than 64 characters
Each domain (after the @) label (between each dot/period) cannot be more than 63 characters
User Account Requirements
The user account you use to log into Resolver must have Administrator permission to use the create an email address field.
Navigation
- From the Home screen, click the Administration icon.
Administration Icon
- From the Administrator Settings menu, click the Admin Overview link.
Admin Overview Link
- From the Admin Overview screen, click the Fields tile in the Data Model section.
Fields Tile
- From the Admin: Fields screen, click the Create Field button.
Create Field Button
Creating an Email Address Field
- From the Which type of Field would you like to create? pop-up, hover your cursor over the Email Address field.
Email Address Field
- Click the Create Field button.
Create Field Button
- From the Admin: Create a Field screen, enter the field name in the Field Name field. The field name can be used on object types throughout the system.
Field Name Field
- (Optional): Enter additional information or alternate phrasing in the Long Name field. Information entered in the Long Name field will appear on forms.
Long Name Field
- (Optional): Enter a field description explaining the function of the field in the Description field. The Description field gives users more information about a field.
Description Field
- Click the Create button.
Create Button