Kodexa is a platform for running document-heavy business processes where automation, human review, institutional knowledge, and audit trails need to stay aligned. The Concepts section starts with the business problem first. Activities are how the platform shows up in the workflow: a run of automated work with inputs, steps, state, and results. Tasks are how people show up in that workflow: reviewable, assignable units of human work when judgment or exception handling is needed.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.
Mental Model
Kodexa models real-world business workflow challenges around unstructured data by starting with Activity. Tasks are incorporated into that Activity model as the human-work points where judgment, approval, exception handling, or correction is needed.- Activity: a run of automated work, defined by an Activity Plan, with inputs, steps, dependencies, status, logs, and results.
- Task: a unit of human work inside an Activity, owned by a person or queue, reviewable, completable, and tied to the workflow when judgment is needed.
- Workflow: the choreography between Activities and Tasks. Activities create Tasks when a human decision is needed; Tasks can start Activities when their status changes.
- Project: the workspace where the right document types, resources, Activity Plans, review surfaces, and permissions are bound together for a business use case.
Where To Go Next
- Activities explain how Kodexa models automated business process runs.
- Tasks explain where human review and judgment fit inside those runs.
- Projects explain the workspace boundary for a business process.
- Project templates explain reusable project setup.
- Activity Plans explain how automated work is configured and run.
- Knowledge system explains how Kodexa represents reusable knowledge.
- Working with exceptions explains where human review fits.