MILESTONE: Milestone
A standalone initiative milestone for tracking key dates, deliverables, approvals, and progress on strategic work.
Default definition. This article describes the default
MILESTONE 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 MILESTONE.Entity properties
| Property | Value |
|---|---|
| Entity code | MILESTONE |
| Display name | Milestone |
| Plural | Milestones |
| Level | 14000 |
Use cases
MILESTONE is a general-purpose milestone entity for initiatives (INI) and other strategic work, distinct from PJMS which is specifically tied to projects. It uses text-based responsible/accountable fields rather than user lookups, making it more flexible for cross-organisational milestone tracking where the responsible party may not be a system user. The type field classifies milestones (Deliverable, Approval, Decision Point, Phase Gate, Review, Launch, Completion) for filtering and reporting.
Fields
Basic Information
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Milestone Name |
code | text | Milestone Code | |
type | enum | Yes | Type Valid ids: deliverable (Deliverable), approval (Approval), decision (Decision Point), phase (Phase Gate), review (Review), launch (Launch), completion (Completion), other (Other). |
status | enum | Status Valid ids: pending (Pending), in_progress (In Progress), completed (Completed), delayed (Delayed), cancelled (Cancelled), on_hold (On Hold). | |
priority | enum | Priority Valid ids: critical (Critical), high (High), medium (Medium), low (Low). | |
description | text (multi-line) | Description |
Success Criteria
| Field | Type | Required | Notes |
|---|---|---|---|
acceptanceCriteria | text (multi-line) | Acceptance Criteria | |
deliverables | text (multi-line) | Key Deliverables |
Timeline
| Field | Type | Required | Notes |
|---|---|---|---|
targetDate | date | Yes | Target Date |
originalDate | date | Original Target Date Read only. | |
completedDate | date | Completed Date | |
startDate | date | Start Date | |
duration | number | Duration (days) | |
percentComplete | number | Percent Complete | |
delayReason | text (multi-line) | Delay Reason |
Dependencies
| Field | Type | Required | Notes |
|---|---|---|---|
predecessors | text (multi-line) | Predecessor Milestones | |
successors | text (multi-line) | Successor Milestones | |
dependencies | text (multi-line) | Other Dependencies |
Ownership & Accountability
| Field | Type | Required | Notes |
|---|---|---|---|
responsible | text | Responsible Person | |
accountable | text | Accountable Person | |
department | text | Department | |
stakeholders | text (multi-line) | Key Stakeholders | |
approver | text | Approver |
Risk & Impact
| Field | Type | Required | Notes |
|---|---|---|---|
riskLevel | enum | Risk Level Valid ids: low (Low), medium (Medium), high (High), critical (Critical). | |
impactOfDelay | enum | Impact of Delay Valid ids: minimal (Minimal), moderate (Moderate), significant (Significant), severe (Severe). | |
risks | text (multi-line) | Key Risks | |
mitigationPlan | text (multi-line) | Mitigation Plan |
Review Process
| Field | Type | Required | Notes |
|---|---|---|---|
reviewRequired | boolean | Review Required | |
reviewDate | date | Review Date | |
reviewStatus | enum | Review Status Valid ids: pending (Pending), scheduled (Scheduled), in_progress (In Progress), completed (Completed). | |
reviewComments | text (multi-line) | Review Comments |
Approval Process
| Field | Type | Required | Notes |
|---|---|---|---|
approvalRequired | boolean | Approval Required | |
approvalDate | date | Approval Date | |
approvalStatus | enum | Approval Status Valid ids: pending (Pending), approved (Approved), rejected (Rejected), conditional (Conditional). | |
approvalComments | text (multi-line) | Approval Comments | |
conditions | text (multi-line) | Conditions (if any) |
Documents
| Field | Type | Required | Notes |
|---|---|---|---|
documents | file |
Activity. Activity timeline panel attached.
Relationships
- No declared relationships in the default definition.
Creating a Milestone via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "MILESTONE",
"level": 14000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"type": "deliverable",
"targetDate": "2026-01-01"
}Listing Milestones records
# All milestones in your tenant
GET /v1/entities/MILESTONE/SUB