Interactive tasks require user input and manual completion. These tasks must be assigned to one or more contributors who are responsible for completing the task.
An interactive task must also have a supervisor who's responsible for approving that the task has been completed. Optionally, an interactive task may have an owner assigned who can verify if a task is complete.
Interactive tasks include:
| Task | Description | Task Type |
| File Import | These tasks are used to manually import data from an Excel or CSV file. | Application |
| Data Input | These tasks require user input in Anaplan XL Reporting writeback reports or Anaplan XML Forms. | Action |
| Reporting | This task allows you to view data in a report. | Reporting |
| Review | This task allows you to decide whether to approve or reject the previous step in the workflow. | Action |
| To Do | These tasks are used to inform a user that there's an offline manual task to be performed. The task has instructions and is completed like any other task. | Action |
Common Workflow Task Fields
Use different tasks to complete the process. Each task type has a different required fields. Interactive tasks require user input and manual completion. Non-Interactive tasks automatically start and complete without user intervention once they have been started.
For interactive task types, there are common fields that may apply.
Workflow Roles
The workflow roles include:
| Role | Description |
| Owner | The Owner can approve, reject, or complete a task. This user role can set a percent completion rate and is responsible for the task. This field is optional. If no owner is set, the contributor is the owner. |
| Supervisor | The Supervisor can approve, reject, or complete a task. They can verify task completion in place of the owner, such as when the owner is out of the office. |
| Contributor | The Contributor performs the task. If no owner is set, the contributor is the owner and can approve, reject, set a percent complete, and complete the task. |
Due Dates
It's the date the task needs to be completed by. This is an optional field. Select from these options:
| Due Date | Description |
| No Due Date | The task will never be overdue. |
| From activity start time | Set the due date from when this task starts plus the days, hours, and minutes selected. |
| From activity start time, business days only | Set the due date from when this task starts plus the days, hours, and minutes selected, excluding weekends. |
| From process start time | Set the due date from the start of the workflow process plus the days, hours, and minutes selected. |
| From process start time, business days only | Set the due date from the start of the workflow process plus the days, hours, and minutes selected, excluding weekends. |
| Before process end time | Set the due date from the due date of the workflow process less the days, hours, and minutes selected |
| Before process end time, business days only | Set the due date from the due date of the workflow less the days, hours, and minutes selected, excluding weekends. |
| Absolute Date | Set the exact date specified. |
Advance Rule
This field specifies how to advance to the task. The default is All predecessors have completed. Select from these options:
| Advance Rule | Description |
| Every time a predecessor completes | Whenever any of the previous tasks have been completed, the current task is started. In this case, if there are three previous tasks, the current task will be run three times. |
| All predecessors have completed | When all tasks before the current task have been completed, then the current task is started. |
| First time a predecessor completes | When any of the previous tasks have been completed, then the current task is started and will be started only once. |
