DRESPONSE: Document Comment Response
A reply to a document comment, forming a threaded discussion within the document review process.
DRESPONSE definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches DRESPONSE.Entity properties
| Property | Value |
|---|---|
| Entity code | DRESPONSE |
| Display name | Document Comment Response |
| Plural | Document Comment Responses |
| Level | 12040 |
Use cases
DRESPONSE is the leaf entity in the DMS hierarchy (DRECORD > DVERSION > DCOMMENT > DRESPONSE), linked via the five-part comboKey SUB|DRECORD|DVERSION|DCOMMENT|DRESPONSE. It is intentionally minimal - just a response text (name field, readonly after creation) with author (ownerId) and date (created). Unlike DCOMMENT, it has no status workflow because responses do not need independent resolution tracking - they contribute to the resolution of their parent comment. The deep comboKey nesting ensures responses are precisely scoped to their specific comment within a specific version of a specific document, maintaining full traceability in the review thread.
Fields
Response
| Field | Type | Required | Notes |
|---|---|---|---|
name | text (multi-line) | Yes | Response. Read only. |
Resolution
| Field | Type | Required | Notes |
|---|---|---|---|
ownerId | reference → user | Comment. Read only. | |
created | date | Created Date. Read only. |
Relationships
- No declared relationships in the default definition.
Creating a Document Comment Response via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "DRESPONSE",
"level": 12040,
"comboKey": "SUB:<your-sub-id>|ENT:"
}Listing Document Comment Responses records
GET /v1/entities/DRESPONSE/SUB:<your-sub-id>