DRAWDOWN: Roadmap drawdown
A roadmap budget drawdown entry recording how much budget a project consumes from its portfolio allocation.
DRAWDOWN 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 DRAWDOWN.Entity properties
| Property | Value |
|---|---|
| Entity code | DRAWDOWN |
| Display name | Roadmap drawdown |
| Plural | Roadmap drawdowns |
| Level | 2000 |
Use cases
DRAWDOWN tracks budget consumption against portfolio roadmap allocations. Each record links a project (PJ via objectLookup) to a drawdown amount (currency value), recording when and how much budget has been drawn from the portfolio. It is linked to portfolios via comboKey SUB|PORT, appearing as a related list on the Portfolio's Roadmap drawdown panel. The entity is intentionally lightweight - name, project reference, and value - because it serves as a financial transaction record rather than a complex governance object. The AI features (ai:true, context.getDivisonUnitData) enable analysis of drawdown patterns across the portfolio. Each drawdown entry has an ownerId and created timestamp for audit purposes, visible in the portfolio's drawdown grid.
Fields
Basic Info
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Mame. | |
project | reference → PJ | Project. | |
value | number | Drawndown amount. |
Relationships
- Lookup:
project(reference →PJ).
Creating a Roadmap drawdown via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "DRAWDOWN",
"level": 2000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"value": 0
}Listing Roadmap drawdowns records
GET /v1/entities/DRAWDOWN/SUB:<your-sub-id>