E-Mail Control
The E-Mail control captures an email address from the user.
It consists of a single-line text box and a label, with email format validation built in. Use it wherever you need a usable address rather than just text — a customer contact, an approver, a supplier.
Add to the Template
The E-Mail control can be added from the controls toolbar in the Template.
Once you have added the control you must set the label text that will be displayed above the text box. The label is required — it is also the name used to identify the control elsewhere in CheckFlow, such as in reports and dynamic values.
Required
Tick the Required checkbox if the user must enter an address before the parent task can be completed.
Populating from a Data Set
The E-Mail control cannot be linked to a Data Set. Only the Dropdown, Multi-Choice, Sub-Tasks and Table controls can be.
Use in the Checklist
The user sees the label with a single-line text box beneath it. Their entry is saved automatically as they type, and the control records who last changed it and when.
Validation
The E-Mail control performs pattern matching to ensure the value entered is a valid email address. If it is not, an error is displayed below the text box and the task cannot be completed.
When the control is marked as required, validation is also performed when the user completes the task. The task cannot be completed until a value has been entered.
If you try to complete a task outside of the checklist (e.g. from the Dashboard) and it fails validation we will notify you of the validation failure via a pop-up message.
Format validation confirms the address is well formed — it does not confirm the mailbox exists or can receive mail.
Conditional Logic
An E-Mail control can be used to drive Conditional Logic. The available conditions are is, is not, has no value and has any value.
An E-Mail control can also be the target of a rule, so it can be shown or hidden by a condition driven by another control.
Dynamic Values and Parameters
The address captured in an E-Mail control can be reused elsewhere in the checklist as a Dynamic Value. This is particularly useful in the To, Cc or Reply-To fields of a Mail-To control, letting you email an address the user supplied earlier in the checklist.
The control can also receive a dynamic value, through a Dynamic Value Binding set from the control's Content Settings cog. The only global dynamic value it accepts is the Current User's Email — the other global values are not email addresses. It can also be bound to the value of another control in the same checklist. See Dynamic Values.
The control can also be bound to a Template Parameter of type String, so it is pre-filled when the checklist is created.
Linked Checklists
An E-Mail control can be either side of a Linked Checklist control mapping, so an address captured in a parent checklist can be carried into the child checklist it creates.
Reporting
E-Mail answers are available in Reports and can be added as a column, displayed as a clickable email address.
Control columns are only available in a report when a single template is selected. Add the column from the Columns dropdown, under Tasks & Fields. See Report Columns.
Limits
| Limit | Value |
|---|---|
| Format | Must be a well-formed email address. One address per control. |
| Maximum length | 500 characters |
This is a storage limit rather than a validation rule. Nothing in the interface stops you entering more, and no warning is shown as you type — a longer value fails when it is saved.
Related Pages
- Mail-To — to send an email to the address captured here.
- Members — to pick someone from your team rather than type an address.
- Dynamic Values — how to push the captured address into an email elsewhere in the checklist.
- Control Types — the capability matrix for every control.