ITCHANGE: Change Request
IT change management record for tracking proposed changes to infrastructure, systems, or services with risk assessment, approval workflow, and implementation planning.
Default definition. This article describes the default
ITCHANGE 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 ITCHANGE.Entity properties
| Property | Value |
|---|---|
| Entity code | ITCHANGE |
| Display name | Change Request |
| Plural | Change Requests |
| Level | 50700 |
Use cases
ITCHANGE implements ITIL change management. The workflow is Draft → Submitted → Approved/Rejected → Scheduled → In Progress → Completed/Failed. Submit for Approval validates required fields and moves from Draft to Submitted.
Fields
Change Information
| Field | Type | Required | Notes |
|---|---|---|---|
ref | text | Ref. | |
name | text | Yes | Change ID. |
subject | text | Yes | Subject. |
description | text (multi-line) | Yes | Description. |
changeType | enum | Yes | Valid ids: 1 (Standard), 2 (Normal), 3 (Emergency), 4 (Major). |
status | enum | Yes | Valid ids: 1 (Draft), 2 (Submitted), 3 (Approved), 4 (Rejected), 5 (Scheduled), 6 (In Progress), 7 (Completed), 8 (Failed), 9 (Cancelled). |
priority | enum | Yes | Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low). |
Classification
| Field | Type | Required | Notes |
|---|---|---|---|
category | enum | Valid ids: 1 (Hardware), 2 (Software), 3 (Network), 4 (Access/Permissions), 5 (Email), 6 (Security), 7 (Infrastructure), 8 (Other). | |
impact | enum | Valid ids: 1 (Organisation-wide), 2 (Department), 3 (Multiple Users), 4 (Single User). | |
likelihood | enum | Valid ids: 1 (Very High), 2 (High), 3 (Medium), 4 (Low), 5 (Very Low). | |
riskLevel | enum | Calculated by Risk Assessment toolbar button from likelihood x impact Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low), 5 (None). | |
riskScore | number | Calculated score (1-25) from likelihood x impact matrix |
Requestor & Asset
| Field | Type | Required | Notes |
|---|---|---|---|
requestedBy | reference → user | Requested By. | |
asset | reference → ITASSET | Affected Asset. | |
department | reference → DEPT | Department. | |
service | reference → ITSVC | Affected Service. | |
relatedTicket | reference → TICKET | Related Ticket. | |
release | reference → ITRELEASE | Release. | |
configItem | reference → CMDB | Configuration Item. |
Implementation Plan
| Field | Type | Required | Notes |
|---|---|---|---|
implementationPlan | text (multi-line) | Implementation Plan. | |
rollbackPlan | text (multi-line) | Rollback Plan. | |
testPlan | text (multi-line) | Test Plan. |
Approvals
| Field | Type | Required | Notes |
|---|---|---|---|
submittedBy | reference → user | Submitted By. | |
submittedDate | datetime | Submitted Date. | |
approvedBy | reference → user | Approved/Rejected By. | |
approvalDate | datetime | Approval Date. | |
approvalNotes | text (multi-line) | Approval Notes. |
Schedule
| Field | Type | Required | Notes |
|---|---|---|---|
scheduledStartDate | datetime | Scheduled Start. | |
scheduledEndDate | datetime | Scheduled End. | |
actualStartDate | datetime | Actual Start. | |
actualEndDate | datetime | Actual End. | |
maintenanceWindow | enum | Valid ids: 1 (Yes), 0 (No). |
Post-Implementation Review
| Field | Type | Required | Notes |
|---|---|---|---|
implementationResult | enum | Valid ids: 1 (Successful), 2 (Partial), 3 (Failed). | |
reviewNotes | text (multi-line) | Review Notes. | |
lessonsLearned | text (multi-line) | Lessons Learned. |
Additional panels
- Activity timeline panel attached.
Relationships
- Lookups:
assetpoints at aITASSETrecord;departmentpoints at aDEPTrecord;servicepoints at aITSVCrecord;relatedTicketpoints at aTICKETrecord;releasepoints at aITRELEASErecord;configItempoints at aCMDBrecord;requestedBypoints at a user;submittedBypoints at a user;approvedBypoints at a user. - Related lists:
TICKET.
Creating a Change Request via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "ITCHANGE",
"level": 50700,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"subject": "...",
"description": "...",
"changeType": "1"
}Listing Change Requests
# All records in your tenant
GET /v1/entities/ITCHANGE/SUB:<your-sub-id>