View all Work Packages by Project

get

/api/restapi/workPackage/project/{projectId}

This endpoint returns work packages that meet the following requirements:
  • The object is associated with a project with an ID value that matches the value of the {projectId} path parameter.

Request

Path Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : List<ApiEntityWorkPackage>
Type: array
Title: List<ApiEntityWorkPackage>
Show Source
Nested Schema : ApiEntityWorkPackage
Type: object
Title: ApiEntityWorkPackage
Show Source
  • Minimum Value: 0
    The percentage complete for all activities assigned to the work package.
  • Allowed Values: [ "DURATION", "LABOR_UNITS", "NON_LABOR_UNITS", "MANUAL" ]
    The method used to calculate Activity Percent Complete. Methods are Duration, Labor Units, Non Labor Units, and Manual.
    Duration: Planned Duration, also known as Original Duration, is used for Weight.
    Labor Units: At Completion Labor Units is used for Weight.
    Non Labor Units: At Completion NonLabor Units is used for Weight.
    Manual: Weight is added manually.
  • Minimum Value: 0
    The actual hours spent on the scope assignment. This tracks the VOWD (Value of Work Done).
    This is the cumulative value for all scope assignments in the work package.
  • The sum of all approved change hours in the change and transfer records for the scope assignment.
    This is the cumulative value for all scope assignments in the work package.
  • Minimum Value: 0
    The total hours expected to be spend at the completion of the scope assignment.
    Calculated as Revised Hours plus Adjusted Hours.
    This is the cumulative value for all scope assignments in the work package.
  • Minimum Value: 0
    The Revised Hours or At Completion Hours at the time the current baseline was set, depending on the selection for the Budget At Completion Method. The Revised Hours of the current project if no baseline is set.
    This is the cumulative value for all scope assignments in the work package.
  • The planned finish date for the work package as is set in the current baseline.
    This field is populated with the Revised Finish date at the time that the current baseline is set.
  • Minimum Value: 0
    The Revised Hours at the time the baseline was set.
    This is the cumulative value for all scope assignments in the work package.
  • The planned start date for the work package as is set in the current baseline.
    This field is populated with the Revised Start date at the time that the current baseline is set.
  • Allowed Values: [ "REVISED", "AT_COMPLETION" ]
    The setting allows users to select which value to use for populating BAC fields when a baseline is set. Choose At Completion to include adjusted values.
  • codeValues
    The list of code values for a work package. This entity can only be used to assign codeValues or create codeValues on the fly.
  • configuredFields
    The list of configured fields for a work package.
  • The curve profile used for time phase distribution of scope assignments.
  • Minimum Length: 0
    Maximum Length: 4000
    Provides additional details about the work package.
  • Minimum Value: 0
    The total hours estimated to be earned at the completion of the work package.
    Calculated as ETC Hours plus Actual Hours to Date.
    This is the cumulative value for all scope assignments in the work package.
  • Calculated as ETC Hours plus Spends Hours for all scope assignments in the work package.
  • Minimum Value: 0
    The portion of budgeted hours that is currently earned for the work package.
    Calculated as Performance Percent Complete multiplied by BAC Hours.
    This is the cumulative value for all scope assignments in the work package.
  • Minimum Value: 0
    Calculated as Earned Hours divided by BAC Hours for all scope assignments in the work package.
  • The latest Effective Finish date of all scope assignments in the work package.
    This is a read-only field.
  • The earliest Effective Start date of all scope assignments in the work package.
    This is a read-only field.
  • Minimum Value: 0
    The amount of scope assignment work that is not yet accounted for. For example, you might enter a value to represent pending change requests that are likely to be approved.
    This is the cumulative value for all scope assignments in the work package.
  • Minimum Value: 0
    The estimated number of hours needed to complete the work.
    Calculated as BAC Hours minus Earned Hours.
    This is the cumulative value for all scope assignments in the work package.
  • The date work on the work package is complete.
    This is the latest Installed Finish date of all scope assignments in the work package.
  • Minimum Value: 0
    Hours spent on the scope assignment.
    Calculated as Installed Quantity multiplied by Revised Productivity Rate.
    This is the cumulative value for all scope assignments in the work package.
  • The date work on the work package began.
    This is the earliest Installed Start date of all scope assignments in the work package.
  • Installed quantity of scope assignments in the work package.
  • The manager or person responsible for the work package.
  • Allowed Values: [ "SEQUENTIAL", "NON_SEQUENTIAL" ]
    Determines how the milestones are progressed if the Progress Measure is set to Milestone Percent Complete.
    Sequential: Milestones must be progressed in order.
    Non Sequential: Milestones can be progressed in whatever order necessary.
  • The date the work on the work package is scheduled to finish.
    This field is populated with the Data Date plus 4 days when the work package is created, but it can be manually modified until the Original Baseline is set.
    If the Data Date is specified after the Original Finish date is set and the Original Start date is before the Data Date, the application sets the Original Finish date to be the same date relative to Original Start before the Data Date was modified when the Modify Dates feature is run.
    If there is no activity link, the field is locked when the original baseline is set.
    If there is an activity link, before the original baseline is set the field is populated with the earliest Planned Finish date of all linked activities. After the baseline is set, the field is locked.
  • The date the work on the work package is scheduled to begin.
    This field is populated with the Data Date with the work package is created, but it can be manually modified until the Original Baseline is set.
    If the Data Date is specified, Original Start cannot be set to a date earlier than the Data Date. If the Data Date is specified after the Original Start date is set and the Original Start date is before the Data Date, the Original Start is populated with the Data Date when the Modify Dates feature is run.
    If there is no activity link, this field is locked when the original baseline is set.
    If there is an activity link, before the original baseline is set this field is populated with the earliest Planned Start dates of all linked activities. After the baseline is set, the field is locked.
  • Calculated as the sum of all pending hour changes in the change and transfer records for the scope assignment.
    This is the cumulative value for all scope assignments in the work package.
  • The weight is calculated using cost, quantity, hours, or manually entered values. Cost, Quantity, and Hours are represented as n in the equations that follow.
    The n weight is first calculated for each scope assignment in the work package as Revised n multiplied by the scope assignment Scope Percent Complete.
    Scope Percent Complete is calculated as Installed Quantity divided by At Completion Quantity.
    The sum of the scope assignments Revised n and the sum of the scope assignments n Weight for all scope assignments in the work package are then used to compute the work package Scope Percent Complete. This is calculated as the n Weight divided by Revised n.
    Weight for the Manual option is calculated as Manual Weight Factor multiplied by Scope Percent Complete.
    Scope Percent Complete at the work package level for the manual option is calculated as the sum of Manual Weight divided by the sum of Manual Weight Factors for all scope assignments in the work package.
  • Allowed Values: [ "MILESTONE_PERCENT_COMPLETE", "PHYSICAL_PERCENT_COMPLETE" ]
    The method used to measure progress.
    Milestone Percent Complete: This option uses a selected Rule of Credit to measure progress.
    Physical Percent Complete: This option allows users to manually enter Installed Quantity for scope assignments.
  • Allowed Values: [ "COST", "QUANTITY", "HOURS", "MANUAL" ]
    The weight is calculated using cost, quantity, hours, or manually entered values. Cost, Quantity, and Hours are represented as n in the equations that follow.
    The n weight is first calculated for each scope assignment in the work package as Revised n multiplied by the scope assignment Scope Percent Complete.
    Scope Percent Complete is calculated as Installed Quantity divided by At Completion Quantity.
    The sum of the scope assignments Revised n and the sum of the scope assignments n Weight for all scope assignments in the work package are then used to compute the work package Scope Percent Complete. This is calculated as the n Weight divided by Revised n.
    Completed Weight for the Manual option is calculated as Manual Weight multiplied by Scope Percent Complete.
    Scope Percent Complete at the work package level for the manual option is calculated as the sum of Manual Completed Weight divided by the sum of Manual Weight for all scope assignments in the work package.
  • The date the work on the work package is scheduled to finish.
    If there is no activity link, this field is populated with the Original Finish date until the original baseline is set. It can be manually modified after the original baseline is set.
    If Data Date is specified after the Planned Finish date is set and the Planned Start date is before the Data Date, the application sets the Planned Finish date to be the same date relative to Planned Start before the Data Date was modified when the Modify Dates feature is run.
    If there is an activity link, this field is populated with the latest Planned Finish date of all activities in the work package.
  • Minimum Value: 0
    The original expected hours needed to complete all the work required to install the material quantity on the scope assignment.
    Calculated as Original Quantity multiplied by Original Productivity Rate.
    Before the baseline is set, this field can be entered manually. A manual entry recalculates the Original Productivity Rate to equal Original Hours divided by Original Quantity.
    This is the cumulative value for all scope assignments in the work package.
  • The date the work on the work package is scheduled to begin.
    If there is no activity link, this field is populated with the Original Start date until the original baseline is set. It can be manually updated after the original baseline is set.
    If the Data Date is specified, the date cannot be set to a date earlier than the Data Date.
    If the Data Date is specified after the Planned Start date is set, the Planned Start date is before the Data Date, and the work package's Scope Percent Complete is equal to 0%, that is Installed Quantity is zero, then the date inherits the Data Date when the Modify Dates feature is run.
    If there is an activity link, this field is populated with the earliest Planned Start date of all the activities in the work package.
  • Minimum Length: 1
    Maximum Length: 60
    The user-specified unique identifier of the project.
  • The unique identifier for the project.The project object can also be identified by its unique criteria.
  • The earliest date the work on the work package is scheduled to finish.
    If there is no activity link, this field is populated with the latest Remaining Early Finish date of all its scope assignments. If the work package does not have scope assignments, the field is populated the Original Finish date before the original baseline is set and the Revised Finish date after the original baseline is set.
    This field is blank when the scope assignment's Scope Percent Complete becomes 100%.
    If there is an activity linked, this field is populated with the latest Remaining Early Finish date of all linked activities.
  • The earliest date the work on the work package is scheduled to begin.
    If the work package does not have scope assignments, before the original baseline is set, this field is populated with the Original Start date. After the original baseline is set, it inherits the Data Date when the Modify Dates feature is run if the work package's Scope Percent Complete is not equal to 100%.
    This field is blank when the scope assignment's Scope Percent Complete becomes 100%.
    If there is any activity linked, this field is populated with the earliest Remaining Early Start date of all linked activities.
  • Minimum Value: 0
    The number of hours left for the scope assignment.
    Calculated as Remaining Quantity multiplied by Revised Productivity Rate.
    This is the cumulative value for all scope assignments in the work package.
  • The latest possible date work on the work package must finish to not delay the finish date.
    If there is no activity link, this field is populated with the latest Remaining Late Finish date of all its scope assignments. If the work package does not have scope assignments, the field is populated with the Remaining Early Finish date.
    If there is an activity linked, this field is populated with the latest Remaining Late Finish date of all linked activities.
  • The latest possible date work on the work package must begin without delaying the finish date.
    If there is no activity link, this field is always equal to the Remaining Late Start date of all scope assignments in the work package. If the work package does not have scope assignments, this field is populated with the Remaining Early Start date.
    If there is any activity linked, this field is populated with the earliest Remaining Late Start date of all activities.
  • The revised finish date for the work package.
    If the work package does not have scope assignments, this field is populated with the Original Finish date until the original baseline is set.
    When the Modify Dates feature is run after the original baseline is set, the Revised Start date is before the Data Date, and the work package's Scope Percent Complete is equal to 0%, the Revised Finish date is updated to be the same date relative to the Revised Start date as it was before the Data Date was modified.
    If the work package has scope assignments, the date is always the latest finish of its scope assignments' Planned Finish dates and all approved Change Finish dates.
  • Minimum Value: 0
    Original Hours before the baseline is set. After the baseline is set, Revised Hours is equal to Original Hours plus Approved Change Hours.
    This is the cumulative value for all scope assignments in the work package.
  • The revised start date for the work package.
    If the work package does not have scope assignments, this field is populated with the Original Start date until the original baseline is set.
    This field is populated with the Data Date when the Modify Dates feature is run after the original baseline is set if the Revised Start date is before the Data Date and the work package's Scope Percent Complete is equal to 0%.
    If the work package has scope assignments, is always the earliest start of its scope assignments' Planned Start dates and all approved Change Start dates.
  • ruleOfCredit
    The name of the rule of credit which includes a set of milestones for which progress is measured.
  • Minimum Value: 0
    Calculated as the sum of Actual Hours to Date for all scope assignments in the work package.
  • Allowed Values: [ "PENDING", "APPROVED", "REJECTED", "WITHDRAW_APPROVAL", "REOPEN" ]
    The status of the work package.
  • Date when the record was last updated.
  • wbsCodes
    Deprecated. As of 23.12.
    The list of WBS codes in a hierarchy of a work package.
  • The unique identifier for the wbs.The wbs object can also be identified by its unique criteria.
  • Minimum Length: 1
    Maximum Length: 60
    The unique identifier for the work package.
  • workPackageCost
    The cost of the work package.
  • The ID for the work package.
  • Minimum Length: 1
    Maximum Length: 255
    The name of the work package.
  • Minimum Length: 0
    Maximum Length: 60
    The user-specified unique identifier of the workspace.
