Tasks

A journey consists of one or more tasks, which can optionally split a task into subtasks. Completing every subtask completes the task. Tasks and subtasks are Serval tickets under the hood. You can leverage all the properties of Serval tickets such as due dates, SLAs, assignment groups, visibility groups and custom fields. Each task/subtask can have an attached workflow that runs automatically or upon form submission.

​

Manual tasks

Manual tasks have no attached workflow. The assignee completes the task with Mark complete and can Reopen it if needed. An example of a manual task is I-9 document verification for a new employee.

​

Form tasks

Form tasks render a form for the assignee to fill in. Submitting the form runs the attached workflow with those inputs. For example, you can have a task that collects emergency contact info and runs an attached workflow to populate the info in Workday.

​

Automated tasks

Automated tasks run on their own with no humans involved. Some run a workflow as soon as they’re ungated (e.g. Okta account creation on start date, Google account creation post Okta account creation), while others are status checks that periodically poll an external system and complete once it reports back (e.g. a background check task that polls Checkr). Automated tasks display a Serval icon.

Only admins can mark a workflow-driven task done by hand: its status normally follows the workflow. The Building journeys guide covers how tasks get their workflows and inputs (see Creating a journey).

​

Task dependencies

Tasks can be gated by dependent tasks or time-based conditions. A locked task will indicate the condition it’s waiting on, and will unlock automatically when those conditions are satisfied.

​

Task states

Each task shows its current state: A task can also surface an Error or Warning when a run needs attention. These roll up into the journey’s Health Checks.

​

Related