Adobe Workfront Core Developer Professional cheat sheet

Access levels and object sharing are separate gates: a user needs the access-level capability and the object permission (View, Contribute, or Manage) before an action is allowed.

Custom statuses are created per object type and must be equated to a default status category (Current, Complete, Dead); system default statuses cannot be deleted.

Layout templates define global navigation, tabs, landing page, and custom-field visibility; they are assigned to users, groups, teams, or job roles.

Project preferences set system or group defaults for status, schedule mode, duration type, and assignment editing; group-level preferences override system defaults for that group.

Groups and subgroups are the administrative hierarchy: group admins manage members, statuses, approval processes, layout templates, and project preferences for their scope.

A request queue requires queue details enabled on a project, at least one queue topic, and ordered routing rules; the first matching rule assigns the issue.

Milestone paths attach milestones to projects or tasks; milestone reports use the Milestone object and compare planned and actual milestone dates.

Exchange rates are configured under project preferences; multi-currency reports convert values using the stored rate for each currency.

Kick-Starts import and export supported Workfront objects through Excel; they handle configuration objects and are not a transactional integration API.

Custom forms are object-specific; supported objects include project, task, issue, portfolio, program, user, company, and group. Multiple forms can attach to one object.

Field types include text, paragraph, dropdown, multi-select, checkbox, radio, date, number, currency, calculated, reference, typeahead, image, rich text, section break, and descriptive text.

Calculated fields use Workfront expression syntax such as IF, CONCAT, DATEDIFF, ROUND, and PROD; they reference other fields on the same object and cannot pull unrelated object data.

Display logic shows or hides fields and sections based on values selected earlier in the same form; it is configured on the field or section break.

Section breaks create collapsible groups of fields; descriptive text provides instructions and can be conditional.

A custom field is referenced in text mode and the API as DE:Field Label, matching the field label shown on the form.

Reference fields link to another Workfront object; typeahead fields search as the user types and store the selected value in the field.

A custom field's type cannot be changed after it is saved with data; create a replacement field and migrate values.

Custom form sharing controls who can attach or edit the form; object access and field-level visibility also affect what a user sees.

Text mode exposes filter, view, group, chart, and aggregate sections; calculated columns use valueexpression and valueformat (currency, percent, date, HTML).

Wildcards resolve at run time: $$USER.ID, $$USER.homeGroupID, $$USER.companyID, $$USER.roleID, $$TODAY, and $$NOW; date modifiers include b, e, +Nd, -Nm, and +Nw.

In text-mode filters, AND narrows results and OR expands them; parentheses control precedence when combining conditions.

Groupings define chart categories and matrix axes; a chart needs at least one grouping, and a matrix report needs both a row grouping and a column grouping.

Report prompts can be required or optional, single- or multi-select, and can carry default values; prompts appear at run time before the report executes.

Scheduled deliveries can send PDF, Excel, or TSV to users, groups, teams, or roles; the report's run-as access setting determines which rows recipients see.

A dashboard supports one-, two-, or three-column layouts and up to 25 reports; report sharing and dashboard sharing both gate visibility.

A report set to run with another user's access rights returns rows based on that user's permissions, which can expose data the viewer cannot otherwise see.

Custom field columns in views use DE:Field Label; calculated expressions belong in valueexpression, not as literal text in the column name.

Approval processes attach to projects, tasks, issues, documents, and proofs; stages run in order and each stage can have one or more approvers plus a deadline.

Approval decisions include Approve and Reject, and some approval types also offer Changes Requested, which returns the object for revision instead of ending the process.

Approvers can delegate approval authority for a date range; the delegate must still have access to the object to act.

Request queue routing rules are ordered; the first matching rule assigns the issue to a user, job role, team, or project, and a default rule handles unmatched submissions.

Task predecessors use FS, SS, FF, or SF relationships plus lag; the relationship and lag determine the successor's earliest planned start.

Duration types are Simple, Calculated Assignment, Calculated Work, and Effort Driven; each determines whether duration, work, or assignment count drives scheduling.

Reminder notifications attach to approval processes and workflows; they fire before or after a deadline and can repeat at a defined interval.

Proof workflow stages assign Approver, Reviewer, or Viewer roles; only Approver decisions affect the proof's overall approval status.

Native automation includes approvals, routing rules, reminders, display logic, and calculated fields; Fusion or Kick-Start handles cross-system and bulk automation.

Workfront REST endpoints use https://.myworkfront.com/attask/api/v/ plus an object name, such as project, task, issue, user, or customform.

API authentication supports API keys, session IDs, and OAuth2; OAuth2 is the standard for multi-user integrations, while API keys suit server-to-server scripts.

HTTP methods map to CRUD: GET reads, POST creates, PUT updates, and DELETE removes; fields= limits attributes, filters= constrains rows, and limit/offset pages results.

Custom field values use DE:Field Label in API fields and payloads, for example fields=DE:Cost Center.

Workfront Fusion scenarios chain modules, run on schedules or webhooks, and use break, ignore, or resume error handlers to control failed operations.

Event subscriptions send create, update, or delete payloads to a receiver URL; filters reduce events, and the receiver must return a 2xx response to acknowledge.

The API Explorer in Setup lists objects, fields, and actions; it is the reference for endpoint names, parameter casing, and available values.

External document integrations such as Google Drive, SharePoint, OneDrive, Box, and Dropbox link files; file access remains governed by the external provider.

API writes enforce object security and required fields but can bypass some UI-only validation.

License types Plan, Work, Review, and Request set maximum capability; the access level then defines which objects, actions, and settings the user can use.

Object permissions are View, Contribute, and Manage; Manage adds delete and share, while Contribute adds add and edit but not delete or share.

Permissions inherit from parent objects such as project to task or issue; inherited and direct permissions combine, and the highest permission applies.

Groups and subgroups form the administrative hierarchy; a user's home group drives default sharing, group statuses, and group-level preferences.

Group admins manage membership, layout templates, approval processes, custom statuses, and project preferences for their group without full system admin rights.

Layout templates can be assigned to users, groups, teams, and job roles; assignment determines tabs, landing page, and visible custom fields.

Deactivating a user preserves history and object ownership but blocks login; deleting a user requires reassigning owned objects and removes the account.

Teams and job roles drive assignment and reporting; a user can belong to multiple teams but has one home team.

Sharing a report, dashboard, or custom form requires the Share permission; the recipient still needs the relevant access level to open it.

A user's access level can be System Administrator or a custom level; system administrators bypass object sharing restrictions.