Configure task types and automatic task templates
Manage the task catalog, form availability, automatic assignments, deadlines, and task permissions.
Table of Contents
Administrators configure Tasks at two levels: the organization’s Task types catalog and the Tasks tab on each form. The catalog groups types into categories. Each form chooses which types employees can use and can define templates that create tasks automatically.
Live settings: changes on a form’s Tasks tab apply immediately, are not part of publishing the form, and are recorded in the audit log. Saving a template with Save and make live activates it for subsequent matching events.
Plan your task setup
- Identify the follow-up actions you need, such as a document request, a management-plan acknowledgment, or a post-approval check.
- Group related actions into clear categories and types.
- Decide which forms should offer each type for manual tasks.
- For automatic tasks, define the triggering event, assignee, instructions, due-date rule, related parties, and visibility.
- Validate the setup with representative test records and users before introducing it into your working process.
For everyday task creation, collaboration, and completion, see Create, manage, and complete tasks.
Manage the organization’s task catalog
Add a category
- Select Switch to admin view.
- Under Content, open Task types.
- Select Add category.
- Enter a Category name and select Add category.
A category groups related task types. For example, a category named “Follow up” might contain a type named “Document request.” Use names that employees will recognize when creating tasks.
Add a type
- On Task types, locate the appropriate category.
- Select Add type for that category.
- Enter the Type name and select Add type.
- Open the relevant form’s Tasks tab and offer the type there.
The type is available for forms to offer immediately, without a publish step. The catalog shows which forms currently offer a type, helping you understand the impact of changes.
Rename or retire a type
Open the type’s More actions menu to find Rename and Retire type. Before retiring a type, read the confirmation: it identifies affected forms, which will stop offering the type for new tasks. Choose Keep type to cancel or Retire type to proceed. The catalog’s Retired view provides a route to restore retired types.
Use retirement to stop offering an obsolete type. Do not treat retiring a catalog entry as a way to complete existing follow-up work; manage those tasks through their own lifecycle.
Understand names on existing tasks
Renaming a category or type updates forms, the task picker and tasks created afterward. Existing tasks keep the category and type names captured when they were created, including in supported exports. An older label does not mean the rename failed. Retiring a type does not complete existing tasks.
Choose which task types a form offers
- Open Content → Form builder.
- Select the form.
- Open Tasks, marked Live.
- Under Task types offered, select the types employees should be able to choose when creating a task on this form’s records.
- Use New type if you need a new catalog entry, or Manage task types to open the organization catalog.
- Check the resulting selection before leaving the page.
These choices take effect immediately. You do not need to publish a new form version. A type being present in the organization catalog does not mean it is offered on every form.

Create an automatic task template
- Open the form’s Tasks tab.
- Under Templates, select Add template.
- Enter a Task title that describes the required action.
- Select a Task type. The list comes from the types this form offers.
- Enter Instructions describing the work and expected completion evidence.
- Choose the When event.
- Configure Assign to, Due, Related parties, and the available options.
- Read the activation message at the top of the dialog.
- Select Save and make live when the template is ready.
If you are only inspecting the options, select Cancel. Saving is the activation step, not a draft-only action.


