ÃÛ¶¹ÊÓƵ

The sum of the Actual Amounts for all expenses logged for a project or a task.

EXAMPLE

If you create an expense for Task 1 and enter $600.00 in the Actual Amount field, the Actual Expense Cost for this task is $600.00.

For a project, Workfront uses the following formula to calculate Actual Expense Cost:

Project Actual Expense Cost = SUM (All Project Actual Expense Costs) + SUM (All Tasks Actual Expense Costs) + Project Fixed Cost

In a project, task, or issue report, Actual Hours are the sum of all hours logged on the project, task, or issue.

Example: If from the Updates tab for Task 1, you click 'Log Time' and enter 25 hours, the Actual Hours of Task 1 = 25 hours.

Workfront calculates Actual Hours for parent tasks or projects using the following formulas:

• For parent tasks = children Actual Hours + Actual Hours on the parent task.

• For projects = Actual Hours logged on the project + Actual Hours logged on standalone or children tasks in the project

The Actual Cost associated with the labor invested in a task or a project.

For a task, Workfront calculates the Actual Labor Cost using the following formula:

Task Actual Labor Cost = Number of Actual Hours on the task * User or Job Role Hourly Cost Rate

If the task has a Cost Type of User Hourly, Workfront uses the user rate. If the task has a Cost Type of Role Hourly, Workfront uses the job role rate to calculate Actual Labor Cost.

For a project, Workfront uses the following formula to calculate the Actual Labor Cost:

Project Actual Labor Cost = SUM(All Tasks Actual Labor Cost)

For more information, see Track costs.

Example: For example, if a user logs 5 hours for a task with a User Hourly Cost Type and their hourly rate is $100, the Actual Labor Cost is $500.

The Actual Revenue of a project or a task is the amount of money associated with the Actual Hours of the project or the task.

For information about tracking revenue in Workfront, see Overview of Billing and Revenue.

When this is referenced in filters, this field displays either users that belong to any of the teams that the logged-in user belongs to, or work items assigned to any of the teams that the logged-in user belongs to.

We recommend using this field in a filter to make reports more generic when sharing them with other users. This way, you can build only one report which will display different information depending on who logs in to view it, as the information is always customized for the logged-in user.

You can find this field in the following types of reports:

• Project (Financial Data)

• Budgeted Hour

Financial information populates in Project (Financial Data) reports only when the data associated with it is less than 5 years old. For example, if a job role was allocated to a task in January 2015 and today is September 2021, a financial field like the Allocation Date for the job role does not populate in the Project (Financial Data) report.

For a Budgeted Hour report:

• Build this report when trying to understand the amount of Budgeted Hours that is allocated to your resources or to your projects in the Resource Planner.

• The Allocation Date is the first day (a Sunday) of the week for which you budgeted the hours in the Resource Planner.

  TIP

  If a week spans for two months, it will generate two rows in the report: one corresponding to the first day of the week (Sunday of the first week which is during the first month), and the second row displays the first day of the second month.

  For example, if you budget 8 hours for a user for the week of June 30 (Sunday) - July 6 (Saturday), the two rows show an Allocation Date of June 30, and July 1.

  For information about budgeting resources in the Resource Planner, see the article Budget resources in the Resource Planner using the Project and Role views.

  For information about building a Budgeted Hour report, see Report: Budgeted Hour.

A way to communicate to users information within the system. This information is often coming from Workfront to the Administrator or from the Administrator to the user.

For more information, see Send announcements

A given work item, such as a task, document, or timesheet, may require that a supervisor or other user sign off on the work item. This process of signing off is called approval.

For more information, see Approval process overview.

In a Task or Issue report, this field displays a list of all entities (users, job roles, teams) that are assigned to the task or issue. You can filter by this field using the fields Assignment Users and Assignment Roles. You can filter by the team assigned to the task or issue using the Team field. You cannot group a report by this field.

Work items that have been placed in the Recycle Bin will continue to display in some reports that refer to the Assignment object where an OR filter modifier is used.

In an assignment, task, or issue report, the Assignment Status displays whether the users assigned to a work item have clicked the Work On It or the Done button to accept or complete the work. The following Assignment Statuses exist:

• Requested: the user has been assigned to the task or issue, but they have not clicked the Work On It button to start working on it yet.
• Working: the user has clicked the Work On It button and is currently working on the item.
• Done: the user has clicked the Done button and has completed their work on the item.

For more information, see Work On It and Done button overview.

Audits are system messages that record an action that happened in Workfront. The following audit types are recorded:

• Scope Change
• Attachment Action
• General Edit
• Status Change
• Note
• Combined Entry
• Error Entry
• Status Change
• Subscription Change

One of the Project Update types. This will recalculate the Project's Projected and Planned timelines when the nightly recalculation process runs and when any update is made to the project or tasks within the Project.

For more information, see Select the project Update Type.

This term is used in relation to "user availability" or "resource availability" and it illustrates the amount of time that the resource (user or job role) is available to work.

Workfront calculates user availability using several fields and depending on what the settings of the Resource Management preferences are in your system. For more information, see Configure Resource Management preferences.

For more information about resource availability, see Get started with Resource Management

Alternately, "capacity" is also used to refer to resource availability.

One of the Project Update types. This will recalculate Projected and Planned timelines when the nightly recalculation process runs.

For more information, see Select the project Update Type.

An expense that is marked as billable to the customer. This can be either a planned expense or an actual expense.

The Planned Billable Expense Cost and Actual Billable Expense Cost fields are available for you to add to views and reports. They do not appear on the project or task details pages.

You can find these fields in the following types of reports:

• Baseline
• Template
• Project (Financial Data)

For more information about marking an expense as billable, see Manage project expenses.

Records the revenue, hours, or expenses that can be billed. This information can be used to create invoices in an external accounting system.

For more information, see Create billing records.

The process of customizing Workfront to give the interface an appearance that mirrors your company by using your colors and logos.

NOTE
If your organization has been onboarded to ÃÛ¶¹ÊÓƵ Experience Cloud, branding is not available.

The area at the top of the page that shows the hierarchical location of where the user is in the application.

For more information, see Breadcrumbs overview.

This is a deprecated field. Any information that this field might display is related to a feature that Workfront has removed and the field cannot be updated.

This field shows whether the project was added to the Capacity Planner and if the budget calculation has been completed for it. The Capacity Planner has been removed from Workfront.

This is a deprecated field. Any information that this field might display is related to a feature that Workfront has removed. This field cannot be updated.

This field is still visible in project reports and lists.

This is the cost associated with budgeting resources for a project.

The field displays in the following areas of Workfront under the following names:

• Budgeted Cost: in the Business Case Summary panel
• Cost: in the Utilization areas when viewing information by Cost
• Project Budgeted Cost: in lists and reports

The Budgeted Cost for the project is calculated using the following formula:

Project Budgeted Cost (or Budgeted Cost) = Budgeted Expense Cost + Budgeted Labor Cost + Fixed Cost of the project

For more information about calculating Budgeted Cost and to understand various names for this concept in Workfront, see Calculate Project Budgeted Cost.

The hours budgeted for resources for the work they need to complete on projects. This field refers to the hours budgeted in the Resource Budgeting area of the Business Case (or in the Resource Planner) for the project or for the project resources.

For more information, see Understand Budgeted Labor Cost and Budgeted Hours for projects.

For information about budgeting Users in the Resource Planner, see the article Budget resources in the Resource Planner using the Project and Role views.

The hours budgeted in the Resource Budgeting area of the Business Case or the Resource Planner display in the following areas of Workfront and under the following names:

