Document Family Commands
Thekdx document-family command provides operational tools for document families that already exist in the platform. Use it to export extracted data, download the KDDB content object behind a processed document, and update labels or statuses for operational workflows.
A document family is the platform record that ties a source document, its content objects, derived data, labels, status, tasks, and processing history together.
Available Commands
| Command | Description |
|---|---|
data | Export extracted JSON data from the latest content object |
content list | List content objects in a document family |
content download | Download a content object as a .kddb file |
add-label | Add a label to a document family |
remove-label | Remove a label from a document family |
set-status | Set the document-family status |
Export Extracted Data
Retrieve the extracted and transformed data from a processed document family.Flags
| Flag | Default | Description |
|---|---|---|
-o, --output | stdout | Output file path |
--include-ids | true | Include element IDs in output |
--friendly-names | false | Use friendly names for fields |
--inline-audits | false | Include inline audit information |
--include-exceptions | false | Include exception information |
Examples
Output Shape
The command exports formatted JSON from the latest content object.--include-ids is enabled, each data element includes an _id field that can be used for traceability and audit review.
Content Object Operations
Document families contain one or more content objects. A content object is the KDDB representation of a processed document at a point in time.List Content Objects
Download Content
Flags
| Flag | Description |
|---|---|
--latest | Download the most recent content object |
-o, --output | Output file path, defaulting to content-<id>.kddb |
Examples
Labels
Labels are often used for operational routing, progress tracking, and downstream filters.Add a Label
| Argument or flag | Description |
|---|---|
document-family-id | The document family to update |
tag-id | The label/tag UUID to apply |
--path | Optional path within the document to scope the label |
Remove a Label
Status
Statuses are useful when a project models lifecycle states such as received, reviewed, approved, rejected, or archived.When To Use Each Command
| Use case | Command |
|---|---|
| Get structured data for an integration check | kdx document-family data |
| Debug what the platform stored in a processed document | kdx document-family content download --latest |
| See whether multiple content versions exist | kdx document-family content list |
| Mark a document for an operational path | kdx document-family add-label |
| Clear an incorrect operational label | kdx document-family remove-label |
| Move a document to a known lifecycle state | kdx document-family set-status |
Upload, Wait, Export
Troubleshooting
| Symptom | What to check |
|---|---|
no content objects found | The document may not have processed yet, or processing failed before content was saved. |
| Empty JSON export | Confirm the document reached the expected processing label and that the Activity Plan produced structured data. |
Document family not found | Confirm the ID, profile, URL, and permissions. |
| Label or status update fails | Confirm you are passing the server UUID for the label or status, not the display name. |