Choose the triggering event
- When a record is submitted: create follow-up work at the record submission event.
- When the final decision is recorded: configure follow-up at the final-decision stage. In the current dialog, the activation message describes records approved from that point onward receiving the task; review that message and test the decision outcome your process relies on.
- When a party is submitted: create a task for each party when its submission event occurs.
- When a party is approved: create a task for each party at its approval event.
A record template creates one task per record; a party template creates one task per party. Choose a party event when the work must be tracked separately for each party, rather than once for the entire record.
Choose the assignee
- The submitter: use when the person who submitted the record should carry out the follow-up.
- The approver of a stage: select the relevant Stage after choosing this option.
Check that the selected stage matches your intended owner. Validate the resulting assignment with a representative record, particularly if approval routing varies between records.
Configure the due date
The Due date based on menu offers:
- Submission date
- Final approval date
- Request expiration date
- Final approval date, by risk band
For a date-based rule, set the number of days and choose before or after the selected date. For a risk-band rule, enter the separate Low risk, Medium risk, and High risk values shown in the dialog.
Example: a document request assigned to the submitter could be due seven days after final approval. A risk-based follow-up could use shorter deadlines for high-risk records. These are process examples; choose deadlines that match your program and verify them on generated tasks.
When using an expiration-based rule, confirm that the record has the relevant expiration date. When using risk bands, validate the resulting deadlines for the risk levels your form actually produces.
Base the deadline on the activity date
Choose Activity date when the deadline should be calculated from the activity recorded on the form, then set the number of days before or after it.
In the form builder, open the relevant date question’s Settings and set Standard reporting concept to Activity period. Save and publish the intended form configuration before testing the template. If Activity date is unavailable, check that designation. If a template warns that its field was removed, restore the designation or choose another deadline basis.
Link related parties
The template offers None, The record’s third party, and All parties on the record. Select the scope that matches the work. Related-party selection is separate from deciding whether the trigger runs once per record or once per party.
Set visibility and approval conditions
Restricted limits visibility to people on the task and task administrators. Choose it when the follow-up should not be visible to other users who can read unrestricted tasks.
Condition of approval, when available for the selected event, marks the follow-up as an approval condition. The record shows Approved with conditions while the task is open. Use this for obligations attached to approval, not as a replacement for the approval decision itself.
Refresh and reopen an automatic task
When a supported event happens again, Quantum updates the existing task created by that template. It recalculates the due date and resolves the assignee using the current template and record information.
| Template event | What happens when it occurs again |
|---|---|
| Record approved again | The task’s due date and assignee can update. A completed task reopens when the template’s reopening option is selected. |
| Party submitted again | The task for that party and template can update and, when configured, reopen. |
| Party approved again | The task for that party and template can update and, when configured, reopen. |
| Record submitted again | The reopening option is not active for this event. Its saved setting does not reopen a completed task. |
For supported recurring events, leaving reopening off keeps a completed task completed; its due date and assignee can still update. Use the task’s History to review a recurrence update.
Review templates and configuration changes
The form’s Templates section separates Live and Retired templates. Review the relevant list when investigating unexpected task creation or maintaining the form’s configuration. An empty template list means tasks on those records are created manually.
Task settings on the form are recorded in the audit log. Use System → Audit log to investigate configuration changes, and review the individual task’s History for task activity.
Review task permissions
Open Access → Capabilities and search for task to audit which roles hold each capability.
- task.participate: read and work on tasks assigned to you or shared with you.
- task.create: create a task on a record you can read and manage tasks you created.
- task.read_all: read every unrestricted task on records you can read.
- task.manage_types: manage task categories and types.
- task.administer: read and manage every task, whoever created it.
Use the capability matrix to verify your workspace’s actual role assignments. Task administration includes restricted tasks; assign it only to people who need that responsibility. Catalog management and task administration serve different purposes.
Validate the setup
- Open a record for the configured form and confirm that manual task creation offers the intended category and type.
- Trigger the configured event on a test record or party after making the template live.
- Verify the generated task’s title, instructions, type, assignee, due date, related parties, origin, restriction and condition setting.
- Check the assignee’s Home page for Complete · Tasks.
- Verify visibility with the intended participant and reviewer roles.
- Complete the test task with a note and confirm that it leaves the active work list and remains in the record’s task history.
- For approval conditions, verify the record’s status before and after the open conditions are resolved.
- For recurring templates, repeat the relevant approval or party-submission event and verify the expected due-date, assignee and reopening behavior.
Troubleshooting
A type is missing from Create task
Check that the type is active in Task types, selected under this form’s Task types offered, and being looked for under the correct category.
A template’s task-type list is empty
First offer a task type on the form’s Tasks tab, then reopen the template dialog.
An automatic task did not appear
Confirm that the template is live, the correct event occurred after activation, and you are looking at the correct record or party. Review assignment and visibility. Test the specific final-decision outcome rather than assuming every outcome creates the same task.
A deadline is unexpected
Check the date basis, number of days, before/after selection and risk-band values. Compare the generated task with the record’s source date and risk level.
Publishing the form did not change Tasks settings
Tasks settings are live configuration and separate from form publishing. Check the saved Tasks settings and audit log.
A completed task did not reopen
Check the template’s triggering event and reopening setting. Record-level submission does not currently reopen completed tasks. For supported events, confirm that the template is live and the corresponding approval or party submission occurred. Inspect the existing task and History before creating another task.