NWPLATCOMP: Platform Component
A component that forms part of a network platform type - either software (e.g. AMF, Kubernetes, VMware) or hardware (e.g. server racks, storage arrays, network switches).
Default definition. This article describes the default
NWPLATCOMP 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 NWPLATCOMP.Entity properties
| Property | Value |
|---|---|
| Entity code | NWPLATCOMP |
| Display name | Platform Component |
| Plural | Platform Components |
| Level | 6150 |
Use cases
Child entity of NWPLAT for defining the full composition of a platform type. Components can be software or hardware - a Network Cloud platform might include server racks (hardware), VMware/Kubernetes (software), and storage arrays (hardware). The componentClass field separates Software vs Hardware vs Infrastructure.
Fields
Component Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Component name |
componentClass | enum | Yes | Class Valid ids: software (Software), hardware (Hardware), infrastructure (Infrastructure). |
componentType | enum | Yes | Type Valid ids: application (Application), middleware (Middleware), database (Database), platform (Platform / Orchestration), integration (Integration / API), security (Security), monitoring (Monitoring / Observability), messaging (Messaging / Queue), compute (Compute / Server), storage (Storage), networking (Networking), appliance (Appliance), power (Power / Cooling), other (Other). |
vendor | reference → VEN | Vendor | |
description | text (multi-line) | Description |
Lifecycle & Classification
| Field | Type | Required | Notes |
|---|---|---|---|
status | enum | Yes | Status Valid ids: planned (Planned), active (Active), deprecated (Deprecated), retired (Retired). |
criticality | enum | Criticality Valid ids: low (Low), medium (Medium), high (High), critical (Critical). | |
currentVersion | text | Current version | |
licenceType | enum | Licence type Valid ids: commercial (Commercial), opensource (Open Source), internal (Internal / Proprietary), saas (SaaS / Subscription). | |
notes | text (multi-line) | Notes |
Activity. Activity timeline panel attached.
Relationships
- Lookups:
vendorpoints at aVENrecord. - Related lists:
NWPLATCOMPDEP(formatSUB|NWPLATCOMP),NWPLATCOMPDEP(formatSUB|NWPLATCOMP),NWPLATHWREQ(formatSUB|NWPLATCOMP).
Creating a Platform Component via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "NWPLATCOMP",
"level": 6150,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"componentClass": "software",
"componentType": "application",
"status": "planned"
}Listing Platform Components records
# All platform components in your tenant
GET /v1/entities/NWPLATCOMP/SUB