A task template is the YAML blueprint for a piece of human work. Projects bind to a task template via project resources, and every task created from that template inherits its options, forms, document family groups, and action buttons. This section is the developer-facing companion to the Studio Task Templates reference. It focuses on the patterns that show up repeatedly in real review workflows — gating actions on data quality, recording reviewer ownership, and making sure event subscriptions and AI agents stay out of the reviewer’s way once a value has been accepted.Documentation Index
Fetch the complete documentation index at: https://developer.kodexa.ai/llms.txt
Use this file to discover all available pages before exploring further.
When to reach for a task template
Use a task template whenever a person needs to look at extracted data, decide something, and click a button:- Reviewing extracted invoice data before payment
- Approving or rejecting a document classification
- Resolving exceptions raised by validation rules
- Confirming that an AI-generated summary is correct
Cookbook recipes
These recipes solve concrete problems that come up in nearly every review workflow. Each recipe is independent — pick the ones you need.Gating actions on exceptions
Only allow the reviewer to approve when the data they care about is clean.
Take-ownership pattern
Record that a reviewer accepted a value, and stop AI from quietly overwriting it.
Related reading
- Task Templates in Studio — visual editor walkthrough
- Activity Plans — how multiple tasks chain together
- Data Definitions: event subscriptions — where AI/automation may try to write
- Data Definitions: validation rules — what creates the exceptions you’ll gate on