PTASK: Project Task
The PTASK entity represents a waterfall-style project task with scheduling, dependencies, resource tracking, and critical path analysis.
PTASK 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 PTASK.Entity properties
| Property | Value |
|---|---|
| Entity code | PTASK |
| Display name | Project Task |
| Plural | Project Tasks |
| Level | 15000 |
Use cases
PTASK is the traditional/waterfall task entity used for detailed project scheduling. It links to a project (PJ) via objectLookup and supports a work breakdown structure through the parentTask self-reference. Task types (Task, Milestone, Summary Task, Phase) enable WBS hierarchy. Scheduling fields include planned/actual start and end dates, duration, and constraint types (ASAP, ALAP, Must Start On, etc.) following project management standards. Critical path analysis fields (earlyStart, earlyFinish, lateStart, lateFinish, totalFloat) support CPM scheduling. Dependencies are managed via TASKDEPENDENCY related entities for both predecessors and successors. The entity includes resource allocation (TASKASSIGNMENT), time tracking (TIMEENTRY), cost tracking (estimated vs actual), and risk/quality management. This is the more comprehensive task entity compared to WTASK, which is a streamlined alternative for workflow-based task management.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Task Name. |
project | reference → PJ | Project. | |
progress | slider | Progress (%). | |
status | enum | Yes | Status. Valid ids: 0 (New), 1 (In Progress), 2 (Done), 3 (Blocked), 4 (Cancelled). |
user | reference → user | Yes | Assigned To. |
parentTask | reference → PTASK | For subtasks or work breakdown structure. | |
taskType | enum | Task Type. Valid ids: 1 (Task), 2 (Milestone), 3 (Summary Task), 4 (Phase). | |
priority | enum | Priority. Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low). | |
description | text (multi-line) | Description. | |
date1 | date | Yes | Planned Start Date. |
date2 | date | Yes | Planned End Date. |
actualStartDate | date | Actual Start Date. | |
actualEndDate | date | Actual End Date. | |
duration | number | Planned duration in working days. | |
actualDuration | number | Actual Duration (days). Read-only. | |
constraintType | enum | Constraint Type. 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. | |
assignedUser | reference → USER | Assigned User. | |
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. | |
status | enum | Yes | Status. Valid ids: 1 (New), 2 (In Progress), 3 (On Hold), 4 (Completed), 5 (Cancelled), 6 (Deferred). |
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. |
Team & Communication
| Field | Type | Required | Notes |
|---|---|---|---|
stakeholders | array of references → PPL | People to notify of task updates. | |
communicationPlan | text (multi-line) | Communication Plan. | |
escalationPath | reference → PPL | Escalation Path. |
Risk & Quality
| Field | Type | Required | Notes |
|---|---|---|---|
riskLevel | enum | Risk Level. Valid ids: 1 (Low), 2 (Medium), 3 (High), 4 (Critical). | |
riskImpact | enum | Risk Impact. 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. | |
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. | |
specificationUrl | text (URL) | Link to technical specifications. | |
designUrl | text (URL) | Link to design documents. | |
testPlanUrl | text (URL) | Link to test plan documents. | |
codeRepositoryUrl | text (URL) | Link to source code repository. | |
issueTrackerUrl | text (URL) | Link to issue tracking system. |
Additional panels
- log panel.
Relationships
- Lookups:
projectpoints atPJrecord;parentTaskpoints atPTASKrecord;assignedUserpoints atUSERrecord;taskOwnerpoints atPPLrecord;stakeholderspoints at an array ofPPLrecords;escalationPathpoints atPPLrecord;reviewerpoints atPPLrecord;approverpoints atPPLrecord. - Related lists:
TASKDEPENDENCYvia formatSUB;TASKDEPENDENCYvia formatSUB;TASKASSIGNMENTvia formatSUB;TIMEENTRYvia formatSUB.
Creating a Project Task via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "PTASK",
"level": 15000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"status": 0,
"user": "",
"date1": "2026-01-01"
} Listing PTASK records
# All project tasks in your tenant
GET /v1/entities/PTASK/SUB