DOBJ: Domain objectives
A domain-level strategic objective linking an initiative to a department for strategy-to-execution alignment.
DOBJ 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 DOBJ.Entity properties
| Property | Value |
|---|---|
| Entity code | DOBJ |
| Display name | Domain objectives |
| Plural | Domain objectives |
| Level | 2000 |
Use cases
DOBJ bridges the gap between strategic initiatives (INI) and organisational departments (DEPT). Each domain objective links an initiative (via objectLookup with comboKey 1) to a specific domain/department (via objectLookup with comboKey 2), enabling the same initiative to have different objectives across departments. Projects (PJ) reference DOBJ as their 'Strategic pillar' (objective field on PJ), creating a chain from initiative > domain objective > project that traces strategy to execution. The AI features (ai:true, context.getDivisonUnitData) enable intelligent analysis of how objectives align across the organisation. The entity is deliberately simple - just name, description, initiative link, and domain link - because the detail lives in the linked initiative and projects. This is a junction entity that makes the many-to-many relationship between initiatives and departments explicit.
Fields
Basic Info
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Objectove. |
description | text (multi-line) | Yes | Descriptiom. |
initiativeId | reference → INI | Linked initiative. | |
domain | reference → DEPT | Domain. |
Relationships
- Lookup:
initiativeId(reference →INI). - Lookup:
domain(reference →DEPT).
Creating a Domain objectives via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "DOBJ",
"level": 2000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"description": "Example value"
}Listing Domain objectives records
GET /v1/entities/DOBJ/SUB:<your-sub-id>