ROAD: Roadmap
The ROAD entity: A financial roadmap for a project, containing annual budget lines with monthly forecast and actual data.
Default definition. This article describes the default
ROAD 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 ROAD.Entity properties
| Property | Value |
|---|---|
| Entity code | ROAD |
| Display name | Roadmap |
| Plural | Roadmaps |
| Level | 445 |
Use cases
ROAD is a project-level financial planning entity at level 445. The General panel uses a 50/50 split: left column links to the parent project (PJ objectLookup, readonly), level, and ID; right column shows created/updated timestamps. The Financial Lines panel has a full-width relatedlist of ROADLINE entities linked via comboKey format SUB|PJ|ROAD|ROADLINE, with addnew enabled and hideaddexisting set.
Each line shows name, year, budget, revised, MTP, total forecast, and total actual.
Fields
Roadmap
| Field | Type | Required | Notes |
|---|---|---|---|
projectId | reference → PJ | Read-only. Project | |
level | number | Level | |
id | text | Read-only. ID |
Summary
| Field | Type | Required | Notes |
|---|---|---|---|
created | datetime | Read-only. Created | |
updated | datetime | Read-only. Updated |
Relationships
- Lookups:
projectIdpoints at aPJrecord. - Related lists:
ROADLINE(formatSUB|PJ|ROAD|ROADLINE).
Creating a Roadmap via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "ROAD",
"level": 445,
"comboKey": "SUB:|ENT:"
} Listing Roadmaps records
GET /v1/entities/ROAD/SUB