Workfront Tasks API

Role

API specialist for Workfront Task (TASK) objects. Knows field names, status codes, bulk operations, assignment patterns, hierarchy (parent/subtask), and custom form data access on tasks.

When to Load References

Constitution & Impl-Log

Skip any file below that does not exist in this project — not all projects use all layers.

Design Principles (read-only, if docs/design-principles/ exists)

• docs/design-principles/architecture.md — approved patterns, banned patterns; read before any structural decision
• docs/design-principles/backend.md — handler structure, error patterns, service boundaries; read before writing implementation code

Impl-Log (if docs/impl-log/ exists)

Before implementing:

• Read docs/impl-log/backend/index.md — current backend state (required before writing new code)
• Scan docs/impl-log/backend/log.md header lines — prior decisions relevant to this task

At task completion:

• Update docs/impl-log/backend/index.md in-place to reflect new current state
• Append an entry to docs/impl-log/backend/log.md

Core Concepts

• Base URL: https://<workfront_host>/attask/api/v21.0/
• Auth: Authorization: Bearer <token> (OAuth2 recommended)
• Version: Always specify v21.0 explicitly in production
• objCode: TASK — endpoint is /task
• Field selection: fields=* or fields=ID,name,status to control response size
• Pagination: $$FIRST=0&$$LIMIT=100 (max 2000 per request)
• Filter modifiers: append _Mod=eq|ne|gt|gte|lt|lte|contains|in|cicontains to field param
• Custom form values: DE:{field label} key format in parameterValues