Subtask types

Updated

A subtask is a question, form field or action inside a task. In the task builder, you build each subtask from a step type. Most step types make a standalone subtask: one step that asks a single question, shows content or runs an action. Form step types make a form subtask: a container that holds several fields in one subtask.

This video walks through both kinds, their step options, and how conditional logic differs between them.

When to use it

  • Use a standalone subtask when each step is a separate action, or when an answer should send the customer down a different branch of subtasks.

  • Use a form subtask when you want several related inputs at once, such as a name, a department and a file, without making the customer move through separate subtasks.

How it works

The step-type palette

The task builder lists step types in collapsible categories, with a Search step types... box at the top. The form categories hold the step types that can go inside a form. The other categories hold step types that work only as standalone subtasks.

While a form is selected, step types outside the form categories are disabled. Hovering over them shows "These step types cannot be added to a form."

Standalone subtasks

Each standalone subtask is one step: a single question, a piece of content or an action. For example, Text Instructions, File Download and Presentation show content, and Create Slack channel is an action. The step types include:

  • Text Instructions

  • Short Answer and Long Answer

  • Yes / No

  • Single Selection and Multiple Selection

  • Dropdown

  • File Upload and File Download

  • Presentation

  • Embeddable

  • Echo Sign (Adobe Sign), when Adobe Acrobat Sign is turned on for your organization

  • DocuSign, when DocuSign is turned on for your organization

  • Create Slack channel, when Slack is turned on for your organization and connected

In the customer portal, the customer finishes a subtask and selects Save & Continue to move on. On the last subtask still to be completed, the button reads Complete Task.

Branching between subtasks

Branching for standalone subtasks happens between subtasks in the tree view. It works from Yes / No, Single Selection and Dropdown subtasks. Each option can lead to its own branch of further subtasks, so customers who answer differently see different subtasks next. Multiple Selection subtasks can't branch.

E-sign steps also have Signature steps nested under them for the signers.

Form subtasks

A form subtask holds several fields inside a single subtask. To make one, drag a form step type, such as Text Input or Group, onto the flow chart. On an empty task, you can also select Start from a template, Start with a group or Start with columns.

Only form step types can be added to a form subtask:

  • Inputs: Text Input, Number Input, Text Area, Rich Text, Date, Date Time, Phone and Rating

  • Choices: Dropdown, Single Choice and Multiple Choice

  • Files and signing: Request Files, Share Files and Signature

  • Content: Heading, Label, Paragraph, Link, Image and Divider

  • Layout: Columns, Group and Table

The customer fills in every field in the form, then selects Save & Continue once. If it's the last subtask still to be completed, they select Complete Task.

To start a new form from a ready-made layout on an empty task, select Start from a template. To add a template's fields to a form you already have, select the form, then select Templates in the task builder. See Best-practice form templates.

Conditional logic inside a form

Conditional logic for a form works inside the subtask, not between subtasks in the tree view. Using a field's Conditional Display setting, an answer can show or hide other fields in the same form. This keeps the form relevant without adding subtasks to the tree.

Quick comparison

Standalone subtasks

Form subtasks

Structure

One step per subtask

Several fields in one subtask

Save point

After each subtask

Once, after all the form's fields

Logic

Branches between subtasks, from Yes / No, Single Selection and Dropdown

Shows or hides fields inside the form

Best for

Separate actions and branching

Collecting several inputs at once

Limits

  • You can't add standalone step types, such as Embeddable or DocuSign, inside a form.

  • Multiple Selection subtasks can't create branches.

  • Conditional logic inside a form only affects fields in that same form.

For more walkthroughs, see the OnRamp tutorials video library.

More in Tasks & Activities