WTASK: Project Task
A streamlined project task for workflow-based delivery with scheduling, resources, and contractual milestones.
WTASK 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 WTASK.Entity properties
| Property | Value |
|---|---|
| Entity code | WTASK |
| Display name | Project Task |
| Plural | Project Tasks |
| Level | 15000 |
Use cases
A streamlined project task for workflow-based delivery with scheduling, resources, and contractual milestones.
WTASK is an alternative task entity to PTASK, designed for workflow-based project delivery rather than traditional waterfall scheduling. It omits the explicit project objectLookup (tasks are associated via context), and the parentTask self-reference points to WTASK rather than PTASK, creating a separate WBS hierarchy. Key differences from PTASK: it includes a contractual milestones panel (SDEL related list) for linking tasks to supplier deliverables, and it drops the time tracking and formal dependency panels. The task types, priorities, scheduling fields, constraint types, and critical path analysis fields mirror PTASK. The filter ['PJ'] on parentTask restricts lookup to tasks within the same project context. This entity suits organisations using automated workflows where task creation and progression are driven by workflow rules rather than manual Gantt chart management.
Fields
Basic Information
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Task Name. |
progress | number | Progress (%). | |
status | enum | Yes | Valid ids: 1 (New), 2 (In Progress), 3 (Done), 4 (Blocked), 5 (Cancelled). |
parentTask | reference → WTASK | For subtasks or work breakdown structure | |
taskType | enum | Valid ids: 1 (Task), 2 (Milestone), 3 (Summary Task), 4 (Phase). | |
priority | enum | Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low). | |
description | text (multi-line) | Description. |
Schedule
| Field | Type | Required | Notes |
|---|---|---|---|
date1 | date | Yes | Planned Start Date. |
date2 | date | Yes | Planned End Date. |
actualStartDate | date | Actual Start Date. | |
actualEndDate | date | Actual End Date. | |
duration | number | Auto-calculated from start and end dates Read only. | |
actualDuration | number | Actual Duration (days). Read only. | |
constraintType | enum | Valid ids: 1 (As Soon As Possible), 2 (As Late As Possible), 3 (Must Start On), 4 (Must Finish On), 5 (Start No Earlier Than), 6 (Start No Later Than), 7 (Finish No Earlier Than), 8 (Finish No Later Than). | |
constraintDate | date | Constraint Date. |
Assignment & Resources
| Field | Type | Required | Notes |
|---|---|---|---|
user | reference → STF | Yes | Assigned To. |
workload | number | Yes | Effort (%). |
taskOwner | reference → PPL | Accountable person for task completion | |
workHours | number | Estimated Work Hours. | |
actualWorkHours | number | Actual Work Hours. | |
estimatedCost | number | Estimated Cost. | |
actualCost | number | Actual Cost. | |
resourceRequirements | text (multi-line) | Resource Requirements. |
Tracking
| Field | Type | Required | Notes |
|---|---|---|---|
criticalPath | boolean | Task is on the project's critical path | |
milestone | boolean | Mark as project milestone | |
earlyStart | date | Calculated early start date Read only. | |
earlyFinish | date | Calculated early finish date Read only. | |
lateStart | date | Calculated late start date Read only. | |
lateFinish | date | Calculated late finish date Read only. | |
totalFloat | number | Total float/slack time Read only. |
Deliverables & Stakeholders
| Field | Type | Required | Notes |
|---|---|---|---|
communicationPlan | text (multi-line) | Communication Plan. | |
escalationPath | reference → PPL | Escalation Path. |
Risk Management
| Field | Type | Required | Notes |
|---|---|---|---|
riskLevel | enum | Valid ids: 1 (Low), 2 (Medium), 3 (High), 4 (Critical). | |
riskImpact | enum | Valid ids: 1 (Negligible), 2 (Minor), 3 (Moderate), 4 (Major), 5 (Severe). | |
riskDescription | text (multi-line) | Risk Description. | |
mitigationPlan | text (multi-line) | Mitigation Plan. | |
contingencyPlan | text (multi-line) | Contingency Plan. |
Quality & Deliverables
| Field | Type | Required | Notes |
|---|---|---|---|
deliverables | text (multi-line) | Expected Deliverables. | |
acceptanceCriteria | text (multi-line) | Acceptance Criteria. | |
qualityStandards | text (multi-line) | Quality Standards. | |
reviewRequired | boolean | Review Required. | |
approvalRequired | boolean | Approval Required. | |
reviewer | reference → PPL | Reviewer. | |
approver | reference → PPL | Approver. |
Documents & Links
| Field | Type | Required | Notes |
|---|---|---|---|
documentationUrl | text (URL) | Link to task documentation URL string. | |
specificationUrl | text (URL) | Link to technical specifications URL string. | |
designUrl | text (URL) | Link to design documents URL string. | |
testPlanUrl | text (URL) | Link to test plan documents URL string. | |
codeRepositoryUrl | text (URL) | Link to source code repository URL string. | |
issueTrackerUrl | text (URL) | Link to issue tracking system URL string. |
Attachments and additional panels
- Activity log panel attached.
Relationships
- Lookups:
parentTaskpoints at aWTASKrecord;userpoints at aSTFrecord;taskOwnerpoints at aPPLrecord;escalationPathpoints at aPPLrecord;reviewerpoints at aPPLrecord;approverpoints at aPPLrecord. - Related lists:
SDELvia link.
Creating a Project Task via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "WTASK",
"level": 15000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"status": 1,
"date1": "2026-01-01",
"date2": "2026-01-01"
}Listing Project Tasks
GET /v1/entities/WTASK/SUB