AUDITFINDING: Audit Finding
A trackable finding raised during an audit (internal, external, or facility), linked to specific assets, ISO clauses, and parent audit records.
Default definition. This article describes the default
AUDITFINDING 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 AUDITFINDING.Entity properties
| Property | Value |
|---|---|
| Entity code | AUDITFINDING |
| Display name | Audit Finding |
| Plural | Audit Findings |
| Level | 100020 |
Use cases
A trackable finding raised during an audit (internal, external, or facility), linked to specific assets, ISO clauses, and parent audit records.
Fields
General: Finding Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Title. |
description | text (multi-line) | Description. | |
findingClassification | enum | Classification. Valid ids: majorNC (Major NC), minorNC (Minor NC), observation (Observation), ofi (Opportunity for Improvement), positive (Positive Finding). | |
findingType | enum | Type. Valid ids: redundantEquipment (Redundant Equipment), underutilised (Underutilised Equipment), cabling (Cabling Issue), power (Power Issue), cooling (Cooling Issue), safety (Safety Concern), labelling (Labelling Issue), rackCondition (Rack Condition), roomCondition (Room Condition), lifecycle (End of Life / Support), compliance (Compliance), quality (Quality), security (Information Security), process (Process / Procedure), other (Other). | |
severity | enum | Severity. Valid ids: critical (Critical), high (High), medium (Medium), low (Low), info (Informational). | |
status | enum | Status. Valid ids: open (Open), inProgress (In Progress), resolved (Resolved), deferred (Deferred), wontFix (Won't Fix). |
General: Traceability
| Field | Type | Required | Notes |
|---|---|---|---|
parentAudit | reference → AUDIT | The audit this finding was raised in | |
isoClause | text | ISO Clause Reference. Placeholder: e.g. 9001:2015 clause 8.5.1. | |
relatedAsset | reference → COMPINV | The specific equipment this finding relates to | |
relatedRack | reference → RACK | The rack this finding relates to | |
relatedRoom | reference → ROOM | The room this finding relates to |
General: Recommendation
| Field | Type | Required | Notes |
|---|---|---|---|
recommendation | text (multi-line) | Recommended Action. | |
estimatedSavings | number | Annual cost saving if resolved | |
estimatedCost | number | Estimated Cost to Resolve. | |
reclaimableU | number | Rack units freed if this finding is resolved | |
reclaimablePowerW | number | Power freed if this finding is resolved |
General: Assignment & Tracking
| Field | Type | Required | Notes |
|---|---|---|---|
raisedBy | reference → user | Raised By. | |
raisedDate | date | Raised Date. | |
assignedTo | reference → user | Assigned To. | |
dueDate | date | Due Date. | |
resolvedDate | date | Resolved Date. | |
resolution | text (multi-line) | Resolution Notes. |
Attachments
| Field | Panel | Allowed types | Max files |
|---|---|---|---|
(unnamed) | General | any | multiple |
Relationships
- Lookups:
parentAuditpoints at aAUDITrecord;relatedAssetpoints at aCOMPINVrecord;relatedRackpoints at aRACKrecord;relatedRoompoints at aROOMrecord. - Activity: activity timeline panel attached.
Creating a Audit Finding via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "AUDITFINDING",
"level": 100020,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Title",
"description": "Description",
"findingClassification": "majorNC",
"findingType": "redundantEquipment"
}
Listing Audit Findings records
GET /v1/entities/AUDITFINDING/SUB