ReportableBudgedHour has been added to the Adobe Workfront API as a resource for Reporting. It features reference fields, core fields, and default fields that are absent in BudgetedHour.
Direct Fields |
|
Reference Fields |
|
Core Fields |
|
Default Fields |
|
Operations |
|
No resources were removed for API v11.
An AccessLevelPermissions object represents a set of permissions. This set of permissions can then be associated with an Access Level.
Direct Fields | The following fields added the possible value BUDGETING_INFORMATION. This allows users with permission to edit priorities and budget hours in the planner.
|
If a User does not have access to an object in Workfront that they need, they can request access to that object. The AccessRequest object represents this request.
Direct Fields |
|
An AccessRule object represents a rule set in custom access levels that determines how users can share projects they create.
Direct Fields | The following fields added the possible value BUDGETING_INFORMATION. This allows users with permission to edit priorities and budget hours in the planner.
|
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. An Approval object represents the action of signing off on a work item.
Direct Fields The following fields added the validators AT_DATE_BEFORE_YEAR and AT_DATE_AFTER_YEAR. These validators specify that dates on associated objects can't be set before the year 1900 or after 2200.
The following fields were added to the public API for transparency in calculating EAC (Estimate at Completion).
The following fields added the possible value ET. This value represents the unit of time Elapsed Months, which refers to months without regard to weekends or holidays.
The following fields added the flag CURRENCY
The following fields were removed from the Approval object.
The following field was added to the Approval object.
|
|
Reference Fields |
|
Collection Fields |
|
An ApprovalPath object is a branch within an Approval Process. Approval Paths are based on the status of the object that the Approval Process is associated with.
Direct Fields |
|
An ApprovalProcess object is a multi-step Approval that can be associated with a Project, Task, or Issue.
Direct Fields |
|
Default Fields |
|
An assignment object represents the connection between a work item and the user, team, or group that is assigned to work on it.
Direct Fields |
|
Baselines are snapshots of what the performance of a project looked like at a given moment in time. They store key pieces of information about the project, like key dates, progress, cost and revenue values. When you create a baseline, the task information is also captured on the baseline tasks of that baseline.
Direct Fields |
|
A Category object is a custom form. You can build reports for this object and you can show it in other object reports, as well.
Direct Fields |
|
Default Fields |
|
A Company object represents an organization consisting of a collection of people. Companies are associated with a user or a project.
Direct Fields |
|
Default Fields |
|
Actions | The following actions were added to the CustomEnum object
|
Queries | The following queries were added to the CustomEnum object
|
A Customer object represents an organization that uses an instance of Workfront.
Direct Fields |
|
Actions | The following actions were added to the Customer object
|
A CustomerPreferences object represents the set of preferences that a customer has set for their instance of Workfront.
name
Added possible values:
Actions |
|
A Document object represents a file (such as written material, images, or other forms of information).
Actions | The following actions were added to the Document object.
|
An Iteration object represents a single Agile Iteration. Iterations are discrete periods of time used to plan and complete Agile stories.
Direct Fields | The following fields were added to the Iteration object.
|
A Layout Template object represents a particular arrangement of layout elements, such as the main menu, navigation panel, or the Home area. Layout templates can be assigned to users, teams, groups, or job roles.
Direct Fields |
|
Default Fields |
|
A milestone is a marker on a task indication that it is a key point in the Project. Generally used to denote a significant event such as the completion of a phase of the project or a set of critical activities. A MilestonePath object is a collection of milestones.
Direct Fields |
|
Default Fields |
|
A Note object is a comment or update made on a Workfront object.
Direct Fields | The following fields were added to the Note object.
|
Collection Fields |
|
An OpTask object is commonly known as an Issue. An issue is a work item that usually indicates that there is a problem preventing the completion of a task or project. An Issue can also be a Help Desk request. Change Orders, Requests, and Bugs are also Issues.
Direct Fields The following fields added the validators AT_DATE_BEFORE_YEAR and AT_DATE_AFTER_YEAR. These valdators specify that dates on associated objects can't be set before the year 1900 or after 2200.
The following fields were added to OpTask.
|
|
Collection Fields |
|
Search Fields |
|
Default Fields |
|
Actions | The following actions were added to the OpTask object
|
A Parameter object is a custom field.
Direct Fields |
|
A Portfolio object is a collection of projects that compete for the same resources, typically money or people to complete them.
Direct Fields |
|
A Program object is a subset within a portfolio, where similar projects can be grouped together.
Direct Fields |
|
Default Fields |
|
Projects are work items within Workfront, and are a main building block in the way Workfront helps people to do work. A Project object represents a group of tasks with a common, specific goal.
Direct Fields The following fields added the validators AT_DATE_BEFORE_YEAR and AT_DATE_AFTER_YEAR. These valdators specify that dates on associated objects can't be set before the year 1900 or after 2200.
The following fields were added to the public API for transparency in calculating EAC (Estimate at Completion).
The following fields added the flag CURRENCY
The following field was removed from the Project object.
|
|
Collection Fields |
|
A ProofApproval object represents an approval that is directly connected to a proof.
Direct Fields |
|
A QueueDef object represents a Queue, which is a Project that has been published to the Help Desk area to allow users to submit Issues to it.
Direct Fields | The following fields added the possible value BUDGETING_INFORMATION. This allows users with permission to edit priorities and budget hours in the planner.
|
A ReservedTime object represents days specified on a User’s Personal Time, indicating that the User will not be available for work.
The ReservedTime resource added the flag REPORTABLE.
Direct Fields | The following fields removed the flag NOT_GROUPABLE.
The following field was removed from the ReservedTime object.
|
Reference Fields |
|
Operations |
|
A ResourcePlannerFilter object is a set of rules that determine which items will display in the Resource Planner.
The ResourcePlannerFilter resource added the flag SHARABLE. There were no other changes to the object.
A Risk object represents a possible event that may prevent a project from finishing on time or within budget. Risks are added to projects in the planning phase to identify potential obstacles prior to the approval of any work.
Direct Fields | The following fields were added to the Risk object:
|
Reference Fields | The following Reference Fields were added to the RIsk object.
|
A ScheduledReport object represents a report that has been configured to be scheduled for delivery.
Direct Fields |
|
A ScoreCardQuestion object represents a question that has been added to a Scorecard. These questions are usually determined by the Portfolio manager, and their answers allow the manager to understand how well a project aligns with the goals of the portfolio.
Direct Fields |
|
A Task object represents a work item that must be performed as a step toward achieving a final goal (completing a Project).
Direct Fields The following fields added the validators AT_DATE_BEFORE_YEAR and AT_DATE_AFTER_YEAR. These valdators specify that dates on associated objects can't be set before the year 1900 or after 2200.
The following fields were added to the public API for transparency in calculating EAC (Estimate at Completion).
The following fields added the possible value ET. This value represents the unit of time Elapsed Months, which refers to months without regard to weekends or holidays.
The following field was removed from the Task object.
The following field was added to the Task object.
|
|
Reference Fields |
|
Collection Fields |
|
A Team object is a collection of Users that can be assigned to a work item.
Direct Fields |
|
A Template object represents a pattern for a Project. Projects can be created from Templates to save time. A Template contains a Team and Tasks, which will be copied to a Project when the Template is used.
Direct Fields |
|
Collection Fields |
|
Default Fields |
|
Direct Fields |
|
A TemplateTask object represents a Task that is part of a Template. Template Tasks become Tasks in the Project where the Template is used.
Direct Fields | The following fields added the possible value ET. This value represents the unit of time Elapsed Months, which refers to months without regard to weekends or holidays.
|
Collection Fields |
|
A Timesheet object represents a virtual timecard that allows Users to enter actual hours worked for Tasks, Projects, and overhead Hour Types.
Core Fields |
|
Work Items in Workfront can be updated to keep users informed of the current status. An Update object represents one of these updates. Updates can be entered by users or created by the Workfront system.
Direct Fields |
|
Queries | The following queries were added to the Update object.
|
loginAsAccessRules
Added
The following actions were added to the User object.
userAdmins
Added
Actions | The following actions were added to the User object.
|
Queries |
|
A Work object is a common interface that both Task and OpTask inherit, and shares common code between the two.
Direct Fields The following fields added the validators AT_DATE_BEFORE_YEAR and AT_DATE_AFTER_YEAR. These valdators specify that dates on associated objects can't be set before the year 1900 or after 2200.
The following fields were added to the public API for transparency in calculating EAC (Estimate at Completion).
The following fields added the possible value ET. This value represents the unit of time Elapsed Months, which refers to months without regard to weekends or holidays.
The following field was removed from the Work object.
The following field was added to the Work object.
|
|
Reference Fields |
|
Collection Fields |
|