Any other mention of Budgeted Hours in ÃÛ¶¹ÊÓƵ Workfront refers to hours budgeted using deprecated features that have been removed from Workfront . These are view-only fields and do not update with current information when you use current resource budgeting tools.

This is the cost associated with the hours that you, as the Resource Manager, budget for your job roles for the work they need to complete on projects.

The Budgeted Labor Cost in a project report is calculated using the following formula:

Budgeted Labor Cost = SUM(Job Role Cost per Hour * Budgeted Hours per Job Role)

This field may refer to the following:

• Labor costs displayed in the Resource Budgeting area of the Business Case or in the Resource Planner that are associated with the cost of job roles on a project. For information about calculating the Budgeted Labor Cost, see the article Understand Budgeted Labor Cost and Budgeted Hours for projects

• Labor costs displayed in the Resource Budgeting area of the Business Case that reflect the People Costs estimated in an initiative linked to the project from the Scenario Planner when you use the Scenario Planner to budget your project resources. For information about initiatives, see Initiatives overview in the Scenario Planner.

  The Scenario Planner requires an additional license. For information about the Workfront Scenario Planner, see The Scenario Planner overview.

  It displays in the following areas of under the following names:

  • Budgeted Labor Cost: in the Resource Budgeting area of the Business Case.

  • Budgeted Cost: in the Utilization report Cost view

    For more information, see View resource utilization information.

  • BDG: in the Resource Planner Project or Role views, when viewing by Cost

  • Resource Planner Budgeted Labor Cost: in the following reports:

    • Project report
    • Project (Financial Data) report
    • Task report
    • Issue report
    • Budgeted Hour report

    For more information about creating a report, see the article Create a custom report.

This is a deprecated field. Any information that this field might display is related to a feature that Workfront has removed. This field cannot be updated.

These areas have been removed from Workfront.

The field is still visible in project reports and lists.

A tool used to evaluate whether a project should be moved forward from the Idea status to the Planning status. In other words, a business case helps the organization decide whether it is worthwhile to launch and complete the project or not, especially when comparing projects with others in a portfolio.

For more information, see Create a Business Case for a project.

This is a deprecated field. Any information that this field might display is related to a feature that Workfront has removed. This field cannot be updated.

This field is still visible in project and task lists and reports.

One of the task Duration Types . This will calculate the percentage of an 8-hour work day that the user assigned to the task will be allocated to the task, based on the Duration of the task and the Work Required.

For more information, see Overview of Task Duration and Duration Type.

One of the task Duration Types. This will calculate the Work Required on a task, given the Duration and the user Assignment percentages (which are based on an 8-hour work day).

For more information, see Overview of Task Duration and Duration Type.

In Workfront, a calendar report is a dynamic report in which users can view the date and other important details of an event, including the due date, status of work, and the user to whom the event is assigned.

For more information about calendar reports, see Calendar reports overview.

In Workfront Planning, a Calendar view is a type of view for a record type that displays records on a calendar. You must have an additional license to access Workfront Planning.

This field indicates whether a task is ready to start to be worked on. If the start is ready to be worked on the Can Start field on the task is set to True.

For more information, see "Can Start" overview for tasks.

A category is a custom form. You can build reports for this object and you can show it in other object reports, as well. Not all objects can have a custom form, or category. The following objects can have a custom form:

• Project
• Task
• Issue
• Portfolio
• Document
• Expense
• Program
• User
• Company
• Iteration

When added as a column to the view of any of the following objects it displays a list of all custom forms associated with these objects:

• Project
• Task
• Issue
• Portfolio
• Document
• Expense
• Program
• User
• Company
• Iteration

One of the Issue types, usually indicating that an unplanned amount of work must be done before the project can be completed.

For more information on Issue types, see the section "Default issue types" in the article Customize default issue types.

A Company is an organizational unit in Workfront.

You can associate a user or a project with one company. For more information, see Create and edit companies.

The date that a project, task, or issue is set to be completed. There are several types of Completion dates in Workfront:

• Actual Completion Date. For more information, see Overview of the project Actual Completion Date.
• Planned Completion Date. For more information, see Set the project Planned Completion Date and Overview of the task Planned Completion Date.
• Projected Completion Date. For more information, see Overview of the Projected Completion Date for projects, tasks, and issues.

This indicates how a project will be marked as Complete. It can have two values:

• Manual: A user must change the project status to Complete.
• Automatic: The project status will automatically change to Complete when all of the tasks in the project are 100% Complete and all of the issues are closed.

This is a visual representation of the progress of a task, issue or project.

For projects, the condition can be manually set by the project owner or it can be automatically set by Workfront, based on the progress status of the project.

The possible values for the project condition are:

• On Target
• At Risk
• In Trouble

For more information about project conditions, see the article Overview of Project Condition and Condition Type.

You can associate task and issue conditions with a number that can display in reports. The lists below display the default names and numbers for task and issue conditions. Your system administrator can update the names of conditions and they can add new conditions with different numbers. After a number is associated with a condition, it cannot be edited.

For tasks, the condition is set manually by the task owner. The possible values for the task condition are:

• Going Smoothly (0)
• Some Concerns (1)
• Major Roadblocks (2)

For more information about task conditions, see the article Update Condition for tasks and issues.

For issues, the condition is set manually by the issue owner. The possible values for the issue condition are:

• Going Smoothly (0)
• Some Concerns (1)
• Major Roadblocks (2)

NOTE

When the Condition field is tracked in Journal Entry reports, the New and Old Number Values display the number associated with the condition instead of its name. If a condition is originally not defined for a task or an issue and you later update it, the journal entry that captures the update will display the Old Number Value of the Condition field as -2,147,483,648. See also "New Number Value", "Old Number Value", and "Journal Entry" in this article.

This field shows the current condition of tasks, projects or issues. This option shows the most recent updates that the owners of tasks, projects or issues have provided in the Update Status field, along with the new condition.

Comments made on condition updates are not displayed in the Condition Update column; only the main update is displayed.

In Workfront Planning, you can create a connection between one of the following:

• Two record types
• A record type and a Workfront object type
• A record type and an ÃÛ¶¹ÊÓƵ Experience Manager asset

Connecting record types allows you to display information from one record or object type on another record type.

For information, see Connected record types overview

Workfront Planning requires an additional license.

In Workfront Planning, after you connect two record types, you can connect two individual records of those types to one another.

Connecting records allows you to display information from one record or object from another application on another record.

For information, see Connected records overview.

Workfront Planning requires an additional license.

If you are using a Task Constraint that is tied to a specific date, such as Must Start On, then that specific date becomes the Constraint Date of the task.

The following task constraints update the Constraint Date field:

• Must Start On
• Must Finish On
• Start No Later Than
• Start No Earlier Than

TIP

• A task with a Constraint of Fixed Dates has no Constraint Date.

• Constraint Date is only viewable in a report or customized view.

If you are using a Task Constraint in a template task that is tied to a specific day, such as Must Start On, then that specific day becomes the Constraint Day of the template task.

The following task constraints update the Constraint Day field:

• Must Start On
• Must Finish On
• Start No Later Than
• Start No Earlier Than

TIP

Constraint Day is only viewable in a report or customized view.

The scheduling tendency of a task. For example, As Soon as Possible will schedule a task to begin as soon as possible, and Finish No Later Than will schedule a task to finish by the Constraint Date and no later.

For more information, see Task Constraint overview.

The monetary amount that you must spend when completing a project, task, or issue.

You can track various types of costs for labor, expenses, risks that relate to the project.For information about tracking costs in Workfront see Track costs.