Nested Schema : codeValues
Type: array
The list of code values for a work package. This entity can only be used to assign codeValues or create codeValues on the fly.
Show Source
Nested Schema : configuredFields
Type: array
The list of configured fields for a work package.
Show Source
Nested Schema : ruleOfCredit
The name of the rule of credit which includes a set of milestones for which progress is measured.
Match All
Show Source
Nested Schema : wbsCodes
Type: array
Deprecated. As of 23.12.
The list of WBS codes in a hierarchy of a work package.
Show Source
Nested Schema : workPackageCost
The cost of the work package.
Match All
Show Source
Nested Schema : ApiEntityCodeValueWorkPackage
Type: object
Title: ApiEntityCodeValueWorkPackage
Show Source
Nested Schema : ApiEntityWorkPackageConfiguredFieldValue
Type: object
Title: ApiEntityWorkPackageConfiguredFieldValue
Show Source
Nested Schema : ApiEntityRuleOfCredit
Type: object
Title: ApiEntityRuleOfCredit
Show Source
  • Allowed Values: [ "OWNED", "INHERITED" ]
    The type of association in the relationship between the rule of credit and the workspace. Possible values are Owned and Inherited.
  • milestones
    The milestones associated with the rule of credit.
  • Allowed Values: [ "MANUAL", "AUTOMATIC" ]
    The push down type of the rule of credit.
  • Unique identifier of the rule of credit.
  • Minimum Length: 1
    Maximum Length: 255
    The name of the rule of credit.
  • Allowed Values: [ "MANUAL", "ZERO_TO_ONE_HUNDRED" ]
    Determines how each milestone in a rule of credit can be progressed.
    Manual: Allows partial completion of a milestone, entered as a percentage.
    0/100%: Partial progress cannot be made when progressing a milestone. As soon as the milestone is selected, the milestone is 100% complete.
  • Date when the record was last updated.
  • Minimum Length: 0
    Maximum Length: 60
    The user-specified identifier of a workspace.
  • The unique identifier for the workspace.The workspace object can also be identified by its unique criteria.
