DemandFlow Support Centre

CMDB: Configuration Item

Configuration Item (CI) representing a service, application, infrastructure component, or other managed element in the CMDB.

Default definition. This article describes the default CMDB 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 CMDB.

Entity properties

Property	Value
Entity code	`CMDB`
Display name	Configuration Item
Plural	Configuration Items
Level	51200

Use cases

CMDB represents Configuration Items broader than ITASSET (which focuses on end-user hardware). CIs can be services, applications, servers, databases, network devices, VMs, containers, or cloud resources. The Dependencies panel uses two relatedlists backed by the CMDBREL junction entity: Depends On (upstream, stockRecord on sourceCi) and Depended On By (downstream, stockRecord on targetCi). This avoids storing large dependency arrays in DynamoDB. Linked Assets shows ITASSET records via stockRecord on configItem.

Fields

General: CI Information

Field	Type	Required	Notes
`name`	text	Yes	CI Name.
`ciType`	enum	Yes	CI Type. Valid ids: `1` (Service), `2` (Application), `3` (Server), `4` (Database), `5` (Network Device), `6` (Storage), `7` (Virtual Machine), `8` (Container), `9` (Cloud Resource), `10` (Document), `11` (Other).
`status`	enum	Yes	Status. Valid ids: `1` (Active), `2` (Planned), `3` (Under Change), `4` (Retired), `5` (Decommissioned).
`description`	text (multi-line)		Description.

General: Classification

Field	Type	Notes
`tier`	enum	Tier. Valid ids: `1` (Tier 1 - Business Critical), `2` (Tier 2 - Important), `3` (Tier 3 - Standard), `4` (Tier 4 - Non-Critical).
`environment`	enum	Environment. Valid ids: `1` (Production), `2` (Staging), `3` (Development), `4` (Test), `5` (DR).
`location`	text	Location.
`version`	text	Version.

General: Ownership

Field	Type	Required	Notes
`owner`	reference → user	Yes	Owner.
`managedBy`	reference → user		Managed By.
`supportGroup`	text		Support Group.
`vendor`	reference → `VEN`		Vendor.
`department`	reference → `DEPT`		Department.
`service`	reference → `ITSVC`		Service.

Technical Details: Configuration

Field	Type	Notes
`hostname`	text	Hostname.
`ipAddress`	text	IP Address.
`operatingSystem`	text	Operating System.
`platform`	text	Platform.
`url`	text	URL.
`port`	text	Port.
`notes`	text (multi-line)	Technical Notes.

Technical Details: Capacity & Performance

Field	Type	Notes
`cpu`	text	CPU.
`memoryGB`	number	Memory (GB).
`storageGB`	number	Storage (GB).
`maxConnections`	number	Max Connections.
`monitoringTool`	text	Monitoring Tool.
`monitoringUrl`	text	Monitoring URL.

Relationships

Lookups: vendor points at a VEN record; department points at a DEPT record; service points at a ITSVC record.
Related lists: CMDBREL (via sourceCi), CMDBREL (via targetCi), ITASSET (via configItem), ITCHANGE (via configItem), TICKET (via configItem).
Activity: activity timeline panel attached.

Creating a Configuration Item via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "CMDB",
  "level":    51200,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "CI Name",
  "ciType": "1",
  "status": "1",
  "description": "Description"
}

Listing Configuration Items records

GET /v1/entities/CMDB/SUB

DemandFlow Support Centre

CMDB: Configuration Item

CMDB: Configuration Item

Entity properties

Use cases

Fields

Relationships

Creating a Configuration Item via the API

Listing Configuration Items records

See also

Was this article helpful?