A task of one project is dependent on a task from a different project.

For more information, see Create cross-project predecessors.

Data that is unique to an organization. Organizations can customize the Workfront application by creating custom forms and custom fields. This custom information can drive reporting for KPIs, auditing, and demand mix.

Custom Data can be linked to:

• Projects
• Tasks
• Users
• Companies
• Issues
• Documents
• Expenses
• Portfolios
• Programs
• Iterations

You can add this field in a report or a view of the Report object, to display the dashboards on which the report is listed in a list.

You can use this field to filter for reports that are listed on a specific dashboard, as well.

For more information about including dashboard information on report object reports, see the "Understanding What Reports Are Listed on Dashboards" section in the article Access and organize reports

This field shows a date difference between Planned Start and Today if the Actual Completion Date is missing.

Also shows a date difference between Actual Completion and Planned Completion, when an Actual Completion Date is present.

Customizable default working hours to be assigned to users and projects within an organization.

Schedules are used to calculate the planned, start, and completion dates of tasks that are assigned to users.

The type of scheduling relationship between a task and its predecessor(s). One example is Finish-Start, which requires that the fist task must Finish before the second task can Start.

For more information, see Overview of task dependency types.

Each time the same document is uploaded to the same object, it is assigned a version number. Users can view and change several options for a previous version of a document.

For more information, see Manage document versions.

The date when a task or an issue is due to complete. The Due Date of a task or issue is the same date as the Planned Completion Date.

The task and issue Due Date is visible in task and issue lists and reports.

Also see Planned Completion Date in this table.

The window of time allocated for completion of a task issue, or project (as determined by the number of days between the Planned Start and the Planned Completion).

• For tasks, the Duration is an editable field if the Duration Type of the task is not Simple. If the Duration Type of the task is Simple, or if the Task Constraint is Fixed Dates, the Duration is a calculation performed by Workfront.
• For issues, the Duration is always an editable field and it should represent an estimate of a number of days that would require the issue to be resolved.
• For projects, the Duration is a calculation performed by Workfront and it represents the difference in days between the Planned Start of the earliest task and the Planned Completion of the latest task on the project.

For more information about the difference between Duration and Planned Duration for tasks, see the article Difference between Planned Duration and Duration for tasks.

This displays in the Task Details and the Edit Task boxes of a parent of recurring tasks. It displays the duration of each recurring task. For information about creating recurring tasks, see Create recurring tasks.

Durations modified in individual recurring tasks do not display the value indicated in this field.

A task field that indicates how the work required to complete the task is allocated to the assignees across the task duration. It represents the relationship between the Duration of the task, the Work Required, and the amount of time, or Allocation, the assigned resources should spend on the task to complete it.

This field appears on the Details tab of a task.

The options for the Duration Type of a task are:

• Calculated assignment
• Calculated Work
• Effort Driven
• Simple

For more information, see Overview of Task Duration and Duration Type.

-->

Elapsed time is a unit of time for a task's Duration. It is the time between the Planned Start Date and the Planned Completion Date of a task that includes holidays, weekends, and time off. In other words, elapsed time is the passage of calendar days.

Workfront supports the following elapsed time units for task duration:

• Elapsed Minutes

• Elapsed Hours

• Elapsed Days

• Elapsed Weeks

• Elapsed Months

For more information about task duration, including elapsed time, see Overview of Task Duration and Duration Type.

Typically, this is a license type, or a user with such a license. A user with such a license type only has the ability to review information in the system. They cannot actively participate in work.

For more information, see ÃÛ¶¹ÊÓƵ Workfront licenses overview.

Any Workfront object or the information associated with it, as it appears in the database.

For example, "project", "user", "hour" are both Workfront objects as well as fields. "Name", "status", "owner", "start date" are Workfront fields that are associated with the above objects.

When referring to objects, the terms "objects" and "fields" can be used interchangeably.

In the scope of reporting, the "fields" refer to the objects or the information about the object that you want to capture in the report.

NOTE

In text-more reporting, fields refer to the objects or their information as it appears in the database.

Sometimes the name that you see in the user interface is different from the name of the field in the database. For example, "issue" is the name of the object in the Workfront interface, but "opTask" is the name of the object (or the field) in the Workfront database.

It's important to use the field as it appears in the database when writing a text-mode report, view, filter, or grouping, or when creating a calculated field.

For more information, see API Explorer and Text Mode overview.

By default, Workfront comes with a set of fields that define both objects and their information. You can also create custom fields to define objects, but you cannot create custom objects.

In Workfront Planning, you can create custom fields for all record type. Workfront record types come with a very limited number of fields. You must create all fields from scratch and associate them with record types. For information, see Field overview.

Workfront Planning requires an additional license.

One of the main building blocks of a report or a list element that defines what information displays on the screen. For more information about reporting elements, see Reporting elements: filters, views, and groupings.

The Filter determines the results that display in a report or on an Workfront panel listing, like projects, tasks, or issues.

This is the same field as Status Icons, but it is only available for the following views:

• Templates
• Expenses

For more information, see the article Built-in Status Icons in Views.

This is the Full Time Equivalent which indicates the amount of time that a resource is available for work. The FTE field displays in the following areas:

• User's profile, when editing or creating the user
• Resource Planner
• Scenario Planner (requires additional license for the Workfront Scenario Planner)
• User lists and reports

The FTE must be a decimal number up to 1, and it cannot be 0.

