Adobe Workfront Core Developer Professional key terms

A configurable set of screen settings assigned to users or groups that controls which tabs, fields, and left-panel items they see. It shapes the interface without granting data access itself.

A named bundle of permissions that sets what a user can do across Workfront, such as create projects or edit reports. It works together with sharing permissions on individual objects.

An organizational unit that can contain users, teams, and other groups, used to administer access, layouts, and approvals. Groups can be nested and often mirror a company's department structure.

A container that groups projects and programs so leaders can compare, prioritize, and report on them together. Portfolios support scoring and optimization of competing work.

A project configured to accept incoming issues through a public or embedded form, routing each request to the right team. It defines topic groups and routing rules that classify submissions.

A set of queue topics inside a request queue that narrows the type of request a user is submitting. Choosing a topic determines the custom form and default routing.

An instruction on a request queue that automatically assigns submitted issues to a team, user, or job role and can set default fields. Rules can send requests to different destinations based on topic.

A reusable set of milestones that marks key checkpoints on a project or task, used to track progress. Milestone paths attach to projects and report on whether checkpoints were hit.

A marker on a project or task that flags a key date or deliverable without representing work itself. Milestones are used in reports and milestone paths to track progress.

A questionnaire of weighted questions used to compare projects in a portfolio or program. Scores feed alignment and prioritization decisions in portfolio optimization.

A collection of custom fields arranged in sections that is attached to objects like projects, tasks, or issues to capture extra data. Forms can be shared and made required.

A field you define to store information Workfront does not track natively, added to an object through a custom form. Each field has a type, label, and optional validation.

A custom field whose value is produced by a formula using other fields rather than typed by a user. It updates automatically when referenced values change.

The interface where you build expressions for calculated fields, complete with a field list, function reference, and preview. It shows errors and the resulting data type before saving.

A divider inside a custom form that groups fields under a heading and can control visibility. It can also add a descriptive text block or gate access to later sections.

Rules that show, hide, or require form fields based on values a user has entered, keeping forms short and relevant. Logic is configured per field in the form designer.

A custom field that pulls values from a JSON endpoint outside Workfront at the moment a user opens the form. It requires a configured API URL and display values.

A set of criteria that limits which records appear in a report, list, or view. Filters can combine AND/OR statements and use prompts or wildcards.

The column layout of a list or report that determines which fields appear and in what order. Views can include calculated columns and conditional formatting.

A report setting that clusters results under shared values, such as by status or owner, and can show subtotals. Groupings can be nested several levels deep.

A report element that asks the viewer to choose values before the report runs, making one report serve many audiences. Prompts can filter, group, or change columns.

A code-like editing mode that exposes the underlying statements behind filters, views, groupings, and calculated columns. It enables logic that the standard interface cannot express.

A column in a view whose value is computed with an expression, often combining fields or applying conditional logic. It is defined in text mode and appears in reports and lists.

A saved query on a chosen object type that returns a list, chart, or matrix of records using filters, views, and groupings. Reports can be shared, scheduled, and placed on dashboards.

A page that arranges reports, calendars, and external content into a single view for a team or leader. Dashboards can be shared and laid out in customizable sections.

An automated email that sends a report or dashboard on a repeating schedule to selected recipients in a chosen format. Deliveries can be limited to when the report has results.

A reusable blueprint of tasks, assignments, forms, and settings used to create consistent new projects. Templates can include queues, approvals, and financial defaults.

A task setting that decides which values stay fixed when effort, duration, or assignments change. Common options include calculated assignment, effort-driven, and fixed dates.

A relationship that makes one task wait for another, optionally with a lag, forming the project schedule. Predecessor types include finish-to-start and start-to-start.

A rule that ties a task's planned dates to a specific condition, such as as-soon-as-possible or must-finish-on. Constraints affect how scheduling recalculates dates.

A defined sequence of approvers and stages that a project, task, issue, document, or timesheet must pass. Processes can be global and reusable or created for one object only.

A step within an approval process that contains one or more approvers and a rule for how many must agree. Stages run in order and stop the process if rejected.

A group of users who can be assigned work together and whose members share visibility of team-related items. Teams are often used for resource planning and assignment.

A credential a user generates in Workfront to authenticate API calls without sending a password. Keys inherit the user's permissions and should be treated as secrets.

Workfront's HTTP interface for reading and writing objects such as projects, tasks, and users using standard methods and JSON. Endpoints follow a predictable object-based URL pattern.

An integration platform that connects Workfront to other systems with automated scenarios, modules, and triggers. It can transform data, handle errors, and run on schedules or events.

A registration that makes Workfront send an HTTP POST to a URL whenever a chosen object changes. It enables near-real-time integrations without polling.

The category assigned to a user, such as Plan, Work, Review, or Request, that caps which features and objects they can use. It works alongside the access level.

The per-object settings that grant users or groups Manage, Contribute, or View rights on a project, report, or other item. Sharing can be inherited from parent objects.

Rights a user receives on an object because they hold permissions on a parent object, such as a project's tasks. Inheritance reduces manual sharing but can widen access unexpectedly.