You can design workflows to ask users to input text, select from list boxes, or click checkboxes or radio buttons. This data is collected as a part of the session and is easily imported into other applications.
Here's how to add a Data Entry field to a node:
- In the editor, open the content node where you would like to place form fields.
- Go to the Data Collection Form Fields section, then Add Data Form Field.
- A new Data Entry field dialog appears. Select the type of data you want to collect, and enter a variable name and a label that the end-user will see.
- Optionally, you can also enter Help Text. The Help text is descriptive text that will be displayed directly below the input Label, like this:
For radio buttons and list boxes, enter the option choices one per line. If you are using scoring variables, you can enter a score variable, and a score value to assign to each choice. In the example below, the residence variable will be assigned a residence_score of 2 if Own is selected, or 1 if Rent is selected.
List Box Filtering: We recommend leaving this option turned on. Users will be able to type to quickly filter a long list box of items. Like this: - Select Required Field to make this field require an entry before proceeding.
- Click the Add button when finished.
Labels vs. Placeholders
You can choose how the hints for the data entry fields display, as either Labels or Placeholders.
Here's how labels appear:
Here's how placeholders look:
Repeating Data Entry Forms
Repeating Data Entry Forms allow you to collect information on an indeterminate number of items. For example, an insurance application may need to collect the names and ages of each family member – be it one or ten. Zingtree’s Repeating Forms capability fulfills this need.
How Repeating Forms Work
A node can collect multiple forms, one at a time. First, the agent starts with one form:
The agent can click the + button to enter a second family member:
This can continue for multiple family members. Here is a representation of the data collected.
Configuring Forms for Repeat Entries
When editing a node, there’s an option in the Data Collection Form Fields section to configure repeating items. Here are the details:
- Edit the node with the form you want to make repeating.
-
In the Data Collection Form Fields tab enter the maximum number of items to repeat (up to 50):
That’s all you need to do! The data variable names for your repeating forms will have an underscore and an item number at the end. So, in the example above, the variables for driver will be driver_1 and driver_2, driver_3, etc.
Please note: File Uploads are not available in repeating forms.
Conditional Form Fields
You can easily create data entry form fields that only display when certain conditions are met. You decide when they appear based on simple logic rules. This can help streamline your workflow by reducing unnecessary clicks and shortening session durations — only showing fields when they’re needed.
For example, here’s a standard field asking if you own or rent your residence:
- If you select Own, a field asking for the monthly mortgage amount will appear.
- If you select Rent, a field asking for the monthly rent amount will appear.
- If you select Neither, no conditional field will be presented.
Adding Conditional Fields
You can add conditional fields in the same way you add any other standard data entry field.
In this example, we’ll create three form fields — two of which are conditional upon the first. Conditional fields do not need to be on the same node as the variable they depend on. They can be placed on the same node, or any subsequent node that follows the dependent variable.
To make a field conditional upon the value of another variable:
- Add your field as you normally would.
- Switch the Conditional option to the ON position.
Once enabled, set the conditions. The Display When condition is based on the variable of a previous field (or any other variable available in your workflow). Clicking into the field will show you all of the variables that are currently available in your workflow.
In this example, we’re setting the mortgage_amount field to display only if the variable residence is equal to Own.
Note: Values are case-sensitive and must exactly match the value of your previously configured options.
More Examples of Conditional Fields
Here’s another example:
You might collect an age variable and set a conditional field called baby_gifts to display only if age < 1 (less than 1).
You could then set up other list box options to display different fields based on other ages.
Operators for Conditional Fields
These are the simple logic operators that can be used for your Conditional Fields:
| Operator | Meaning |
|---|---|
| = | is equal to |
| ≠ | is not equal to |
| < | is less than |
| > | is greater than |
| ≤ | is less than or equal to |
| ≥ | is greater than or equal to |
Advanced logic operators are coming soon for Conditional Fields.
Using Required Conditional Fields
Conditional fields can be set to required. They will only be required if the field is displayed (i.e., when the condition you’ve specified is met).
Limitation: Repeating Forms
Note that Conditional fields are not available for use on forms that are set to allow more than 1 submission.
Displaying collected values of variables in your content
-
When an end-user enters something into a data collection form field, you can display it in subsequent nodes. Just include the variable name surrounded by #characters. In the example below, you would insert #first_name# to show the entered first name, and #last_name# to insert the entered last name.
You can also insert variables from the content editor when editing a node, like this:
Data Entry Placement
- Data Entry fields are displayed at the end of the content area by default. If you want your Data Entry fields to be inserted in a different place in your content area, use the Put the Data Entry Area at the Cursor template in the content editor instead:
This will insert the text ##data-collection-entry-fields## into the content area, which will be replaced by your data collection form fields.