NWPLATCOMPDEP: Component Dependency
A dependency relationship between two software components within a platform type, tracking how components rely on each other.
Default definition. This article describes the default
NWPLATCOMPDEP 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 NWPLATCOMPDEP.Entity properties
| Property | Value |
|---|---|
| Entity code | NWPLATCOMPDEP |
| Display name | Component Dependency |
| Plural | Component Dependencies |
| Level | 6160 |
Use cases
Junction entity linking two NWPLATCOMP records to model dependencies between software components within a platform. Follows the same dual-comboKey pattern as NWPLATDEP: sourceComponent uses comboKey (position 1), targetComponent uses comboKey2 (position 2). This enables bidirectional related lists on NWPLATCOMP: 'Depends On' queries comboKey, 'Depended On By' queries comboKey2.
Fields
Dependency
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Description | |
sourceComponent | reference → NWPLATCOMP | Yes | Source component |
targetComponent | reference → NWPLATCOMP | Yes | Target component |
Classification
| Field | Type | Required | Notes |
|---|---|---|---|
dependencyType | enum | Yes | Dependency type Valid ids: runtime (Runtime), data (Data / Storage), api (API / Interface), messaging (Messaging / Event), auth (Authentication / Authorisation), config (Configuration / Discovery). |
criticality | enum | Criticality Valid ids: low (Low), medium (Medium), high (High), critical (Critical). | |
protocol | text | Protocol / interface | |
notes | text (multi-line) | Notes |
Relationships
- Lookups:
sourceComponentpoints at aNWPLATCOMPrecord.targetComponentpoints at aNWPLATCOMPrecord.
Creating a Component Dependency via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "NWPLATCOMPDEP",
"level": 6160,
"comboKey": "SUB:<your-sub-id>|ENT:",
"sourceComponent": "",
"targetComponent": "",
"dependencyType": "runtime"
} Listing Component Dependencies records
# All component dependencies in your tenant
GET /v1/entities/NWPLATCOMPDEP/SUB