A Task is a unit of human work inside an Activity. It is owned, reviewable, completable, and tied to the business process when the platform needs a person to make a decision, resolve an exception, or confirm extracted data. Tasks are not the whole workflow and they are not the primary process model. They are how people participate in an Activity.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.
What Tasks Are For
Tasks exist where automation should pause for judgment:- Review extracted fields before a process continues
- Resolve validation errors or missing data
- Approve or reject a business decision
- Route an exception to the right queue
- Capture a user decision that determines the next Activity step
Task Shape
| Area | Purpose |
|---|---|
| Owner or queue | Who should work on it? |
| Status | Is it open, in progress, blocked, complete, rejected, or canceled? |
| Document context | Which document, packet, or extracted data is being reviewed? |
| Data form | Which review UI should the user see? |
| Actions | What decisions can the user make? |
| Exceptions | Which issues need attention before completion? |
| Audit | Who completed the work, when, and with what result? |
Tasks in an Activity
An Activity creates a Task when a configured step needs a person. The Task completion result becomes workflow state that can drive the next Activity step.What Belongs in a Task
A Task should be specific enough that a person can finish it without reconstructing the entire process. Good Tasks:- Review this invoice extraction
- Resolve these validation exceptions
- Approve this loan packet summary
- Confirm this vendor match
- Reject this claim intake with a reason
- Process this business workflow
- Run invoice automation
- Handle the loan process
- Figure out what happened