DCOMMENT: Document Comment
A review comment on a document version with resolution status tracking and threaded responses.
DCOMMENT 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 DCOMMENT.Entity properties
| Property | Value |
|---|---|
| Entity code | DCOMMENT |
| Display name | Document Comment |
| Plural | Document Comments |
| Level | 12040 |
Use cases
DCOMMENT captures review feedback on document versions, linked via comboKey SUB|DRECORD|DVERSION|DCOMMENT. The comment text (name field) is readonly after creation to preserve the audit trail. Status tracking (Open > Resolved > Closed) with resolvedBy and resolvedDate provides evidence of comment disposition - essential for regulated document management. Responses (DRESPONSE) are linked via the five-part comboKey SUB|DRECORD|DVERSION|DCOMMENT|DRESPONSE, creating threaded discussions. The hiddenOnNew property on the status field hides the resolution workflow when creating a new comment, simplifying the creation form. The autoOpen:true setting means comments open in the editor immediately when clicked in the parent version's comment list, streamlining the review workflow.
Fields
Comment
| Field | Type | Required | Notes |
|---|---|---|---|
name | text (multi-line) | Yes | Comment. Read only. |
Resolution
| Field | Type | Required | Notes |
|---|---|---|---|
ownerId | reference → user | Comment. Read only. | |
created | date | Created Date. Read only. | |
status | enum | Yes | Valid ids: open (Open), resolved (Resolved), closed (Closed). |
resolvedBy | reference → user | Resolved By. Read only. | |
resolvedDate | date | Resolved Date. Read only. |
Relationships
- Related list:
DRESPONSE, comboKey formatSUB|DRECORD|DVERSION|DCOMMENT|DRESPONSE.
Creating a Document Comment via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "DCOMMENT",
"level": 12040,
"comboKey": "SUB:<your-sub-id>|ENT:",
"status": "open"
}Listing Document Comments records
GET /v1/entities/DCOMMENT/SUB:<your-sub-id>