NWCHANGE: Network Change
Network change management record for tracking proposed changes to telecom platform instances, network infrastructure, or services with risk assessment, approval workflow, and implementation planning.
Default definition. This article describes the default
NWCHANGE 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 NWCHANGE.Entity properties
| Property | Value |
|---|---|
| Entity code | NWCHANGE |
| Display name | Network Change |
| Plural | Network Changes |
| Level | 6700 |
Use cases
NWCHANGE is the network operations equivalent of ITCHANGE (IT 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 |
|---|---|---|---|
name | text | Yes | Change ID |
subject | text | Yes | Subject |
description | text (multi-line) | Yes | Description |
changeType | enum | Yes | Change Type Valid ids: 1 (Standard), 2 (Normal), 3 (Emergency), 4 (Major). |
status | enum | Yes | Status Valid ids: 1 (Draft), 2 (Submitted), 3 (Approved), 4 (Rejected), 5 (Scheduled), 6 (In Progress), 7 (Completed), 8 (Failed), 9 (Cancelled). |
priority | enum | Yes | Priority Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low). |
Classification
| Field | Type | Required | Notes |
|---|---|---|---|
category | enum | Category Valid ids: 1 (Radio/RF), 2 (Transport), 3 (Core Network), 4 (IP/MPLS), 5 (Optical), 6 (Access Network), 7 (Power/Environmental), 8 (Security), 9 (Configuration), 10 (Capacity), 11 (Other). | |
impact | enum | Impact Valid ids: 1 (Network-wide), 2 (Regional), 3 (Single Site), 4 (Single Element). | |
likelihood | enum | Likelihood 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 Read only. Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low), 5 (None). | |
riskScore | number | Calculated score (1-25) from likelihood x impact matrix Read only. |
Requestor & Platform
| Field | Type | Required | Notes |
|---|---|---|---|
requestedBy | reference → user | Requested By | |
platformInstance | reference → NWPLATINST | Affected Platform | |
department | reference → DEPT | Department | |
site | reference → SITE | Site | |
affectedAssets | array of references → COMPINV | Affected Assets | |
service | reference → NWSVC | Affected Network Service | |
relatedTicket | reference → NWTICKET | Related Ticket |
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 Read only. | |
submittedDate | datetime | Submitted Date Read only. | |
approvedBy | reference → user | Approved/Rejected By Read only. | |
approvalDate | datetime | Approval Date Read only. | |
approvalNotes | text (multi-line) | Approval Notes Read only. |
Schedule
| Field | Type | Required | Notes |
|---|---|---|---|
scheduledStartDate | datetime | Scheduled Start | |
scheduledEndDate | datetime | Scheduled End | |
actualStartDate | datetime | Actual Start | |
actualEndDate | datetime | Actual End | |
maintenanceWindow | enum | Maintenance Window Valid ids: 1 (Yes), 0 (No). |
Post-Implementation Review
| Field | Type | Required | Notes |
|---|---|---|---|
implementationResult | enum | Implementation Result Valid ids: 1 (Successful), 2 (Partial), 3 (Failed). | |
reviewNotes | text (multi-line) | Review Notes | |
lessonsLearned | text (multi-line) | Lessons Learned |
Activity. Activity timeline panel attached.
Relationships
- Lookups:
platformInstancepoints at aNWPLATINSTrecord.departmentpoints at aDEPTrecord.sitepoints at aSITErecord.affectedAssetspoints at aCOMPINVrecord.servicepoints at aNWSVCrecord.relatedTicketpoints at aNWTICKETrecord. - Related lists:
NWTICKET.
Creating a Network Change via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "NWCHANGE",
"level": 6700,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"subject": "Example",
"description": "Example text.",
"changeType": "1"
}Listing Network Changes records
# All network changes in your tenant
GET /v1/entities/NWCHANGE/SUB