PROG: Programme
The PROG entity represents a coordinated group of related projects delivering outcomes that could not be achieved if managed separately.
PROG 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 PROG.Entity properties
| Property | Value |
|---|---|
| Entity code | PROG |
| Display name | Programme |
| Plural | Programmes |
| Level | 100000 |
Use cases
PROG sits between PORT and PJ in the hierarchy (PORT > PROG > PJ). It exists to coordinate related projects that together deliver a strategic outcome. The portfolio objectLookup with comboKey:1 establishes the parent relationship to PORT. Projects link to programmes via comboKey2 (SUB|PROG on PJ), allowing a project to belong to both a portfolio (comboKey) and a programme (comboKey2) independently. Governance fields (status, priority, riskRating, lastReviewDate) support programme-level health monitoring. Programme roles (progroles) capture governance assignments. The finance section includes costs for budget management and a finance tracker (ft) for monthly spend tracking across all child projects.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name. |
description | text (multi-line) | Description. | |
portfolio | reference → PORT | Portfolio. | |
programmeManager | reference → user | Programme Manager. | |
sponsor | reference → user | Executive Sponsor. | |
startDate | date | Start Date. | |
endDate | date | End Date. | |
status | enum | Status. Valid ids: new (New), delivery (Delivery), on_hold (On Hold), closed (Closed). | |
priority | enum | Priority. Valid ids: high (High), medium (Medium), low (Low). | |
riskRating | enum | Risk Rating. Valid ids: low (Low), moderate (Moderate), high (High). | |
lastReviewDate | date | Last Review Date. |
Additional panels
- Dashboard panel.
- progdepmap panel.
- proggantt panel.
- progroles panel.
- costs panel.
- ft panel.
Relationships
- Lookups:
portfoliopoints atPORTrecord. - Related lists:
PJvia formatSUB|PROG;PROGGATEvia formatSUB|PROG.
Creating a Programme via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "PROG",
"level": 100000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"description": "Long description text.",
"portfolio": "",
"programmeManager": ""
} Listing PROG records
# All programmes in your tenant
GET /v1/entities/PROG/SUB