PJDEP: Project Dependency
The PJDEP entity represents a directional dependency relationship between two projects, capturing scheduling and delivery dependencies with criticality and lag time.
PJDEP 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 PJDEP.Entity properties
| Property | Value |
|---|---|
| Entity code | PJDEP |
| Display name | Project Dependency |
| Plural | Project Dependencies |
| Level | 425 |
Use cases
PJDEP is a junction entity linking two PJ records in a directional relationship. The sourceProject is the project that has the dependency (the one that must wait), and targetProject is the project being depended on (the one that must complete first). For example, if 'Meter Installation' depends on 'Network Telemetry', sourceProject=Meter Installation and targetProject=Network Telemetry. The dual comboKey pattern stores sourceProject in comboKey (position 1) and targetProject in comboKey2 (position 2). On PJ, the 'Depends On' relatedlist queries the comboKey property and the 'Depended On By' relatedlist queries the comboKey2 property, both using format SUB|PJ.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Short description e.g. 'Meter Install depends on Network Telemetry'. |
sourceProject | reference → PJ | Yes | The project that has the dependency (must wait). |
targetProject | reference → PJ | Yes | The project being depended on (must complete first). |
relationshipType | enum | Yes | Relationship Type. Valid ids: finish-to-start (Finish to Start), start-to-start (Start to Start), finish-to-finish (Finish to Finish), delivers-input (Delivers Input), shared-resource (Shared Resource). |
criticality | enum | Yes | How critical is this dependency? Critical = project cannot proceed at all without the target completing. Valid ids: low (Low), medium (Medium), high (High), critical (Critical). |
lagDays | number | Number of days lag between the dependency link (0 = immediate). | |
status | enum | Status. Valid ids: active (Active), resolved (Resolved), blocked (Blocked). | |
description | text (multi-line) | Describe the nature of this dependency. | |
mitigations | text (multi-line) | Fallback or workaround if the dependency is delayed. |
Relationships
- Lookups:
sourceProjectpoints atPJrecord;targetProjectpoints atPJrecord.
Creating a Project Dependency via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "PJDEP",
"level": 425,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"sourceProject": "",
"targetProject": "",
"relationshipType": "finish-to-start"
} Listing PJDEP records
# All project dependencies in your tenant
GET /v1/entities/PJDEP/SUB