DAPPROVAL: Document Approval
A document approval record tracking an approver's decision (pending, approved, or rejected) on a version.
DAPPROVAL 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 DAPPROVAL.Entity properties
| Property | Value |
|---|---|
| Entity code | DAPPROVAL |
| Display name | Document Approval |
| Plural | Document Approvals |
| Level | 12040 |
Use cases
DAPPROVAL records individual approval decisions on document versions. It uses view:simple (flat field list rather than panelled layout) because it is a lightweight workflow record typically managed through the parent version's approval panel (dversionapprovals) rather than opened independently. The name field is a singleuser lookup identifying the approver (readonly, set by the system). Status tracks the decision (Pending > Approved/Rejected) with decisionBy and decisionDate recording who acted and when. The approverComment field captures the approver's feedback. All audit fields (ownerId/created for request, decisionBy/decisionDate for response) are readonly to maintain integrity. Multiple DAPPROVAL records per version support multi-party approval workflows where several approvers must sign off.
Fields
No form fields in the default definition.
Relationships
- No declared relationships in the default definition.
Creating a Document Approval via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "DAPPROVAL",
"level": 12040,
"comboKey": "SUB:<your-sub-id>|ENT:"
}Listing Document Approvals records
GET /v1/entities/DAPPROVAL/SUB:<your-sub-id>