DECISION: Decision
A formal decision record capturing what was decided, the rationale, and resulting impacts.
DECISION 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 DECISION.Entity properties
| Property | Value |
|---|---|
| Entity code | DECISION |
| Display name | Decision |
| Plural | Decisions |
| Level | 540 |
Use cases
DECISION records formal governance decisions made within projects, typically during meetings. It uses comboKey SUB|PJ|MEETING when created from a meeting context, or SUB|PJ when created directly from a project. The status workflow (Proposed > Approved > Implemented > Superseded > Rejected) tracks the decision lifecycle. The rationale and impacts fields provide an audit trail explaining why a decision was made and what consequences it has. The decision_date and owner fields establish accountability. This entity supports compliance and governance requirements where organisations need to demonstrate that decisions were properly documented, authorised, and communicated.
Fields
Decision Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Title. |
decision_date | date | Yes | Decision Date. |
owner | reference → user | Decision Owner. | |
status | singleselect | Status. |
Decision Context
| Field | Type | Required | Notes |
|---|---|---|---|
description | text (multi-line) | Describe what was decided and why. | |
rationale | text (multi-line) | Document the reasoning or trade-offs considered. | |
impacts | text (multi-line) | Impacts / Consequences. |
Attachments
| Field | Type | Required | Notes |
|---|---|---|---|
attachments | file | Allowed types: any. |
Relationships
- No declared relationships in the default definition.
Creating a Decision via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "DECISION",
"level": 540,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"decision_date": "2026-01-15",
"description": "Example value",
"rationale": "Example value"
}Listing Decisions records
GET /v1/entities/DECISION/SUB:<your-sub-id>