SUBCOMPTYPE: Subcomponent type
Classification type for subcomponents, providing a taxonomy to categorise subcomponent catalogue entries.
SUBCOMPTYPE 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 SUBCOMPTYPE.Entity properties
| Property | Value |
|---|---|
| Entity code | SUBCOMPTYPE |
| Display name | Subcomponent type |
| Plural | Subcomponent types |
| Level | 100000 |
Use cases
Classification type for subcomponents, providing a taxonomy to categorise subcomponent catalogue entries.
SUBCOMPTYPE is a simple lookup/reference entity that provides a controlled vocabulary for classifying SUBCOMP records via their 'class' field. It mirrors COMPTYPE but exists separately because subcomponents have a fundamentally different classification need - they represent internal parts (CPUs, memory modules, line cards, power supplies) rather than top-level equipment. Separating the type entities means organisations can maintain distinct taxonomies for components vs subcomponents without ambiguity. The minimal structure (name + description) is standard for a lookup entity.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name. |
description | text (multi-line) | Description. |
Relationships
No declared relationships in the default definition.
Creating a Subcomponent type via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SUBCOMPTYPE",
"level": 100000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"description": "Example text"
}Listing Subcomponent types
GET /v1/entities/SUBCOMPTYPE/SUB