INCIDENT: Incident
An incident record with severity classification, root cause analysis, resolution tracking, and preventive actions.
Default definition. This article describes the default
INCIDENT 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 INCIDENT.Entity properties
| Property | Value |
|---|---|
| Entity code | INCIDENT |
| Display name | Incident |
| Plural | Incidents |
| Level | 55500 |
Use cases
INCIDENT is a more detailed event-tracking entity than ISSUE, designed for significant unplanned events requiring formal investigation and resolution. It is linked to projects via comboKey SUB|PJ. Key differentiators from ISSUE: severity levels with color coding (Critical/High/Medium/Low), separate occurred and discovered dates to track detection lag, multiselect impact areas (Schedule, Budget, Quality, Scope, Resources, Customer, Reputation, Compliance), and a full root cause analysis panel.
Fields
Incident Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Incident Title. |
description | text (multi-line) | Yes | Description. |
incidentDate | date | Yes | Date Occurred. |
discoveredDate | date | Yes | Date Discovered. |
reporter | reference → user | Yes | Reported By. |
assignedTo | reference → user | Yes | Assigned To. |
Classification & Impact
| Field | Type | Required | Notes |
|---|---|---|---|
severity | enum | Yes | Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low). |
category | enum | Yes | Valid ids: technical (Technical), operational (Operational), security (Security), process (Process), human_error (Human Error), external (External). |
impactType | array of enums | Valid ids: 1 (Schedule), 2 (Budget), 3 (Quality), 4 (Scope), 5 (Resources), 6 (Customer), 7 (Reputation), 8 (Compliance). | |
affectedSystems | text (multi-line) | Affected Systems/Components. | |
businessImpact | text (multi-line) | Business Impact. |
Status & Priority
| Field | Type | Required | Notes |
|---|---|---|---|
status | enum | Yes | Valid ids: 1 (New), 2 (Investigating), 3 (In Progress), 4 (Resolved), 5 (Closed). |
priority | enum | Yes | Valid ids: 1 (Immediate), 2 (High), 3 (Medium), 4 (Low). |
estimatedCost | number | Estimated Cost Impact. | |
actualCost | number | Actual Cost Impact. |
Root Cause Analysis
| Field | Type | Required | Notes |
|---|---|---|---|
rootCause | text (multi-line) | Underlying cause of the incident | |
contributingFactors | text (multi-line) | Contributing Factors. | |
timeline | text (multi-line) | Chronological sequence of events |
Resolution Actions
| Field | Type | Required | Notes |
|---|---|---|---|
immediateActions | text (multi-line) | Immediate Actions Taken. | |
resolutionActions | text (multi-line) | Resolution Actions. | |
resolutionDate | datetime | Resolution Date. | |
verificationDate | date | When resolution was verified |
Prevention Measures
| Field | Type | Required | Notes |
|---|---|---|---|
preventiveActions | text (multi-line) | Actions to prevent recurrence | |
processImprovements | text (multi-line) | Process Improvements. | |
lessonsLearned | text (multi-line) | Lessons Learned. | |
communicationPlan | text (multi-line) | How lessons will be shared |
Additional panels
- Activity timeline panel attached.
Relationships
- Lookups:
reporterpoints at a user;assignedTopoints at a user.
Creating a Incident via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "INCIDENT",
"level": 55500,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"description": "...",
"incidentDate": "2026-01-15",
"discoveredDate": "2026-01-15"
}Listing Incidents
# All records in your tenant
GET /v1/entities/INCIDENT/SUB:<your-sub-id>