Dataflow and form logic let you build smarter forms — ones that pull data from previous forms and change their behavior based on how they're filled out.

Dataflow

Dataflow copies data entered in one form into a matching node on a different form. It's most useful for progressive evaluations: data from a fall evaluation can flow into the spring evaluation, so the evaluator sees previous ratings while scoring current performance.

Set up dataflow

1. Create the source form — the one data flows from. See Building Your First Form.
2. Create the destination form — the one data flows into. If it shares many fields with the source, use Clone form instead of building from scratch.

3. Open the destination form and select the node you want data copied into.
4. In Data Properties, select Read only.
5. Still in Data Properties, go to the Dataflow section and click (+) Add new source to choose the source form.

6. Click Available Nodes and select the node to pull data from.
7. Repeat steps 3 through 6 for every node that should receive dataflow.
8. Click Publish changes.

Note: Both nodes must be the same type. You can't flow a checkbox into a text box. Dataflow also can't go to and from the same form — it only works between two different forms.

Why read only? Setting receiving fields to read only keeps data from other forms uneditable, so it stays a snapshot of what was entered on the source form. It's recommended but not required.

Best practice: Data is pushed only once — at the moment the destination form is started by its author. To make sure the source form is finished first, set it as a prerequisite to the destination form in your assignment setup.

Form logic

Logic rules make a form behave differently depending on who is completing it and how certain fields are answered.

Adding a logic rule

Every logic type follows the same path.

1. Build the fields the rule will use.
2. Click the Logic button in the top right.
3. Click the + icon to create a new rule.
4. Name the rule after the field it controls — for a Yes/No question like "Do you have a car?", name it CarShowHide.
5. Choose the rule type and configure it.
6. Click Preview on desktop and test the rule.
7. Click Publish changes.

Note: Logic rule names cannot contain spaces. Only checkboxes, radio buttons, and dropdown lists can control logic.

Show, hide, or require fields

Shows or requires content based on what a user selects in another field.

Set up your controlling field first — a checkbox, radio button, or dropdown list — and give each option both text and a value. Then create the controlled field, leaving it not required.

In the rule, configure:

• Show these items — makes the controlled field appear.
• Require these items — makes the controlled field required.
• Items — the controlled field.
• Data Elements — the controlling field.
• Expression — the condition that has to be true.

Caution: Never mark a logic-controlled field as required in Data Properties. It would stay required while hidden, and your users would get an error about a field they can't see.

Note: Options must have values for logic to work, and each value must be different — 1 for Yes, 2 for No. For this rule type the specific numbers don't matter.

Show or enable based on signer tag

Controls fields based on a user's signer tags. Useful when you want to hide certain fields from students or site supervisors while still collecting everything on one form.

In the rule, configure:

• Show — the fields are only visible to the signer tags you define.
• Enable — the fields are visible to everyone, but only the signer tags you define can fill them in.
• Fields — what the rule controls.
• Qualifier — use IS.
• Signer tag — who the rule applies to.

Note: This rule reads a user's signer tags, not their role. If it isn't working for someone, check their signer tags against the ones in the rule. See Signature Lines and Signer Tags.

Basic arithmetic

Adds, subtracts, multiplies, or divides values collected on the form. An AVG function is also available for averaging across selected nodes.

Create the fields to be calculated, giving each option text and a matching value. Then create a results field.

In the rule, configure:

• Perform the following arithmetic — the fields to calculate with. Text boxes, checkboxes, radio buttons, or dropdown lists.
• Add — adds another field to the calculation.
• Add group — wraps fields in parentheses for order of operations. To average three fields: (A + B + C)/3.
• And put the result here — the results field.
• Resulting equation — shows the equation you've built.

Note: The results field must be a text box, and it must be marked Read only so users can't change the score while it calculates. For arithmetic, each option's value should match its text — the calculation uses the value, not the text.

Copy to fields

Copies a value from one field into other fields on the same form. Useful when the same answer is needed in several places, such as an author's name repeated throughout a form.

Create the source field and the destination fields, then configure:

• Copy value of field — the source field.
• To — the destination fields.

Related articles

• Building Your First Form
• Form Builder: Node Types
• Form Builder: Menus & Options
• How to Autofill a Form Using the Correct Dataflow Source
• Signature Lines and Signer Tags
• Form Builder: Editing Published Forms