Project demands
The quantity and date that a project requires for planning and fulfillment.
Fields
The API name is what the API, MCP and the CLI use.
| Name | API name | Type | Required | Description |
|---|---|---|---|---|
| ID | id | Record ID | Yes | |
| Project | projectId | Reference | Yes | |
| Item | productitemId | Reference | ||
| Quantity | quantity | Quantity | Yes | Quantity in the catalog unit after any unit conversion on the line. |
| Item | customitemId | Reference | ||
| Deliverable | projectdeliverableId | Reference | ||
| Work breakdown element | projectwbselementId | Reference | ||
| Catalog | catalog | Constant | Yes | Fixed option from the allowed set for this field. |
| Treatment | treatment | Constant | Yes | Consumable includes fulfillment through linked sales lines. Independent plans the quantity on its own. |
| Withhold from planning | withholdPlanning | Boolean | Yes | Planning ignores this demand. |
| Date required | dateRequired | Date | Yes | Calendar date without time of date. |
| Description | description | Text Area | ||
| Data | data | Data | ||
| Created by | createdBy | User | ||
| Created at | createdAt | Date and Time | Yes | |
| Updated by | updatedBy | User | ||
| Updated at | updatedAt | Date and Time | Yes | |
| Confirmed by | confirmedBy | User | ||
| Confirmed at | confirmedAt | Date and Time | ||
| Canceled by | canceledBy | User | ||
| Canceled at | canceledAt | Date and Time | ||
| Superseded by | supersededBy | User | ||
| Superseded at | supersededAt | Date and Time | ||
| Blocked by | blockedBy | User | ||
| Blocked at | blockedAt | Date and Time | ||
| Archived by | archivedBy | User | ||
| Archived at | archivedAt | Date and Time |
Relations
Owned records (solid line) are deleted with their owner. Grouped records (dashed line) can exist alone.
| Field | Points to | Kind |
|---|---|---|
Project projectId | Projects | owned by |
Deliverable projectdeliverableId | Project deliverables | reference |
Work breakdown element projectwbselementId | Work breakdown elements | reference |
Actions
What you can do with a record. Every action also sends the webhook event projectdemands.<action>. Reads (find, get, count) work on every table.
| Name | API name | Description | Where |
|---|---|---|---|
| Create | create | Add a new demand. | App · WebMCP · API · MCP · CLI |
| Edit | update | Save changes to this demand. | App · API · MCP · CLI |
| Supersede | supersede | Replace this demand with a newer one. | App · API · CLI |
| Firm | confirm | Fix this demand so planning treats it as committed. | App · API · CLI |
| Delete | delete | Delete this demand and the data that belongs with it. This cannot be undone. | App · WebMCP · API · MCP · CLI |
States
How a record moves from state to state. Archive and block can happen in any state.