Control Types
Controls are the building blocks of a task. Every task in a template is made up of one or more controls, added from the controls toolbar in the template editor.
There are two types of control in CheckFlow. Content Controls display information to the user, and Input Controls capture information from them.
Content Controls
Content Controls are read-only in the checklist. You set them up once in the template and they are displayed, unchanged, in every checklist created from it. The user cannot alter them, they capture no answer, and they never prevent a task from being completed.
| Control | Purpose |
|---|---|
| Text | Formatted text, lists, tables, links and images — usually instructions |
| Image | A picture with an optional caption |
| Video | A playable video, uploaded or embedded from YouTube, Vimeo and others |
| File | A file for the user to download |
| Mail-To | A pre-written email that can be sent from the checklist |
| Embed | An external web page or application shown inside the task |
| Separator | A horizontal line to divide a long task into sections |
Input Controls
Input Controls capture input from the user while they run the checklist.
| Control | Captures |
|---|---|
| Short Text | A single line of text |
| Long Text | Multiple lines of text |
| An email address | |
| Website | A web address |
| File Upload | One or more uploaded files |
| Date & Time | A date, a time, or both |
| Drop-Down | One option from a list |
| Multi-Choice | One or more options from a list |
| Sub-Tasks | A checklist of items within the task |
| Members | Users and groups from your team |
| Table | A grid of values |
| Linked Checklist | Creates a child checklist (captures no answer of its own) |
Making a Control Required
Most input controls have a Required checkbox. When a control is marked as required, the parent task cannot be completed until a value has been entered.
Two controls express the same idea differently, and two do not support it at all:
| Control | How "required" works |
|---|---|
| Short Text, Long Text, E-Mail, Website, Date & Time, Drop-Down, Multi-Choice, Members | A Required checkbox on the control |
| Sub-Tasks | A Required checkbox — when set, every item in the list must be ticked |
| File Upload | A Minimum Files count rather than a checkbox. Set it to 1 or more to make an upload mandatory |
| Table | Set per cell, via Is Required? in the cell's dropdown, rather than for the whole control |
| Linked Checklist | Not supported. A task can be completed whether or not the child checklist has been created |
| Mail-To | No checkbox, but the Required – Manual Send send mode blocks completion until the email has been sent |
Validation runs when the user completes the task, and failing controls display an error message beneath them. If you complete a task from outside the checklist — from the Dashboard, for example — any validation failure is reported in a pop-up message instead.
What Else Controls Can Do
Beyond capturing an answer, controls take part in several template features. Which ones apply depends on the control:
- Conditional Logic — the answer given in one control can show or hide other controls and tasks. Short Text, Long Text, E-Mail, Website, Date & Time, Drop-Down, Multi-Choice and Members can drive a condition. Every control, content controls included, can be shown or hidden by one.
- Dynamic Values — an answer captured in one control can be reused elsewhere in the checklist. Short Text, Long Text, E-Mail, Website, Date & Time, Drop-Down, Multi-Choice, Sub-Tasks, Members and Table are the sources. There are two separate ways a control can receive one, and the DV target column marks which applies:
- Placeholders —
{{tokens}}typed into the content of a Text or Mail-To control, replaced with the live value. The Linked Checklist control's Default Checklist Name field takes them too. - Bindings — set from a control's own settings, pre-filling it from a global value or another control. Short Text, Long Text, E-Mail, Website, Date & Time and Drop-Down accept these, as do Video and Embed for their source URL.
- Placeholders —
- Template Parameters — a control can be pre-filled when the checklist is created, rather than by the user. Supported by Short Text, Long Text, E-Mail, Website, Date & Time, Drop-Down, Multi-Choice, Sub-Tasks and Members, and also by Video and Embed so their source URL can be set per checklist.
- Data Sets — Drop-Down, Multi-Choice, Sub-Tasks and Table can be populated from a Data Set, so their options or rows come from your own managed data rather than being typed into the template.
- Linked Checklists — values can be carried from a control in a parent checklist into a control in the child checklist it creates.
- Reports — answers from input controls can be added as report columns. Table and Linked Checklist are the exceptions.
- Tooltips — every control can be given a tooltip offering extra guidance on hover.
Each control's own page sets out exactly which of these it supports. The matrix below gives the whole picture in one place.
Capability Matrix
| Control | Required | Drives logic | Can be hidden | DV source | DV target | Parameter | Data Set | Reports | Linked ⇄ | API |
|---|---|---|---|---|---|---|---|---|---|---|
| Text | — | — | ✓ | — | ✓ 1 | — | — | — | Child | Read/Write |
| Image | — | — | ✓ | — | — | — | — | — | — | Read/Write |
| Video | — | — | ✓ | — | ✓ 2 | ✓ | — | — | Child | Read/Write |
| File | — | — | ✓ | — | — | — | — |