ITMAINT: IT Maintenance
Maintenance record for an IT asset covering scheduled servicing, repairs, upgrades, and inspections with cost and outcome tracking.
Default definition. This article describes the default
ITMAINT 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 ITMAINT.Entity properties
| Property | Value |
|---|---|
| Entity code | ITMAINT |
| Display name | IT Maintenance |
| Plural | IT Maintenance Records |
| Level | 50100 |
Use cases
ITMAINT tracks individual maintenance events against IT assets via comboKeyEntity relationship to ITASSET. Each record captures what was done (maintenanceType), when (maintenanceDate/completedDate), who did it (performedBy/vendor), what it cost, and the outcome. The maintenanceType field uses indexedSelect with categories covering the common maintenance activities: Preventive (scheduled), Corrective (break-fix), Upgrade (hardware/firmware), Inspection, Cleaning, and Calibration.
Fields
Maintenance Record
| Field | Type | Required | Notes |
|---|---|---|---|
ref | text | Ref. | |
name | text | Yes | Maintenance ID. |
asset | reference → ITASSET | Yes | IT Asset. |
maintenanceType | enum | Yes | Valid ids: 1 (Preventive), 2 (Corrective), 3 (Upgrade), 4 (Inspection), 5 (Cleaning), 6 (Calibration). |
status | enum | Yes | Valid ids: 1 (Scheduled), 2 (In Progress), 3 (Completed), 4 (Cancelled). |
priority | enum | Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low). |
Schedule
| Field | Type | Required | Notes |
|---|---|---|---|
maintenanceDate | date | Yes | Maintenance Date. |
completedDate | date | Completed Date. | |
nextScheduledDate | date | Next Scheduled Date. | |
frequency | enum | Valid ids: 0 (One-off), 1 (Weekly), 2 (Monthly), 3 (Quarterly), 4 (Semi-Annual), 5 (Annual). |
Assignment
| Field | Type | Required | Notes |
|---|---|---|---|
performedBy | reference → user | Performed By. | |
vendor | reference → VEN | External Vendor. | |
requestedBy | reference → user | Requested By. |
Work Performed
| Field | Type | Required | Notes |
|---|---|---|---|
description | text (multi-line) | Yes | Description. |
workPerformed | text (multi-line) | Work Performed. | |
partsUsed | text (multi-line) | Parts Used. | |
outcome | enum | Valid ids: 1 (Resolved), 2 (Partially Resolved), 3 (Unresolved), 4 (Escalated), 5 (Replaced). |
Cost & Warranty
| Field | Type | Required | Notes |
|---|---|---|---|
cost | number | Cost. | |
labourHours | number | Labour Hours. | |
partsCost | number | Parts Cost. | |
labourCost | number | Labour Cost. | |
warrantyCovered | enum | Valid ids: 1 (Yes), 0 (No), 2 (Partial). | |
warrantyClaimRef | text | Warranty Claim Reference. | |
notes | text (multi-line) | Notes. |
Relationships
- Lookups:
assetpoints at aITASSETrecord;vendorpoints at aVENrecord;performedBypoints at a user;requestedBypoints at a user.
Creating a IT Maintenance via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "ITMAINT",
"level": 50100,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"asset": "",
"maintenanceType": "1",
"status": "1"
} Listing IT Maintenance Records
# All records in your tenant
GET /v1/entities/ITMAINT/SUB:<your-sub-id>