Nested Schema : milestones
Type: array
The milestones associated with the rule of credit.
Show Source
Nested Schema : ApiEntityRuleOfCreditMilestone
Type: object
Title: ApiEntityRuleOfCreditMilestone
Show Source
Nested Schema : ApiEntityWorkPackageCost
Type: object
Title: ApiEntityWorkPackageCost
Show Source
  • The actual costs incurred on the scope assignment. This tracks the VOWD (Value of Work Done).
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from actualCostToDateProject field based on the specified exchange rate.
  • The actual costs incurred on the scope assignment. This tracks the VOWD (Value of Work Done).
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • The amount the scope assignment work that is not yet accounted for. For example, you might enter a value to represent pending change requests that are likely to be approved.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from adjustedCostProject field based on the specified exchange rate.
  • The amount the scope assignment work that is not yet accounted for. For example, you might enter a value to represent pending change requests that are likely to be approved.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • The sum of all approved cost changes in the change records for the scope assignment.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from approvedChangedCostProject field based on the specified exchange rate.
  • The sum of all approved cost changes in the change records for the scope assignment.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • The total cost at the completion of the scope assignment.
    Calculated as Revised Cost plus Adjusted Cost.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from atCompletionCostProject field based on the specified exchange rate.
  • The total cost at the completion of the scope assignment.
    Calculated as Revised Cost plus Adjusted Cost.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • The Revised Cost or At Completion Cost at the time the current baseline was set, depending on the selection for the Budget at Completion Method. The Revised Cost of the current project if no baseline is set.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from bacCostProject field based on the specified exchange rate.
  • The Revised Cost or At Completion Cost at the time the current baseline was set, depending on the selection for the Budget at Completion Method. The Revised Cost of the current project if no baseline is set.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • The Revised Cost at the time the current baseline was set.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from baselineCostProject field based on the specified exchange rate.
  • The Revised Cost at the time the current baseline was set.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • The total cost estimated to be earned as the completion of the work package.
    Calculated as ETC Cost plus Actual Cost to Date.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from eacCostProject field based on the specified exchange rate.
  • The total cost estimated to be earned as the completion of the work package.
    Calculated as ETC Cost plus Actual Cost to Date.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • Calculated as ETC Cost plus Spends Cost for all scope assignments in the work package. This field is in base currency and is calculated from eacWithSpendsCostProject field based on the specified exchange rate.
  • Calculated as ETC cost plus spends cost for all scope assignments in the work package. This value is based on the project currency.
  • The portion of the budgeted cost that is currently earned for the work package.
    Calculated as Performance Percent Complete multiplied by BAC Cost.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from earnedCostProject field based on the specified exchange rate.
  • The portion of the budgeted cost that is currently earned for the work package.
    Calculated as Performance Percent Complete multiplied by BAC Cost.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • The estimate of the cost needed to complete the work.
    Calculated as BAC Cost minus Earned Cost.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from etcCostProject field based on the specified exchange rate.
  • The estimate of the cost needed to complete the work.
    Calculated as BAC Cost minus Earned Cost.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • The total cost incurred on the scope assignment as of the current date.
    If Rate By is set to Hours, then Installed Cost equals Revised Cost Rate multiplied by Installed Hours.
    If Rate By is set to Quantity, then Installed Cost equals Revised Cost Rate multiplied by Installed Quantity.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from installedCostProject field based on the specified exchange rate.
  • The total cost incurred on the scope assignment as of the current date.
    If Rate By is set to Hours, then Installed Cost equals Revised Cost Rate multiplied by Installed Hours.
    If Rate By is set to Quantity, then Installed Cost equals Revised Cost Rate multiplied by Installed Quantity.
    This is the cumulative value for all scope assignments in the work package. of a project. This value is based on the project currency.
  • Calculated as the sum of all pending cost changes in the change records for the scope assignment.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from pendingChangedCostProject field based on the specified exchange rate.
  • Calculated as the sum of all pending cost changes in the change records for the scope assignment.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • The original cost of the scope assignment.
    If Rate By is set to Hours, then Original Cost equals Original Hours multiplied by Original Cost Rate. If this value is entered manually, then Original Cost Rate is recalculated to equal Original Cost divided by Original Hours.
    If Rate By is set to Quantity, then Original Cost equals Original Quantity multiplied by Original Cost Rate. If this value is entered manually, then Original Cost Rate is recalculated to equal Original Cost divided by Original Quantity.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from plannedCostProject field based on the specified exchange rate.
  • The original cost of the scope assignment.
    If Rate By is set to Hours, then Original Cost equals Original Hours multiplied by Original Cost Rate. If this value is entered manually, then Original Cost Rate is recalculated to equal Original Cost divided by Original Hours.
    If Rate By is set to Quantity, then Original Cost equals Original Quantity multiplied by Original Cost Rate. If this value is entered manually, then Original Cost Rate is recalculated to equal Original Cost divided by Original Quantity.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • The amount left to be spent.
    If Rate By set to Hours, then Remaining Cost equals Remaining Hours multiplied by Revised Cost Rate.
    If Rate By set to Quantity, then Remaining Cost equals Remaining Quantity multiplied by Revised Cost Rate.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from remainingCostProject field based on the specified exchange rate.
  • The amount left to be spent.
    If Rate By set to Hours, then Remaining Cost equals Remaining Hours multiplied by Revised Cost Rate.
    If Rate By set to Quantity, then Remaining Cost equals Remaining Quantity multiplied by Revised Cost Rate.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • The Original Cost before the baseline is set. After the baseline is set, Revised Cost equals Original Cost plus Approved Change Cost.
    This is the cumulative value for all scope assignments in the work package. This field is in base currency and is calculated from revisedCostProject field based on the specified exchange rate.
  • The Original Cost before the baseline is set. After the baseline is set, Revised Cost equals Original Cost plus Approved Change Cost.
    This is the cumulative value for all scope assignments in the work package of a project. This value is based on the project currency.
  • Calculated as the sum of Actual Cost to Date for all scope assignments in the work package. This field is in base currency and is calculated from spendsCostProject field based on the specified exchange rate.
  • Calculated as the sum of actual cost to date for all scope assignments in the work package. This value is based on the project currency.
  • Date when the record was last updated.
  • The ID for the work package.

204 Response

Successful operation with no content.

404 Response

The requested work package does not exist, or you do not have access to it.
Back to Top