RISK: Risk
The RISK entity: A risk register entry with probability, impact, cost assessment, mitigation strategy, and contingency planning.
RISK 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 RISK.Entity properties
| Property | Value |
|---|---|
| Entity code | RISK |
| Display name | Risk |
| Plural | Risks |
| Level | 55000 |
Use cases
RISK is the project risk register entity, linked to projects via comboKey SUB|PJ. It follows the standard risk management model with probability and impact assessments (both Low/Medium/High), category classification (Technical, Financial, Operational, Resource, Legal, Environmental), and cost impact estimation. The management section captures mitigation strategy, triggers/warning signs, and contingency plan - all required fields, enforcing thorough risk documentation.
Status tracking (Open, Closed, Monitoring, Resolved) with next_review_date supports periodic risk reviews. Note the Status field has an uppercase 'S' in its id, which is a quirk in the definition. Risks appear as related lists on PJ with category as a secondary field for grouped display.
Fields
Risk
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Risk |
description | text | Yes | Description |
Impact
| Field | Type | Required | Notes |
|---|---|---|---|
category | enum | Yes | Risk Category Valid ids: technical (Technical), financial (Financial), operational (Operational), resource (Resource), legal (Legal), environmental (Environmental). |
probability | enum | Yes | Probability of occurence Valid ids: low (Low), medium (Medium), high (High). |
impact | enum | Yes | Impact of occurence Valid ids: low (Low), medium (Medium), high (High). |
cost | number | Potential cost impact |
Manage
| Field | Type | Required | Notes |
|---|---|---|---|
mitigation_strategy | text (multi-line) | Yes | Mitigation Strategy |
triggers | text (multi-line) | Yes | Triggers / Warning Signs |
contingency_plan | text (multi-line) | Yes | Contingency Plan |
Status | enum | Yes | Impact of occurence Valid ids: open (Open), closed (Closed), monitoring (Monitoring), resolved (Resolved). |
next_review_date | date | Next Review Date |
Relationships
- No declared relationships in the default definition.
Creating a Risk via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "RISK",
"level": 55000,
"comboKey": "SUB:|ENT:",
"name": "Example name",
"description": "Example value",
"category": "technical",
"probability": "low"
} Listing Risks records
GET /v1/entities/RISK/SUB