DPLATSW: Platform Software
A software release or version for a deployed platform, tracking its lifecycle dates, testing status, and deployment details.
DPLATSW 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 DPLATSW.Entity properties
| Property | Value |
|---|---|
| Entity code | DPLATSW |
| Display name | Platform Software |
| Plural | Platform Software |
| Level | 6000 |
Use cases
DPLATSW captures the software release lifecycle for platforms tracked in DPLAT. Each record represents a specific version (e.g., v3.1.0) of a platform with its release ID, type (Major, Minor, Patch, Hotfix), and colour-coded status (New, Testing, Planned, In Progress, Active, Delayed, Rolled back, Retired). The DPLAT objectLookup with comboKey ties the release to its parent platform. Lifecycle dates (GA, EOL, EOS, end-of-support) drive upgrade planning and compliance reporting, and the swTimeline flag on key fields enables timeline visualisation. Pre-requisites uses a multi-objectLookup to other DPLATSW records, modelling version dependency chains. The Release panel is deliberately comprehensive: it covers planning (planned/actual dates, rollback availability/plan), change impact (features, fixes, security patches, impacted services, risk level, approval status), testing (status, coverage %, UAT, sign-off, performance benchmarks), compliance (regulatory checks, audit references, incident reports), deployment details (release notes, scripts, config changes, dependencies), and post-deployment monitoring (status, feedback score, issues). The Pre-requisites panel uses a custom dplatswprereq row type for visual dependency mapping. This depth exists because software releases on network/infrastructure platforms carry significant operational risk and require formal change management.
Fields
Basics
| Field | Type | Required | Notes |
|---|---|---|---|
ref | text | Ref. Read only. | |
name | text | Yes | Release name. Example: (e.g., Network Platform v3.1 Upgrade). |
relid | text | Yes | Release ID. Example: (e.g., REL-2025-001). |
version | text | Yes | Release version. Example: (e.g., v3.1.0). |
type | singleselect | Release type. | |
status | enum | Valid ids: New (New), Testing (Testing), Planned (Planned), In Progress (In Progress), Active (Active), Delayed (Delayed), Rolled back (Rolled back), Retired (Retired). | |
DPLAT | reference → DPLAT | Yes | Platform. |
Description
| Field | Type | Required | Notes |
|---|---|---|---|
description | text (multi-line) | Description. Example: (Summary of the release purpose and impact). |
Lifecycle
| Field | Type | Required | Notes |
|---|---|---|---|
datega | date | General availability date. | |
dateeol | date | End-of-life date. | |
dateeos | date | End-of-service date. | |
dateeosup | date | End-of-supprt date. |
Pre-requisites
| Field | Type | Required | Notes |
|---|---|---|---|
prereqs | array of references → DPLATSW | Pre-requisites. |
Plan
| Field | Type | Required | Notes |
|---|---|---|---|
dateplan | date | Planned release date. | |
dateactual | date | Actual release date. | |
rbackavail | singleselect | Rollback Available. | |
rbackplan | text (URL) | Rollback plan. Example: (Link to rollback documentation). |
Change & impact details
| Field | Type | Required | Notes |
|---|---|---|---|
changeFeatures | text (multi-line) | New features & enhancements. Example: (List of key updates). | |
changeFixes | text (multi-line) | Bug fixes. Example: (List of resolved issues with references). | |
changePatches | text (multi-line) | Security patches. Example: (Any security vulnerabilities addressed). | |
changeServices | text (multi-line) | Impacted services. Example: (Which services may be affected, e.g., VoLTE, 5G core). | |
risk | singleselect | Risk level. | |
approvalstatus | singleselect | Approval status. |
Testing & validation
| Field | Type | Required | Notes |
|---|---|---|---|
teststatus | singleselect | Testing status. | |
testcases | number | Test cases passed (%). Example: (Coverage). | |
testuat | singleselect | UAT completed. | |
testsignoff | text | Test sign-off. Example: (Person or team who approved the release for production). | |
testbenchmarks | text (multi-line) | Performance metrics. Example: (Before & After performance metrics, if applicable). |
Compliance & audit details
| Field | Type | Required | Notes |
|---|---|---|---|
regcompliance | singleselect | Regulatory compliance check. | |
regaudit | text | Audit log reference. Example: (Link to audit records). | |
regincident | text (multi-line) | Incident reports. Example: (Any incidents related to the release, linked to tickets in your tracking system). |
Deployment details
| Field | Type | Required | Notes |
|---|---|---|---|
deprel | text | Release Notes URL. Example: (Link to documentation). | |
depurl | text | Deployment script location. Example: (Path to automation scripts). | |
regconfig | text (multi-line) | Configuration changes. Example: (Details of any network config changes). | |
regpost | text (multi-line) | Dependencies. Example: (List of software/hardware this release depends on). |
Deployment artifacts & documentation
| Field | Type | Required | Notes |
|---|---|---|---|
poststatus | singleselect | Monitoring status. | |
postrating | rating | Feedback score. | |
postissues | text (multi-line) | Post-deployment issues. Example: (Any issues reported after release). |
Relationships
- Lookup:
DPLAT(reference →DPLAT). - Lookup:
prereqs(array of references →DPLATSW).
Creating a Platform Software via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "DPLATSW",
"level": 6000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"relid": "Example value",
"version": "Example value",
"DPLAT": ""
} Listing Platform Software records
GET /v1/entities/DPLATSW/SUB:<your-sub-id>