NWPLATHWVER: Hardware Version
A specific version or generation of an abstract hardware type, with lifecycle dates and status tracking.
Default definition. This article describes the default
NWPLATHWVER 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 NWPLATHWVER.Entity properties
| Property | Value |
|---|---|
| Entity code | NWPLATHWVER |
| Display name | Hardware Version |
| Plural | Hardware Versions |
| Level | 6180 |
Use cases
Child entity of NWPLATHW for tracking versions/generations of a hardware type (e. g. Gen 10, Gen 11 of an HPE ProLiant, or v1.
Fields
Version Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name |
version | text | Version / generation label | |
specs | text (multi-line) | Key specifications | |
notes | text (multi-line) | Notes |
Lifecycle Dates
| Field | Type | Required | Notes |
|---|---|---|---|
releaseDate | date | Release date | |
endOfSaleDate | date | End of sale | |
endOfSupportDate | date | End of support | |
endOfLifeDate | date | End of life | |
status | enum | Yes | Status Valid ids: planned (Planned), current (Current), supported (Supported (not current)), endsale (End of Sale), endsupport (End of Support), eol (End of Life), retired (Retired). |
Relationships
- Related lists:
NWPLATHWREQ(formatSUB|NWPLATHWVER).
Creating a Hardware Version via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "NWPLATHWVER",
"level": 6180,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"status": "planned",
"version": "Example",
"specs": "Example text."
}Listing Hardware Versions records
# All hardware versions in your tenant
GET /v1/entities/NWPLATHWVER/SUB