WORKFLOWTRANSITION: Workflow Transition
A valid status-to-status transition within a workflow, defining which moves are permitted and what the action button should be labelled.
Default definition. This article describes the default
WORKFLOWTRANSITION 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 WORKFLOWTRANSITION.Entity properties
| Property | Value |
|---|---|
| Entity code | WORKFLOWTRANSITION |
| Display name | Workflow Transition |
| Plural | Workflow Transitions |
| Level | 11120 |
Use cases
A valid status-to-status transition within a workflow, defining which moves are permitted and what the action button should be labelled.
Child of WORKFLOW, stored in the transitions objectarray. Each row defines an allowed move from one statusId to another. The name field provides an optional action label (e.g. 'Start Work', 'Send to Review') shown on buttons or context menus. When a WORKFLOW has enforceTransitions enabled, only transitions defined here are permitted.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Action label shown on buttons (e.g. Start Work, Send to Review) |
fromStatusId | reference → WORKFLOWSTATUS | Yes | From Status. |
toStatusId | reference → WORKFLOWSTATUS | Yes | To Status. |
Relationships
- Lookups:
fromStatusIdpoints at aWORKFLOWSTATUSrecord;toStatusIdpoints at aWORKFLOWSTATUSrecord.
Creating a Workflow Transition via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "WORKFLOWTRANSITION",
"level": 11120,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"fromStatusId": "",
"toStatusId": ""
} Listing Workflow Transitions
GET /v1/entities/WORKFLOWTRANSITION/SUB