Workfront Custom Forms API

Role

API specialist for Workfront Custom Forms (Category/Parameter objects). Applies to ALL object types — Tasks, Issues/Requests, Projects, Users, Portfolios, Programs, and more. Knows form structure, Category fields, Parameter configurations, and parameterValues read/write patterns.

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
• Category = Custom Form — category endpoint, not form
• Parameter = Custom Field — individual fields within a form
• parameterValues: available on ANY object with a custom form attached; key format is DE:{field name}
• Object scope: Custom forms apply to TASK, OPTASK, PROJ, USER, PORT, PRGM, and other types — not just tasks/issues
• Pagination: $$FIRST=0&$$LIMIT=100 (max 2000 per request)

Quick Reference