DREVIEW: Document Review
A document review record tracking a reviewer's assessment status and feedback on a version.
DREVIEW 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 DREVIEW.Entity properties
| Property | Value |
|---|---|
| Entity code | DREVIEW |
| Display name | Document Review |
| Plural | Document Reviews |
| Level | 12040 |
Use cases
DREVIEW records individual review assignments on document versions, parallel to DAPPROVAL but for the review (rather than approval) stage of the workflow. Like DAPPROVAL, it uses view:simple for a flat layout managed through the parent version's review panel (dversionreviews). The status workflow is more granular than approval (Not Started > In Review > Needs Changes > Reviewed > Reopened > Cancelled), reflecting the iterative nature of document review where changes may be requested and the review reopened. The reviewerComment field captures detailed feedback. The resolvedBy and resolvedDate fields record when the review was completed. Multiple DREVIEW records per version support multi-reviewer workflows. Reviews typically precede approvals in the document lifecycle (Under Review > Pending Approval).
Fields
No form fields in the default definition.
Relationships
- No declared relationships in the default definition.
Creating a Document Review via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "DREVIEW",
"level": 12040,
"comboKey": "SUB:<your-sub-id>|ENT:"
}Listing Document Reviews records
GET /v1/entities/DREVIEW/SUB:<your-sub-id>