DemandFlow Support Centre

NWPROBLEM: Network Problem

ReferenceEntity Reference16/04/2026Updated 16/04/2026
Network problem management record for tracking root causes of recurring faults on telecom platform instances, workarounds, and known errors to prevent future outages.

NWPROBLEM: Network Problem

Network problem management record for tracking root causes of recurring faults on telecom platform instances, workarounds, and known errors to prevent future outages.

Default definition. This article describes the default NWPROBLEM 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 NWPROBLEM.

Entity properties

PropertyValue
Entity codeNWPROBLEM
Display nameNetwork Problem
PluralNetwork Problems
Level6800

Use cases

NWPROBLEM is the network operations equivalent of ITPROBLEM (IT problem management). The workflow is New → Investigating → Root Cause Identified → Known Error → Resolved → Closed. The Mark as Known Error toolbar button sets the status and knownError flag, confirming the problem is documented with a workaround.

Fields

Problem Information

FieldTypeRequiredNotes
nametextYesProblem ID
subjecttextYesSubject
descriptiontext (multi-line)YesDescription
statusenumYesStatus Valid ids: 1 (New), 2 (Investigating), 3 (Root Cause Identified), 4 (Known Error), 5 (Resolved), 6 (Closed).
priorityenumYesPriority Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low).

Classification

FieldTypeRequiredNotes
categoryenumCategory Valid ids: 1 (Radio/RF), 2 (Transport), 3 (Core Network), 4 (IP/MPLS), 5 (Optical), 6 (Access Network), 7 (Power/Environmental), 8 (Security), 9 (Other).
impactenumImpact Valid ids: 1 (Network-wide), 2 (Regional), 3 (Single Site), 4 (Single Element).
servicereference → NWSVCAffected Network Service

Assignment

FieldTypeRequiredNotes
assignedToreference → userAssigned To
assignedGrouptextAssigned Group
reportedByreference → userReported By
reportedDatedatetimeReported Date

Root Cause

FieldTypeRequiredNotes
rootCausetext (multi-line)Root Cause
rootCauseCategoryenumRoot Cause Category Valid ids: 1 (Hardware Failure), 2 (Software Bug), 3 (Configuration Error), 4 (RF Interference), 5 (Fiber/Cable Fault), 6 (Power Failure), 7 (Capacity Exceeded), 8 (Environmental), 9 (Design Flaw), 10 (External Factor), 11 (Unknown).
identifiedDatedatetimeIdentified Date

Workaround

FieldTypeRequiredNotes
workaroundtext (multi-line)Workaround
workaroundAvailableenumWorkaround Available Valid ids: 1 (Yes), 0 (No).
workaroundEffectivenessenumEffectiveness Valid ids: 1 (High), 2 (Medium), 3 (Low), 4 (None).

Resolution Details

FieldTypeRequiredNotes
resolutionSummarytext (multi-line)Resolution Summary
resolutionDatedatetimeResolution Date
knownErrorenumKnown Error Valid ids: 1 (Yes), 0 (No).
knownErrorIdtextKnown Error ID

Related

FieldTypeRequiredNotes
relatedChangereference → NWCHANGERelated Change Request
platformInstancereference → NWPLATINSTAffected Platform
sitereference → SITESite
affectedAssetsarray of references → COMPINVAffected Assets

Activity. Activity timeline panel attached.

Relationships

  • Lookups: service points at a NWSVC record. relatedChange points at a NWCHANGE record. platformInstance points at a NWPLATINST record. site points at a SITE record. affectedAssets points at a COMPINV record.
  • Related lists: NWTICKET.

Creating a Network Problem via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "NWPROBLEM",
  "level":    6800,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "subject": "Example",
  "description": "Example text.",
  "status": "1"
}

Listing Network Problems records

# All network problems in your tenant
GET /v1/entities/NWPROBLEM/SUB

See also

nwproblemnetworkproblemproblemsnwproblemsentity reference

Was this article helpful?

← Back to Knowledge Base