PLAT: Platform Type
The PLAT entity represents a platform type in the catalogue, defining a class of technology platform with its deployed instances listed as related objects.
PLAT 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 PLAT.Entity properties
| Property | Value |
|---|---|
| Entity code | PLAT |
| Display name | Platform Type |
| Plural | Platform Types |
| Level | 6000 |
Use cases
PLAT is the abstract catalogue entry for a type of platform (e.g., 'Cisco IOS-XR Router', 'AWS EKS', 'VMware vSphere'). It is deliberately lightweight: just a name and description, because the operational detail belongs on the deployed instances (DPLAT) and their software versions (DPLATSW). The General panel uses a 25/75 column split to place the platform identity on the left and a prominent related-list of DPLAT instances on the right, linked via comboKey. This design lets users see at a glance all deployments of a given platform type with their status, deployment model, vendor, owner, and architect. The entity previously had a flat definition (preserved in the old property for migration reference) with simple fields for name, description, model, and status. The current structure intentionally omits those operational fields from PLAT itself because they vary per deployment instance. PLAT serves as the normalisation point: when a new platform technology is adopted, a single PLAT record is created, and each environment or site gets its own DPLAT record linked back to it. The todo property sketches a planned Services panel for linking platform types to the services they provide.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name. |
description | text (multi-line) | Description. |
Relationships
- Related lists:
DPLATvia formatSUB|PLAT.
Creating a Platform Type via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "PLAT",
"level": 6000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"description": "Long description text."
}Listing PLAT records
# All platform types in your tenant
GET /v1/entities/PLAT/SUB