An FTE of 1 (which is the default for a user's FTE field, as defined in their profile) means that a resource (user or role) works the entire number of hours, based on the schedule that calculates their availability.

Your Workfront administrator decides which schedule to use in determining user's availability.

• When the Default Schedule is used, Workfront uses the FTE of the user found in their profile to calculate availability.
• When the User's Schedule is used, Workfront uses the user's time off, Work Time value, and Default Schedule's hours to calculate the user's FTE.

For more information, see Configure Resource Management preferences.

For more information about creating schedules in Workfront, see Create a schedule.

NOTE

For all calculations in the Scenario Planner, Workfront uses the following value: 1 FTE = 8 Hours.

For more information, see Get started with the Scenario Planner.

There are two concepts of goals in Workfront:

• Project goals: A set of business objectives agreed to by the relevant stakeholders of a project. Project goals are part of the Business Case of a project.

  You cannot display project goals in lists or reports but you can access them through the API.

  For information about Business Case project goals, see Create Business Case goals.

• Strategic goals: A strategic goal is an objective that you create to plan your work strategy for a specific time-period. You can create these types of goals using Workfront Goals. Your organization must purchase an additional license and you must have access to this feature to be able to create strategic goals. Workfront Goals are available only with an additional license.

  For more information, see ÃÛ¶¹ÊÓƵ Workfront Goals overview.

  You can display strategic goals in a goal or a project report and access them through the API.

In Goal and Project reports, this is a collection field that displays the goals in the hierarchy that a strategic goal belongs to when it aligns to other goals. The goals are separated by a â–¸ delimiter.

Only the parents of the goal and the goal display in this field. Children goals do not display.

For information about aligning goals in Workfront Goals, see Goal alignment overview in Workfront Goals.

This field is visible only if your organization has purchased Workfront Goals. For information about managing strategic goals using Workfront Goals, see ÃÛ¶¹ÊÓƵ Workfront Goals overview.

In a Project report, this is a collection field that displays all the strategic goals that are associated with a project. The goals are separated by commas.

This field is visible only if your organization has purchased Workfront Goals. For information about managing strategic goals using Workfront Goals, see Workfront Goals overview. For more information about strategic goals and project goals in Workfront, see "Goal" in this article.

A collection of users (possibly from the same department or business unit) that have access to the same objects. In addition to users, groups can be associated with portfolios, programs, projects, project templates, companies, teams, schedules, layout templates, and timesheet profiles.

You can also grant permissions to objects by group. For more information, see Groups overview.

In a list or report of objects of one of the following types, you can use the Group field to list which objects of that type are associated with a particular group: user, portfolio, program, project, project template, company, team, schedule, layout template or timesheet profile.

Users who manage the objects, access, and users of designated user groups.

In a Group report, this field displays the names of the users designated as Group Administrators in the Group. For more information about Group Administrators, see Group administrators.

In a Layout Template, Timesheet Profile, or Schedule report, this field displays the Groups whose Group Administrators have access to modify the template. You can also filter this report by this field.

For more information, see Create and manage layout templates.

A reporting element used to categorize information in a list by a common criterion.

For more information, see the "Groupings" section in the article Reporting elements: filters, views, and groupings.

An attribute set by Workfront for the Actual Hours that users log for tasks, issues, or projects.

Hour entries can have one of the following statuses in Workfront:

• Submitted: the hours have been logged on a project, task, or issue. They are either part of a billing record or not added to a billing record yet.
• Approved: the hours have been logged and they have been approved by the Project Owner. They are either part of a billing record or not added to a billing record yet.
• Not Approved: the hours have been logged and rejected by the Project Owner. They are either part of a billing record or not added to a billing record yet.
• Billed: the hours have been logged, added to a billing record, and the billing record status has been marked as Billed. They did not require to be approved by the Project Owner.
• Billed and Approved: the hours have been logged, approved by the Project Owner, and the billing record status has been marked as Billed.

When hours are part of a billing record, the Hour Status indicates whether the hours have been approved or if the Billing Record they belong to has been billed. The Hour Status of an hour entry is only visible in an hour list or report.

For more information about adding hours to billing records, see the section "Add Hours to billing records" in the article Create billing records.

For more information about approving time on projects, see Require time to be approved for a project.

TIP

General Hours that are not logged directly on work items do not display an Hour Status.

An attribute that can be set for Actual Hours that users log for tasks, issues, or projects. This is also an attribute for the hours logged that are not directly linked to work, such as Vacation and Time Off.

For more information, see Manage hour types.

The ID is an alphanumeric indicator associated with every object in Workfront. It uniquely identifies each object in the Workfront database. You can view the ID of any object in a report or a list for each object.

TIP

You can also view the ID in the URL of the object's page. For example, the ID of a project might look something like the number outlined in the following URL, when you access the Project Details page:

https://<your domain>.my.workfront.com/project/5e29c8010027d8eb334762d4fff3ffca/overview

In the Workfront Scenario Planner, you can divide a plan into several initiatives to make it easier to manage the plan. You can build an Initiative report and you can access Initiative information in a Project report.

The Scenario Planner requires an additional license. For information about the Workfront Scenario Planner, see The Scenario Planner overview.

The Initiative report is not visible in your Workfront instance unless your company has purchased a Workfront Scenario Planner license. You cannot access Initiatives through the API.

The Initiative Job Role report type displays information about the job roles associated with a plan initiative in the Workfront Scenario Planner.

The Scenario Planner requires an additional license. For information about the Workfront Scenario Planner, see The Scenario Planner overview.

This report type is not visible in your Workfront instance unless your company has purchased a Workfront Scenario Planner license.

In an Initiative Job Role report, this displays the number of hours associated with a job role in an initiative.

The Scenario Planner requires an additional license. For information about the Workfront Scenario Planner, see The Scenario Planner overview.

This field and the Initiative Job Role report type are not visible in your Workfront instance unless your company has purchased a Workfront Scenario Planner license.

In an Initiative Job Role report, this displays the number of specific job roles associated with an initiative.

The Scenario Planner requires an additional license. For information about the Workfront Scenario Planner, see The Scenario Planner overview.

This field and the Initiative Job Role report type are not visible in your Workfront instance unless your company has purchased a Workfront Scenario Planner license.

A field in an Initiative, Initiative Job Role, and Project report that displays the date that a plan initiative was last published to a project. You can publish initiatives to create projects or to update projects linked to the initiatives.

The Scenario Planner requires an additional license. For information about the Workfront Scenario Planner, see The Scenario Planner overview.

For information about publishing initiatives, seePublish scenarios to create and update projects in the Workfront Scenario Planner. This field is not visible in your Workfront instance unless your company has purchased a Workfront Scenario Planner license.

In goal reports, this displays a "True/ False" value for each strategic goal to indicate whether your organization is assigned to the goal as its owner.

This field is visible only if your organization has purchased Workfront Goals. For information about managing strategic goals using Workfront Goals, see ÃÛ¶¹ÊÓƵ Workfront Goals overview.

An unplanned work item that usually indicates that there is a problem preventing the completion of a task or project. It is triaged and evaluated for further work effort consideration

An Issue can also be a Help Desk request. Change Orders, Requests, and Bugs are also Issues.

Used to identify a user's day-to-day job functions and responsibilities. Job roles can be assigned to work items to identify the required skill needed to complete a work process without assigning it to a specific user.

A user can have more than one role. Examples include Graphic Designer or Consultant.

For more information, see Create and manage job roles.

A reportable object that tells you information about system updates for tracked fields that appear in the Updates area of projects, tasks, issues, and other objects.

To learn more, see Report on the Updates area.

In a Task Report or Issue Report, the Kanban Flag field displays the flag status that is set on the story on the Kanban board. Possible values are On Track, Ready to Pull, and Is Blocked.

For more information about setting flag status on stories on the Kanban story board, see  the article Use flags on stories on the Kanban board.

The method of calculating the Lag. It can be:

• Days (work days)
• Calendar Days (ignore holidays)
• Percent
• Day of Week

For more information, see Lag Types overview.

In a Document list or report, it displays a preview of the document in a thumbnail.

Select Large Thumbnail to view a 400 pixel-wide thumbnail in the report.

The size of the thumbnail adjusts when you modify the width of the column in a list or report.

See also "Thumbnail" in this article.

This field displays the update last entered on an object by the owner of the object, This is the owner's most recent activity or interaction on an object.

The Last Condition Note column is empty if the note text of the last note of an object has been deleted. When a new note is entered on the object, it becomes the last note and it displays again in the column.

This field displays the update last entered on an object by any user. This is the most recent activity or interaction on an object.

The Last Note column is empty if the text of the last note of an object has been deleted. When a new note is entered on the object, it becomes the last note and it displays again in the column.

When this field is added to a Task report, any updates left on child objects — such as issues, subtasks, documents, etc. — of the task do not display in this column.

In Workfront Planning, after you establish the connection between two record types and you link individual records together, you can reference the linked records' fields on the record you are connecting from.

For example, if you connect a Campaign record type with a Workfront Project object type, you can display the Budget field of connected projects on the campaign records. The Budget project field is a lookup field from projects on a campaign.

The values of lookup fields are automatically populated on the records they are connected from.

For information, see Connected records overview.

Workfront Planning requires an additional license.

One of a Project's Update Types. This setting allows Project Projected and Planned timelines to be updated only when "Recalculated Timelines" is clicked. Projects set up this way will be ignored during the nightly recalculation process and when the project or tasks in the project are updated.

For more information, see Select the project Update Type.

This refers to the currently logged-in user.

We recommend using this field in a filter to make reports more generic when sharing them with other users. This way, you can build only one report which will display different information depending on who logs in to view it, as the information is always customized for the logged-in user.

This is a deprecated field. Any information that this field might display is related to a feature that Workfront has removed and the field cannot be updated.

In previous releases of Workfront, you could update this field when creating or editing a job role. It displayed the total number of users that can be associated with a role on each project. A value of zero allowed for an unlimited number of users that can be assigned on a project.

The field is still visible in some reports and lists, but the information displayed cannot be updated.

When this is referenced in filters, this displays either users that have the same Primary Role as the logged-in user, or work items assigned to the Primary Role of the logged-in user.

We recommend using this field in a filter to make reports more generic when sharing them with other users. This way, you can build only one report which will display different information depending on who logs in to view it, as the information is always customized for the logged-in user.

When this is referenced in filters, this field displays either users that belong to the Home Team of the logged-in user, or work items assigned to the Home Team of the logged-in user.

We recommend using this field in a filter to make reports more generic when sharing them with other users. This way, you can build only one report which will display different information depending on who logs in to view it, as the information is always customized for the logged-in user.

An expense that is not marked as billable to the customer. This can be either a planned expense or an actual expense.

The Planned Non-Billable Expense Cost and Actual Non-Billable Expense Cost fields are available for you to add to views and reports. They do not appear on the project or task details pages.

You can find these fields in the following types of reports:

• Baseline
• Template
• Project (Financial Data)

For more information about marking an expense as billable, see Manage project expenses.

In a Project report, this is the number of strategic goals that are associated with the project. For information about associating projects with strategic goals, see Add projects to goals in ÃÛ¶¹ÊÓƵ Workfront Goals.

For information about strategic goals, also see "Goal" in this article.

This field is visible only if your organization has purchased Workfront Goals. For information about managing strategic goals using Workfront Goals, see Add projects to goals in ÃÛ¶¹ÊÓƵ Workfront Goals.

The information you display in ÃÛ¶¹ÊÓƵ Workfront is represented by objects which are stored in the Workfront database. The objects are what drives the information in Workfront. Some examples of objects are:

• Portfolios

• Programs

• Projects

• Tasks

• Issues

• Documents

• Dashboards

• Reports

• Groups

• Teams

• Users

• Companies

• Custom forms

• Custom fields

• Hours

• Billing Rates

• Templates

• Template tasks

  NOTE

  This is not an extensive list.

For more information, see Understand objects in ÃÛ¶¹ÊÓƵ Workfront.

One of the Project Update Types. When this is selected, the Project Projected and Planned timelines update only when an update or change is made to the project or to a task within the project. It does not update the project every night.

For more information, see Select the project Update Type.

In a Job Role report, this is the currency associated with a job role. It is an override of the Base Currency as established in the Setup area by the Workfront administrator.

For more information, see Create and manage job roles.

In a Job Role report, this is the billing per hour rate of the job role using the selected Override Currency of the job role.

For more information, see Create and manage job roles.

In a Job Role report, this is the cost per hour rate of the job role using the selected Override Currency of the job role.

For more information, see Create and manage job roles.

In a Goal report, this displays the type of owner that is assigned to a strategic goal. The following are the goal owner types:

• User

• Team

• Group

No value displays in this field when the goal owner is your organization.

This requires an additional license. For information about Workfront Goals, see ÃÛ¶¹ÊÓƵ Workfront Goals overview.

A project, task, or issue field that shows what percentage of the work associated with the task, project, or issue is completed.

You can update this field manually for issues and working tasks.

For projects and parent tasks, this field is a roll-up from all the working tasks and you cannot update it manually.

For more information, see Project Percent Complete overview.

Rights that are granted to a user on an object, typically given so they can complete work on the item or view the item. You can grant permissions to:

• Projects
• Tasks
• Issues
• Portfolios
• Programs
• Reports
• Dashboards
• Documents
• Custom Forms
• Views
• Filters
• Groupings

For more information, see Overview of sharing permissions on objects.

This is a full license type in the Workfront system. Users must have this to access all of the features in Workfront.

For more information, see ÃÛ¶¹ÊÓƵ Workfront licenses overview.

A plan is the main object when working with the Workfront Scenario Planner. You can outline the strategy for your company's near and long-term future and identify each high-level outcome and add it as a plan to the Workfront Scenario Planner.

You cannot display Scenario Planner plans in a report and you cannot access them through the Workfront API.

The Scenario Planner requires an additional license. For information about the Workfront Scenario Planner, see The Scenario Planner overview.

In a Budgeted Hour report, this displays the number of hours budgeted for projects or Job Roles in the Resource Planner.

For information about budgeting projects or roles in the Resource Planner, see the article Budget resources in the Resource Planner using the Project and Role views. For information about the Budgeted Hours report, see the article Report: Budgeted Hour.

You can manually set the Planned Completion Date of a task, project, or issue to a date of your choosing. If you do not set the Planned Completion Date, Workfront sets it automatically. When set automatically, the Planned Completion Date is: Planned Start Date + Duration

For more information, see the following articles:

• Overview of the task Planned Completion Date

• Set the project Planned Completion Date

This is an automatic indicator that Workfront assigns projects, tasks, and issues to show when an item will be completed in relation to its Planned Completion Date.

The following are possible values for the Planned Date Alignment indicator:

• Will be done on the planned completion date
• Will be done before the planned completion date
• Will be done after the planned completion date

The Planned Date Alignment is visible in project, task, and issue lists and reports.

A task's Planned Duration is usually the same as the task's Duration. It represents the difference in days between the Planned Start and the Planned Completion Dates of the task.

When the task has a Duration Type of Effort Driven, the Planned Duration can differ from the Duration of the task, based on how many resources you assign to the task.

For example, if a task with a Duration Type of Effort Driven has a Duration of 3 days and you assign one resource with a full-time schedule to the task, the Planned Duration is 3 days, as well. If you assign three resources with a full-time schedule to the same task, the Duration stays 3 days, but the Planned Duration becomes 1 day. The Planned Duration also changes the Planned Start and Planned Completion dates of the task, to reflect the new Planned Duration. As a result, the timeline of the project is affected as well.

For more information about the difference between Duration and Planned Duration for tasks, see the article Difference between Planned Duration and Duration for tasks.

Projects and issues don't have a Planned Duration.

The Planned Duration Minutes of a project or an issue is the Duration of the project or issue in minutes.

Tasks don't have a Planned Duration Minutes field.

Template Tasks have a Planned Duration Minutes field which displays the Planned Duration of the task in minutes.

The sum of the Planned Amounts for all expenses logged for a project or a task.

EXAMPLE

If you create an expense for Task 1 and enter $600.00 in the Planned Amount field, the Planned Expense Cost for this task is $600.00.

For a project, Workfront uses the following formula to calculate Planned Expense Cost:

Project Planned Expense Cost = SUM (All Project Planned Expense Costs) + SUM (All Tasks Planned Expense Costs)

This field appears in the projects, tasks, and issues areas, reports for projects, tasks, or issues, and resource management tools like the Resource Planner, Workload Balancer and the Utilization report.

It shows the number of hours that the Project Owner estimates that each task or issue should take to complete. For projects, it is generally a roll-up of the Planned Hours from the tasks on the project.

The Planned Hours field might display different information depending on where you view it from. For information about Planned Hours, see Planned Hours overview.

Planned Hours are stored in minutes in the Workfront database. When writing calculations using this field, ensure you account for the fact that the hours display as minutes.

By default, Planned Hours are distributed equally to all the days within the duration of a work item and also equally for all resources assigned to the task. Users can update the daily number of Planned Hours for a work item or the individual Planned Hours for each assignee.

Updating this field differs for projects, tasks, and issues:

• For issues, you can manually update this field. Issue Planned Hours are not added to the Project Planned Hours.

  TIP

  In an issue report, one of the Planned Hours fields is replaced by the Work field. The field displays the number of Planned Hours on the issue. For more information, see the "work" or "Work" fields in this table.

• For tasks, you can manually update this field when the Duration Type of the task is Calculated Assignment or Simple. This field is calculated by Workfront when the Duration Type of the task is Calculated Work or Effort Driven.
  For information about Task Duration, see the article Overview of Task Duration and Duration Type.

• For projects, Workfront calculates the Planned Hours by adding all Planned Hours from all the tasks on the project.

TIP

You can display Planned Hours in project, task, or issues reports also by using text mode and reference additional fields. For more information, see the "work", "Work", and "workRequiredExpression" fields in this table.

For a task, the hourly rate of the user or role multiplied by the number of hours assigned to the user or role.

For a project, it is a total of all Planned Labor Costs of all the tasks.

Whether the rate of the user or role is used depends on the Cost Type that is selected for the given task.

For more information, see Track costs.

Tasks and projects can display a value for Planned Revenue in Workfront. Planned Revenue represents the amount of money associated with the Planned Hours of the tasks on the project. For projects, it can also include the Fixed Revenue of the project.

For tasks, this is the revenue associated with the Planned Hours of tasks. The Planned Hours from all tasks roll up to the Planned Hours of the project to contribute to the calculation of the project Planned Hours.

Workfront calculates Planned Revenue for tasks and projects using the following formulas:

Task Planned Revenue = Planned Hours * Billing hourly rate

Project Planned Revenue = SUM (All tasks Planned Revenue) + Fixed Revenue

The project Planned Revenue that displays in the Project Details area and in project reports differs from the Planned Revenue that displays in the Utilization report.

The Planned Revenue in the Project Details area reflects the task revenue as well as the Fixed Revenue of the project. The Planned Revenue in the Utilization Report displays Planned Revenue associated only with the tasks in the project.

EXAMPLE

If the project has 1 task with 10 hours, assigned to a Consultant with $20 hourly rate, and the project has $100 Fixed Revenue, the Utilization report displays $200 for Planned Revenue (the Planned Revenue associated with the hours on the task). The Project Details section displays $300 (the Planned Revenue from the task and the Fixed Revenue for the project.)

For information about tracking revenue in Workfront see Overview of Billing and Revenue.

For information about Planned Revenue calculations in the Utilization report, see View resource utilization information.

The total of the Potential Cost of all the risks on the project factoring in their Probability of occurring. This amount is not included in the Planned Cost of the project.

The Planned Risk Cost of a project is calculated by the following formula:

Planned Risk Cost = SUM(Potential Risk Cost * Probability / 100)

A collection of projects that have unifying characteristics. Those projects usually compete for the same resources, budget, or time slot. You can divide Portfolios into Programs and associate the projects with the Programs before they are added to a Portfolio.

For more information about portfolios, see Portfolio overview in ÃÛ¶¹ÊÓƵ Workfront.

A task that must be completed prior to the completion of a dependent task. Also a task that is marked as a Dependency for another task. Predecessors allow the planner to set sequence-dependency logic, such as to start a task after another task finishes.

For more information, see Overview of task predecessors.

The Primary Contact is the creator of an issue and it is automatically designated by Workfront when the someone creates the issue. You can manually update this field if you have Manage permissions to the issue. An issue can have only one Primary Contact.

If you change the Primary Contact, the user originally designated as the primary contact still has Manage access to the issue.

When converting an issue to a task or a project, the user designated as the Primary Contact of the issue becomes the Converted Issue Originator of the project or task. If the Primary Contact of the issue is updated after the issue was converted, the Converted Issue Originator will be preserved as the Primary Contact of the issue at the moment when the conversion happened. See also "Converted Issue Originator" in this article.

In a Goal report, this displays the percent of how close a strategic goal is to completing. The percent of progress displays as a number. For information about strategic goals, also see "Goal" in this table.

This field is visible only if your organization has purchased Workfront Goals. For information about managing strategic goals using Workfront Goals, see Add projects to goals in ÃÛ¶¹ÊÓƵ Workfront Goals.

In a Project, Task, and Goal report, this field displays the Progress Status of projects, tasks, or strategic goals. For more information, see the following articles:

• Project Progress Status overview

• Task Progress Status overview

• Overview of goal progress and condition in ÃÛ¶¹ÊÓƵ Workfront Goals

  The Goal report and the Progress Status for goals field are visible only if your organization has purchased Workfront Goals. For information about strategic goals in Workfront Goals, see Workfront Goals overview.

This is the Budgeted Cost of a project as it displays in lists and reports.

See also "Budgeted Cost" in this article.

The collection of users or roles assigned to a project

For more information, see Project Team overview.

An estimate of the timestamp of when the work will be completed based on the planned hours and percentage complete of a task, issue, or project.

This refers to dates or the Duration of tasks, issues, or projects. Usually, it designates dates and durations that are more true to the life of the work items, after some work has already been completed or some time has passed.

For example, the Projected Completion Date of a task is the date when Workfront estimates that the task will complete, based on how much work has been done on it so far, how many people are assigned to it, and how much time has passed since the start date.

In reports that contain the Document Version object (such as a Document Version report and Proof Approval report), displays the progress status of the proof (Sent, Opened, Commented, Decision Made).

For more information, see Proof progress overview in Proof progress and status overview.

A property on a Help Request Queue that allows users submitting an issue to select a Topic. Topics can:

• Be associated with a Custom Data Form.
• Assign the issue automatically to a user, role, or team through the Routing Rule set on the selected Topic.
• Move the issue to a different project or queue through the routing rule set on the selected topic.

For more information, see Create Queue Topics.

In Workfront Planning, a record is a unique instance of a record type.

After adding a record type to a workspace, you can start adding records of that type on the record type's page.

For example, "Campaign" can be a record type and "Summer Campaign for EMEA" is a record of the Campaign record type.

For information about creating records, see Create records.

Workfront Planning requires an additional license.

The object type of Workfront Planning.

Unlike Workfront, where the object types are predefined, in Workfront Planning, you can create your own object types.Workfront Planning object types are called record types.

For example, in Workfront the object types of Program, Portfolio, Project, Task, or Issue are already created.

In Workfront Planning, you can create any record types that meet your organization's workflows. Later, you can define how the record types relate to one another or form dependencies.

For information about creating record types, see Create record types.

Workfront Planning requires an additional license.

Projects, tasks, and issues are automatically associated with a unique reference number as they are created. You can view the Reference Number in the Details page of projects, tasks, or issues, or in a list or report.

TIP

You can defer to reference numbers when two items have the same name, as reference numbers are always unique.

Workfront automatically generates sequential reference numberss at the system level. Each project, task, or issue gets the next available number in the sequence.

For example, if User A creates a task, Workfront might automatically assign the task the Reference Number of 100. If User B creates an issue right after this, Workfront assigns the issue the Reference Number of 101. You cannot manually edit Reference Numbers.

Workfront objects are always connected to each other using one of the following relationship types:

• One to many: In this relationship, one object can be connected to multiple other objects of different types. For example one project can have multiple tasks. The Project-Tasks relationship is a one to many relationship. You cannot display this relationship in a report using the Standard interface. You must use text mode reporting to view one to many relationships.
• One to one: In this relationship, one object can only be connected to one other object of a different type. For example, a project can only have one Group. The Project-Group relationship is a one to one relationship. You can display one to one relationships between objects in a Standard report.
• Many to one: In this relationship, multiple objects can be connected to only one other objects of a different type. For example multiple tasks can be connected to the same project. The Tasks-Project relationship is a many to one relationship. You can display many to one relationships between objects in a Standard report.
• Many to many: In this relationship, multiple objects of the same type can be connected to multiple objects of a different type. For example, several users can belong to multiple Other Teams, and the teams can belong to several users. You cannot display this relationship in a report using the Standard interface. You must use text mode reporting to view many to many relationships.

A project field that shows the difference between the Planned Risk Cost of a project and the total of all Actual Costs of all risks on the project.

The Remaining Risk Cost for a project is calculated using on the following formula:

Remaining Risk Cost = Project Planned Risk Cost - SUM(Actual Cost for all risks)

In an issue report, use this field in views or filters to refer to the issue that resolves the issue.

For information about displaying resolving objects in reports, see View Resolvable and Resolving Object information in a report in Overview of Resolving and Resolvable Objects.

In an issue report, use this field in views or filters to refer to the project that resolves the issue.

For information about displaying resolving objects in reports, see View Resolvable and Resolving Object information in a report in Overview of Resolving and Resolvable Objects.

In an issue report, use this field in views or filters to refer to the task that resolves the issue.

For information about displaying resolving objects in reports, see View Resolvable and Resolving Object information in a report in Overview of Resolving and Resolvable Objects.

Resource Management is an enterprise set of tools that allows you to accurately forecast the use of your resources based on their availability so that the work that must be done is completed on time and on budget.

With Resource Management tools you can plan long-term capacity and short-term scheduling needs for your resources.

For information about Resource Management in Workfront, see Get started with Resource Management.

In a project report or list view, this is an informational field that displays users designated to perform resource management activities on the project. When you use "Resource Managers" in a report, a list of resource managers is displayed, with each resource manager on the project separated by a comma. You can designate up to 30 resource managers on a given project.

For more information, see the article Designate Resource Managers for a project or template.

These is the cost associated with the hours budgeted for project job roles using the Resource Planner.

See also "Budgeted Labor Cost" in this article.

Resource Pools are collections of users that can be associated with a project. The users in the same Resource Pool usually belong to the same department, have similar or complementary skills, or are funded by the same budget. You can associate multiple Resource Pools to a project or to a user. A resource pool can be assigned exclusively to a project or shared by several projects.

For more information about resource pools, see Resource pools overview.

In project reports, Resource Pools show all the pools associated with a project. This object cannot be used in a grouping.

This may refer to the following concepts in Workfront:

• A field on a project that indicates how risky a project can be. You can prioritize the execution of your projects based on the level of risk. Projects can have the following levels of risk:

  - Very Low

  - Low

  - Medium

  - High

  - Very High

  The levels of risks you indicate for a project cannot be customized.

  For information about updating the Risk of a project, see the " Project Settings" section of the article Edit projects. You can display the risk field of a project in reports.

• An event that might occur during the life of a project that identifies a potential impact to the cost, scope, or schedule of the project. You define potential risks to a project and associate a probability of them occurring or a cost as you build the project's Business Case. For information about adding risks to the Business Case of the project, see "Create and edit risks on projects".

  You cannot display risks defined in the Business Case in reports. You can only display several types of Risk Costs in reports and lists.

The cost associated with the risks on a project. The following are risk costs associated with projects that you can display in reports:

• Actual Cost: a field on a risk that shows the actual cost for the risk that has occurred. In addition to reports and lists, you can locate it in the Edit Risk box when editing or creating a risk.

  For project, task, or issue costs, see "Actual Cost" in this article.

• Planned Risk Cost: a field on the project that shows a total of all Potential Risk Costs for the project. See also "Planned Risk Cost" in this article.

  For information about Potential Risk Cost, see Calculate Potential Risk Cost.

• Remaining Risk Cost: a field on the project that displays the difference between the total of the Actual Costs of all risks and the Planned Risk Cost. See also "Remaining Risk Cost" in this article.

A scenario is comprised of a series of steps (modules) that indicate how data should be transferred and transformed between apps/ services.

For information about scenarios in Workfront Fusion, see ÃÛ¶¹ÊÓƵ Workfront Fusion scenario overview.

In the Scenario Planner, a scenario is a copy of a plan.

The Scenario Planner requires an additional license. For information about the Workfront Scenario Planner, see The Scenario Planner overview.

For information about creating scenarios, see Create and compare plan scenarios in the Scenario Planner.

When you build a report of reports, you can display information about the schedules of the report, if the report is scheduled for delivery using the Scheduled Report field. This field shows multiple values, one for each schedule of each report, in a bulleted list. For more information about scheduling reports, see the article Report delivery overview.

Because this field shows multiple values, it cannot be used in a grouping. You can access it only in a filter or a view.

Severity is an indication of how likely an item is to impact the completion of the work. For example, an issue with high Severity may completely block a task's completion, but an issue with low Severity may be merely cosmetic.

For more information, see Update issue severity.

When assigning tasks or issues to users, Workfront makes recommendations (Smart Assignments) about who the best users are to complete the work, based on the time they have available to complete it and their relationship to the project.

For more information , see Smart assignments overview.

Indicates the parent object of another object. For example, a document attached to a task has the name of the task in the Source field of a Document report or view; an issue logged under a project has the name of the project in the Source field of an Issue report or view.

The following reports display a Source column where you can view information about the parent object:

• Issue reports
• Hour reports
• Document reports

If users don't have permissions to the parent object of an issue, hour, or document, the Source column of the report displays empty, even when the report is configured to display, or to be delivered with the access rights of another user.

In order to show information about the parent object in the report, we recommend adding a column for the parent object where you can display the name of the parent.

For example, you can add any of the following to a report with a Source column:

• The Project Name, Task Name, or Issue Name columns to a document or hour report.
• The Project Name or Task Name columns to an issue report.

For more information, see Run and deliver a report with the access rights of another user

The Date when the work on an item is set to start. There are several Start Dates in Workfront:

• Planned
• Actual
• Projected

In a Rate report, this is the date when a new billing rate for a job role at the project level starts. The hours associated with the project that are after this date are multiplied by this billing rate to calculate the revenue on the project.

An indicator used to signal a workflow position of a work item or of a strategic goal.

For projects, the Status is a setting on the project that indicates whether the project is:

• Current
• On Hold
• Complete
• Dead

For more information on a project's Status, see Access the list of system project statuses.

For tasks, the Status is a setting on the task that indicates whether the task is:

• New
• In Progress
• Complete

For more information on task Status, see Access the list of system task statuses

For issues, the Status is a setting on the issue that indicates whether this issue is:

• New
• In Progress
• Awaiting Feedback
• On Hold
• Resolved
• Won't Resolve
• Cannot Duplicate
• Verified Complete
• Reopened

For more information on issue Statuses, see Access the list of system issue statuses.

For strategic goals, the Status is a setting on the goal that indicates whether the goal is:

• Active
• Draft
• Inactive
• Closed

For more information about strategic goals, also see "Goal" or "Goals" in this article.

For strategic goals, this field is visible only if your organization has purchased Workfront Goals. For information about managing strategic goals using Workfront Goals, see Workfront Goals overview.

You can add the built-in Status Icons field as a column in your views to enhance visibility into key points about your objects, like:

• An object has documents attached
• An object is associated with an approval process
• An object has additional notes associated with it
• An expense is billable or reimbursable
• A task is on a critical path
• A user belongs to a company, a team, or is located in a different time zone

You can add the Status Icons field in the views of the following objects:

• Tasks
• Issues
• Projects
• Template Tasks
• Templates
• Expenses
• Documents
• Users

For more information, see Built-in Status Icons in Views.

In a project, task, or issue report, this field shows the most recent status update that object owners have provided in the 'Updates' area. For projects, this means that comments made by the Project Owner, and for tasks and issues, this means that comments made by the assignees.

Comments made when updating the status of an object do not display in the Status Update column.

To show the 'New,' 'In Process,' and 'Complete' statuses, use the Status column.

For more information on statuses, see the article Update task status.

This is used in report columns when using the Text Mode interface.

The stretch is used to identify which columns occupy extra space not needed by the view. The user interface width of the workspace for a typical user is about 850 pixels. This means that if you have a view with four columns (150 pixels each) that your view occupies 600 of 850 pixels. There are 250 extra pixels in the UI that will be added to the columns that have a stretch percentage provided.

The stretch of a column is enforced when you use the additional line of code: usewidths=true for at least one of the columns in the view.

Users that subscribe to projects, tasks, or issues.

When you use this field in a report, a list of subscribers displays, with each subscriber separated by a comma.

For more information, see the article Subscribe to items in ÃÛ¶¹ÊÓƵ Workfront.

An activity that must be performed as a step toward achieving a final goal (completing the Project).

For more information, see Tasks overview.

A collection of users working toward similar goals or business objectives. These users can be collectively assigned to a work item by assigning the team to the work item.

For more information on Teams, see Teams overview.

Projects can have a Project Team, which contains all the users or roles associated with the work on the project.

For more information about Project Teams, see Project Team overview

Project templates are generic outlines of your most repeatable projects. You can define tasks, queue topics, custom forms, attach documents or approvals when you create a project template to save you time when you must create a new project.

You can attach templates to existing projects, or you can use them to build new projects. All the information specified on the template transfers to the projects that are created using it.

For more information about templates, see Project template overview.

In a Document list or report, it displays a preview of the document in a thumbnail.

Select Thumbnail  to view a 33-66 pixel-wide thumbnail in the report.

The size of the thumbnail adjusts when you modify the width of the column in a list or report.

See also "Large Thumbnail" in this article.

A Timesheet Profile is a template that Workfront uses to automatically create timesheets for the users associated with them.

You can configure a number of settings that will apply to each timesheet as it is created. Some of these settings are: how often the timesheet should be created (weekly, every other week, twice a month, or monthly), the start day of the timesheet, the timesheet approvers, the available Hour Types that users can associate with recorded hours.

This field allows you to identify data about a top-level group and its subgroups in a View for a list or report.

You can also do this using the Top Parent ID field.

In a project report, this field displays the rounded sum of all hours on the project, the last time the project finances were calculated. Actual Hours reflect the exact hours logged on the project. Typically, the Actual Hours should match the Total Hours. If the Total Hours appears significantly different from the Actual Hours field, you must Recalculate Finances on the project.

For more information about recalculating project finances, see the article Recalculate project finances.

In a timesheet Standard view, this field refers to the total hours logged for items for the dates displayed on a timesheet. The Total Hours field for timesheets in this built-in view references the "hoursDuration" field which dynamically calculates the difference in hours between the timesheet Start and End dates. This is used to display the Total Hours column in red if the user logs more time than the available hours in the timesheet's time frame. For more information, see View total hours on the timesheet.

An attribute of a task. This determines how and when the Projected timelines will be updated for a task. For example:

• User Must Update requires that a task be updated manually. Otherwise, it will become Behind Schedule, then Late.
• Auto Complete will automatically complete a task when the Due Date, or Planned Completion Date, has passed.

For more information, see Task Tracking Mode overview.

A setting on a project that determines when the project's Projected timeline will be recalculated. The Update Type can have the following values:

• Automatic and On Change
• Automatic Only
• Manual Only

For more information, see Select the project Update Type.

A reportable object that tells you:

• Which users have delegated task, issue, and project approvals
• Which users have had task, issue, and project approvals delegated to them
• When these delegations start and end

To learn more, see Create a User Delegation report.

Views refer to a reporting element which allows you to modify the columns in a report or in a list of objects.

View also refers to a user's right to only view information on an object, according to their access level or at a permissions sharing level on that object.

In Workfront Planning, records display on the record type page in one of the following view types:

• Table
• Timeline
• Calendar

In Workfront Planning, views include the filters, groupings, sorting, and other settings applied to the records on the screen.

For information, see Manage record views.

Workfront Planning requires an additional license.

This is the same field as Status Icons, but it is only available for the following views:

• Documents

For more information, see the article Built-in Status Icons in Views.

In a project, task, or issue report, using the following statement in text mode displays the Planned Hours of the project, task, or issue:

``

valuefield=work

valueformat=HTML

For information about using text mode, see Text mode syntax overview.

TIP

In an issue report, adding one of the Planned Hours fields adds the work field to the report.

One of the two primary License Types. This has less access than Plan, but can create and make updates in the system. A user with a Work license has more abilities than an External, Reviewer, or Requester license holder.

For more information, see ÃÛ¶¹ÊÓƵ Workfront licenses overview.

Work might refer to the number of Planned Hours for a project, task, or issue. For more information, see the "work" field in this table.

TIP

In an issue report, adding one of the Planned Hours fields adds the work field to the report.

A project manager might decide to use this field instead of Planned Hours to estimate the effort needed to complete a task. This field is visible only when the following conditions are met:

• The task has a Simple Duration Type.

  TIP

  If you update the task Duration Type to any other type, this field becomes hidden.

• The project manager has enabled the Use Work Effort to automatically calculate task Planned Hours field on the project.

For information about using Work Effort instead of Planned Hours to estimate task effort, see Work Effort overview.

You can display this field in task reports and lists.

This field refers to either tasks or issues in Workfront.

The Work Item report displays information for both tasks and issues.

Mix ratio, capacity, velocity, quality, and engagement.

WPI is a common acronym for Work Performance Indicator.

The method in which work is received, prioritized, and executed. The way you execute the work is typically called "the workflow" or "project plan" (a list of tasks with dates, predecessor relationships, and so forth).

Examples of a work process might be the production of a single asset or the delivery of a multi-asset campaign.

Represents the percentage of the Full Time Equivalent (FTE) time that the user is available for actual work, not including overhead. Work Time must be a decimal number up to 1, and it cannot be 0. For example, a 20% availability for actual work would be 0.2.

The field's default is 1, indicating that a user spends their entire FTE on actual, project-related work.

The system uses this number to calculate the availability of the user for actual, project-related work.

Schedule exceptions and time off might also affect the user capacity.

For more information about creating schedules in Workfront, see Create a schedule.

Workfront calculates a user's availability depending on the Resource Management preferences in the Setup area. For more information, see Configure Resource Management preferences.

You can update the Work Time of a user when you edit or create the user. For information, see Edit a user's profile

TIP

Set the Work Time value to 1 to indicate that the user is available for project-related work their entire full-time equivalent.

In a project, task, or issue report, using the following statement in text mode displays the number of Planned Hours of the project, task, or issue followed by the word "Hours":

``

valuefield=workRequiredExpression

valueformat=HTML

For information about using text mode, see Text mode syntax overview.

In Workfront Planning, a workspace is a collection of record types that define the operational lifecycle of a certain organization. A workspace is the work frame of an organizational unit.

Workfront Planning requires an additional license.

For information, see Create workspaces.