Choose Read only, Execute JS, Go to Page or Start a tour and understand checklist task completion.
Each checklist task has an action and a completion setting. Choose the action that matches what the user needs to do.
| Action | What it does |
|---|---|
| Read only | Displays task content without starting a tour, navigating or running a script. |
| Execute JS | Runs the configured JavaScript. |
| Go to Page | Opens the configured page. |
| Start a tour | Starts the selected product tour. |
Set up a task
- Open the checklist and add or select a task.
- Enter a short title that describes the user's task.
- Choose an action and configure its destination, script or tour.
- Review Mark as complete. The default completion option depends on the selected task action. For Execute JS, it is labeled Script Executed Successfully. Choose Match Actions to use event conditions.
- Test the task in the demo application.
Match Actions uses configured event conditions. Your application must send the matching events.
Check completion behavior
Do not assume that a completed task proves a separate business outcome occurred. A page action can be marked complete before navigation finishes. Running a script is not proof that a downstream request succeeded. A tour action's completion depends on its completion configuration.
Skipping a task also marks it complete in the checklist. Check this behavior before using checklist completion as a measure of product adoption.
There is no separate Manual checkbox task type. Use the separate Allow mark as completed manually setting when appropriate.