1. Oracle Primavera Cloud REST API
  2. Tasks
  3. Activity

View an Activity by Code and Parent Codes

get

/api/restapi/activity/byItemCode

Send a request to this endpoint to view an activity with codes matching the code fields in query parameters.

Request

Query Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : ApiEntityActivity
Type: object
Title: ApiEntityActivity
Show Source
  • The difference between the planned value of work scheduled and the actual work performed.
  • Minimum Length: 0
    Maximum Length: 60
    The user-specified identifier of the activity.
  • activityFinancial
    An object containing the financial fields of an activity in the form of key-value pairs.
  • The unique identifier for the activity.
  • Minimum Length: 1
    Maximum Length: 255
    The name of the activity.
  • The percentage of the activity that has been completed.
    This value is based on the formula for the selected Percent Complete Type. The Percent Complete Type can be Physical, Duration, Units, or Scope.
    Physical: The user records the percent complete manually.
    Duration: Calculated as (Planned Duration minus Remaining Duration) divided by Planned Duration, multiplied by 100.
    Units: Calculated as (Actual Labor Units plus Actual Nonlabor Units) divided by (Actual Labor Units plus Actual Nonlabor Units plus Remaining Labor Units plus Remaining Nonlabor Units), multiplied by 100.
    Scope: Calculated as Installed Quantity divided by At Completion Quantity, multiplied by 100.
  • Allowed Values: [ "TOP", "HIGH", "NORMAL", "LOW", "LOWEST" ]
    Determines the priority of the activity when performing role leveling.
  • Allowed Values: [ "NOT_STARTED", "IN_PROGRESS", "COMPLETED" ]
    Determines the status of the activity. Valid values are Not Started, In Progress, and Completed.
  • Allowed Values: [ "ACTIVITY", "RESOURCE_DEPENDENT", "LEVEL_OF_EFFORT", "START_MILESTONE", "FINISH_MILESTONE", "WBS_SUMMARY" ]
    The type of activity. Valid values are Activity Dependent, Resource Dependent, Level of Effort, Start Milestone, and Finish Milestone.
  • activityUncertainties
    The uncertainties associated with an activity.
  • Allowed Values: [ "NO_TASK_DATES", "ALL_WITHIN", "AT_LEAST_ONE_OUTSIDE" ]
    The current state of task dates assigned to the activity.
  • Allowed Values: [ "NO_TASKS", "ACTIVITY_COMPLETE_TASKS_NOT", "TASKS_COMPLETE_ACTIVITY_NOT", "BOTH_COMPLETE", "BOTH_NOT_COMPLETE" ]
    The current status of the task assigned to the activity. Valid values are New, Pending, Committed, and Completed.
    This is a read-only field.
  • Indicates whether any of the activity's assigned tasks have dates or completion statuses that requires attention.
    This is a read-only field.
  • Minimum Value: 0
    Maximum Value: 10000000
    The total working time from the activity Actual Start date to the Actual Finish date for completed activities, or the total working time from the Actual Start date to the data date for in-progress activities.
    The actual working time is computed using the activity's calendar.
  • The date when the activity was completed.
  • The number of units expended for all labor resources assigned to the activity.
  • The number of nonlabor units that have been expended on the activity.
  • The date work on the activity began.
  • The number of labor units used during this financial period.
  • The nonlabor units used during this financial period.
  • The planned total labor units through activity completion.
  • Minimum Value: 0
    Maximum Value: 10000000
    The total working time from the activity's current start date to the current finish date.
    The current start date is the planned start date until the activity is started, and then it is the actual start date. The current finish date is the activity planned finish date while the activity is not started, the remaining finish date while the activity is in progress, and the actual finish date once the activity is completed. The total working time is calculated using the activity's calendar.
  • The sum of the actual plus remaining units for all labor resources assigned to the activity.
    It is the same as the planned labor units if the activity is not started, and the actual labor units after the activity is completed.
    Calculated as Actual Labor Units plus Remaining Labor Units.
  • The sum of the actual plus remaining units for all nonlabor resources assigned to the activity.
    It is the same as the planned nonlabor units if the activity is not started, and the actual nonlabor units after the activity is completed.
    Calculated as Actual Nonlabor Units plus Remaining Nonlabor Units.
  • The calendar assigned to the activity.
  • Minimum Length: 0
    Maximum Length: 255
    The name of the calendar.
  • codeValuesActivity
    The list of code values for an activity. This entity can only be used to assign codeValues or create codeValues on the fly.
  • The weight of the activity percent completed value.
  • configuredFields
    The list of configured fields for an activity.
  • The constraint date for the activity, if the activity has a constraint.
  • Allowed Values: [ "NONE", "START_ON", "START_ON_OR_BEFORE", "START_ON_OR_AFTER", "FINISH_ON", "FINISH_ON_OR_BEFORE", "FINISH_ON_OR_AFTER", "AS_LATE_AS_POSSIBLE", "MANDATORY_START", "MANDATORY_FINISH" ]
    The main restriction impacting the activity start or finish date.
  • The measure of a activity's cost efficiency.
  • The measure of a activity's cost efficiency in labor units.
  • The ratio of the cost variance and the earned value of work performed on the WBS or activity.
  • The difference between the earned value labor units and the actual labor units.
  • The ratio of the cost variance labor units and the earned value labor units for the activity.
  • Designates an activity as critical. An activity is defined as critical based upon the project settings configured for the project.
  • currentBaselineFields
    Activity fields available in the current baseline.
  • An activity with a dangling finish has only SF or SS successors and therefore could have an unrealistic finish date. To avoid dangling finishes, ensure each activity has at least one FS or SS relationship as its successor.
  • An activity with a dangling start has only SF or FF predecessors and therefore could have an unrealistic start date. To avoid dangling starts, ensure each activity has at least one FS or SS relationship as its predecessor.
  • The sequence of project activities from start to finish where the Total Duration is longer than any other path.
  • The duration percent complete for the activity. Calculated as Planned Duration minus Remaining Duration divided by Planned Duration multiplied by 100.
  • The actual duration percent of planned duration for the activity. Calculated as Actual Duration divided by Original BL Duration multiplied by 100.
  • Allowed Values: [ "FIXED_RATE", "FIXED_QUANTITY", "FIXED_DURATION_AND_UNITS", "FIXED_DURATION" ]
    Determines how remaining duration, units, and units/time are calculated when you update an activity that has resources assigned. The valid values are Fixed Units/Time, Fixed Units, Fixed Duration & Units, and Fixed Duration & Units/Time.
  • The earliest possible date the activity can finish.
    This date is calculated based on network logic, schedule constraints, and resource availability.
  • The earliest possible date the remaining work for the activity can begin.
    This date is calculated based on network logic, schedule constraints, and resource availability.
  • The portion of baseline labor units that are actually completed as of the project data date.
    Calculated as Budget At Completion Labor Units multiplied by Performance Percent Complete. The performance percent complete will be calculated using the activity percent complete.
  • The estimated labor units at completion.
    Calculated as Actual Labor Units plus Estimate To Complete Labor Units. Estimate To Complete Labor Units is calculated based off of the Earned Value setting.
  • The estimated number of labor units required to complete the activity.
    Calculated as the Remaining Total Units for the activity.
  • The date you expect work on the activity to finish.
  • Finish-to-Finish (FF) relationships are acceptable to use in moderation.
  • The current finish date for the activity.
  • Indicates which critical path the activity is on. An activity with a floatPath value of 1 is on the most critical path, whereas an activity with a floatPath value of 2 is on the second most critical path, and so on.
  • The position of the activity on its critical path.
  • The amount of time the activity can be delayed before delaying the start date of any successor activity.
  • Finish-to-Start (FS) relationships are the easiest to trace and understand. The majority of your relationships should be FS.
  • Mandatory Start and Mandatory Finish are hard constraints that prevent activities from being scheduled according to logic and prevent delays from impacting succeeding activities. The effects of hard constraints become more noticeable as the schedule is progressed, and they generally should not be used.
  • Progress should be recorded before the Data Date, and planned work should be recorded after. Activities with invalid dates can affect the accuracy of the project schedule.
  • The percent complete of units for all labor resources for the activity. Calculated as Actual Labor Units divided by At Completion Labor Units multiplied by 100.
  • Large duration activities are harder to manage and may lack sufficient detail. Consider dividing these activities into shorter, more discrete activities, which provide better insight into cost and schedule.
  • Large float values may indicate missing activity relationships. Provide activities with reasonable logic to ensure a more stable project plan.
  • Late activities indicate how well the project is performing against the earned value baseline.
  • The latest possible date the activity can finish without delaying the project finish date.
    This date is calculated based on activity relationships, schedule constraints, and resource availability.
  • The latest possible date the remaining work for the activity can begin without delaying the project finish date.
    This date is calculated based on activity relationships, schedule constraints, and resource availability.
  • Negative float usually indicates an activity constraint that cannot be met with the current schedule or progress has been made out of sequence. Corrective action should be taken to ensure activity dates are accurate and achievable.
  • The percent complete of units for all nonlabor resources for the activity. Calculated as Actual Nonlabor Units divided by At Completion Nonlabor Units multiplied by 100.
  • An activity with no predecessors could be scheduled to start immediately. This can negatively impact your project schedule and should be avoided.
  • Roles and resources detail the cost and labor of the work to be performed. An activity without roles or resources may be insufficiently planned.
  • An activity with no successor relationships could be delayed indefinitely without affecting project completion. Ensure all activities have at least one successor.
  • An activity without a predecessor or successor relationship may negatively affect the quality of your schedule and should be avoided.
  • originalBaselineFields
    Activity fields available for the original baseline.
  • otherBaselineFields
    Activity fields available for baseline marked other.
  • Maximum Length: 255
    The user responsible for the activity.
  • Allowed Values: [ "PHYSICAL", "DURATION", "UNITS", "SCOPE" ]
    Determines the way in which the application calculates the percent complete for the activity.
    Physical: Percent complete is manually entered by a user based on the amount of physical work completed on the activity.
    Duration: Percent complete is calculated from the actual and remaining duration.
    Units: Percent complete is calculated from the actual and remaining units.
    Scope: The percent complete for the activity is derived from the scope percent complete of the linked scope assignments.
  • Allowed Values: [ "COST", "QUANTITY", "HOURS", "MANUAL" ]
    The method used to calculate the scope percentage completion for scope assignments. The weight is calculated using cost, quantity, hours, or manually entered values.
  • The percentage of the planned work that is currently complete.
    Performance Percent Complete is used to calculate earned value and is equal to the activity percent complete.
  • The activity percent complete, manually entered by a user.
  • Minimum Value: 0
    Maximum Value: 10000000
    The expected amount of time required to complete an activity.
    The planned working time is calculated using the activity's calendar. The duration is measured from the activity's planned start date to its planned finish date.
  • The date the activity is scheduled to finish if the activity has not started.
    This date is calculated by the project scheduler but can be updated manually by the project manager. This date is not changed by the project scheduler after the activity has started.
  • The planned number of units for all labor resources assigned to the activity.
  • The planned units for all nonlabor resources assigned to the activities in the project.
  • The date the activity is scheduled to start.
    This date the activity is scheduled to begin is calculated by the project scheduler but can be updated manually by the project manager. This date cannot be changed by the project scheduler after the activity has started.
  • The portion of baseline labor units that are scheduled to be completed as of the project data date.
    Calculated as Budget At Completion Labor Units multiplied by Schedule Percent Complete.
  • Lag time between activities should not be used to control float or constrain dates. Consider representing the delay between two activities by adding another activity.
  • The use of negative lags to overlap activities or adjust successor dates can affect the critical path and distort total float. It can also cause a successor to start before a predecessor. Negative lags can cause activities to be scheduled in unrealistic ways and generally should not be used.
  • The user designated as the primary resource for the activity.
  • Prior Actual Labor Units
  • Prior Actual Nonlabor Units
  • Display Milestone on Program.
  • Minimum Length: 1
    Maximum Length: 60
    The unique identifier for a project set by the user who created the project.
  • The unique identifier for the project.The project object can also be identified by its unique criteria.
  • The number of activities added to the project.
  • Minimum Value: 0
    Maximum Value: 10000000
    The total working time from the activity remaining start date to the remaining finish date.
  • The date the remaining work for the activity is scheduled to finish.
    If this activity is not started, this date is the planned finish. This date can be updated manually by the user, but it is overwritten when you schedule the project.
  • The amount of time remaining in which the activity can be delayed before delaying the project finish date. Calculated as Late Finish minus Remaining Finish.
  • The remaining units for all labor resources assigned to the activity.
    The Remaining Labor Units reflect the work remaining to be done for the activity. Before the activity is started, the remaining units are the same as the planned units. After the activity is completed, the remaining units are zero.
  • The latest possible date the activity must finish without delaying the project finish date.
    This date is calculated by the project scheduler based on activity relationships, schedule constraints, and resource availability. When the activity is complete, this field is blank.
  • The latest possible date the remaining work for the activity must begin without delaying the project finish date.
    This date is calculated by the project scheduler based on activity relationship, schedule constraints, and resource availability.
  • The remaining units for all nonlabor resources assigned to the activity.
    The remaining units reflect the work remaining to be done for the activity. Before the activity is started, the remaining units are the same as the planned units. After the activity is completed, there are zero remaining units.
  • The date the remaining work for the activity is scheduled to begin.
    This date can be updated manually by the user. Before the activity is started, this date is the same as the planned start.
  • Minimum Length: 0
    Maximum Length: 930
    The unique identifiers of the resources assigned to the activity.
  • Minimum Length: 0
    Maximum Length: 3855
    The names of the resources assigned to the activity.
  • The date when a suspended task or activity is resumed.
  • Minimum Length: 0
    Maximum Length: 930
    The unique identifiers of the roles assigned to the activity.
  • Minimum Length: 0
    Maximum Length: 3855
    The names of the roles assigned to the activity.
  • The activity schedule percent complete specifies how much of the activity's project baseline duration is complete so far.
    With an earned value baseline selected, the schedule percent complete value is calculated based on where the current data date falls relative to the activity's project baseline start and finish dates.
    Calculated as (Data Date - Baseline Start Date) / (Baseline Finish Date - Baseline Start Date).
    If the data date is earlier than the baseline start, the schedule percent complete is 0. If the data date is later than the baseline finish, the schedule percent complete is 100.
    Without an earned value baseline selected, the schedule percent complete value will use the activity planned dates and will be calculated based on where the current data date falls relative each activity's planned start and finish dates.
    Calculated as (Data Date - Planned Start Date) / (Planned Finish Date - Planned Start Date).
    If the data date is earlier than the planned start, the schedule percent complete is 0. If the data date is later than the planned finish, the schedule percent complete is 100.
  • The ratio of the earned value of labor units to the planned value of labor units.
    Calculated as Earned Value Labor Units divided by Planned Value Labor Units.
  • The measure of work accomplished as a percentage of the work scheduled on the activity.
  • The ratio of schedule variance and the work scheduled to be performed.
  • The difference between the earned value of work performed and the work scheduled to be performed.
    Calculated as Earned Value Labor Units minus Planned Value Labor Units.
  • The ratio of schedule variance labor units and the planned value labor units.
    Calculated as Schedule Variance Labor Units divided by Planned Value Labor Units.
  • The percentage completion of the scope assignments linked to the activity.
    Calculated as Installed Quantity divided by At Completion Quantity.
  • The date for the activity's secondary constraint, if the activity has a secondary constraint.
  • Allowed Values: [ "NONE", "START_ON", "START_ON_OR_BEFORE", "START_ON_OR_AFTER", "FINISH_ON", "FINISH_ON_OR_BEFORE", "FINISH_ON_OR_AFTER", "AS_LATE_AS_POSSIBLE", "MANDATORY_START", "MANDATORY_FINISH" ]
    The secondary restriction impacting the activity start or finish date.
  • The number that specifies the position of the activity relative to others within the view.
  • Start-to-Finish (SF) relationship logic says the successor occurs before the predecessor. SF relationships are a poor practice and generally should not be used.
  • Soft constraints allow the schedule to be logic driven but can distort float and create negative float.
  • Start-to-Start (SS) relationships are acceptable to use in moderation.
  • Specifies whether the activity has been marked as important.
  • The current start date of the activity.
    For started activities, this is the actual start date. For not started activities, this is the planned start date until the project is scheduled. When scheduled, the start date field is set to the remaining early start date.
  • The date work has temporarily stopped on a given activity.
  • A measure of the value of the activity work that is remaining.
  • The amount of time the activity can be delayed before delaying the project finish date. Calculated as Late Start minus Early Start or as Late Finish minus Early Finish.
  • The percent complete of units for all labor and nonlabor resources assigned to the activity. Calculated as Actual Units divided by At Completion Units multiplied by 100.
  • Date when the record was last updated.
  • userBaseline1Fields
    Activity fields available for the current user's 1st baseline.
  • userBaseline2Fields
    Activity fields available for the current user's 2nd baseline.
  • userBaseline3Fields
    Activity fields available for the current user's 3rd baseline.
  • The duration between the activity's duration and the at completion duration.
  • The duration between the current project finish date and the baseline project finish date.
  • The difference between the baseline planned total labor units and the estimate at completion labor units.
    Calculated as Project Baseline Planned Total Labor Units minus Estimate At Completion Labor Units.
  • The difference between baseline labor units and at completion labor units.
  • The difference between the baseline nonlabor units and the at completion nonlabor units.
  • The duration between the current project start date and the baseline start date.
  • wbscodes
    List of WBS codes in hierarchy.
  • The WBS that the activity is associated with.
  • The importance of the activity in relation to other activities.
  • The number of tasks assigned to an activity.
    This is a read-only field.
  • The number of planned tasks assigned to the activity that are completed.
  • The number of planned tasks assigned to the activity that are not completed.
  • The number of planned tasks assigned to the activity whose Start or Finish dates fall outside of the activity's Start or Finish dates.
  • The number of unplanned tasks assigned to the activity that are not completed.
  • Minimum Length: 1
    Maximum Length: 60
    The unique identifier for the work package.
  • The unique identifier for the work package that the activity is associated with.
  • Minimum Length: 1
    Maximum Length: 255
    The name of the work package.
  • Minimum Length: 0
    Maximum Length: 60
    The user-specified identifier of a workspace.
Nested Schema : activityFinancial
An object containing the financial fields of an activity in the form of key-value pairs.
Match All
Show Source
Nested Schema : activityUncertainties
Type: array
The uncertainties associated with an activity.
Show Source
Nested Schema : codeValuesActivity
Type: array
The list of code values for an activity. 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 an activity.
Show Source
Nested Schema : currentBaselineFields
Activity fields available in the current baseline.
Match All
Show Source
Nested Schema : originalBaselineFields
Activity fields available for the original baseline.
Match All
Show Source
Nested Schema : otherBaselineFields
Activity fields available for baseline marked other.
Match All
Show Source
Nested Schema : userBaseline1Fields
Activity fields available for the current user's 1st baseline.
Match All
Show Source
Nested Schema : userBaseline2Fields
Activity fields available for the current user's 2nd baseline.
Match All
Show Source
Nested Schema : userBaseline3Fields
Activity fields available for the current user's 3rd baseline.
Match All
Show Source
Nested Schema : wbscodes
Type: array
List of WBS codes in hierarchy.
Show Source
Nested Schema : ApiEntityActivityFinancial
Type: object
Title: ApiEntityActivityFinancial
Show Source
Nested Schema : ApiEntityActivityUncertainty
Type: object
Title: ApiEntityActivityUncertainty
Show Source
Nested Schema : ApiEntityCodeValueActivity
Type: object
Title: ApiEntityCodeValueActivity
Show Source
Nested Schema : ApiEntityActivityConfiguredFieldValue
Type: object
Title: ApiEntityActivityConfiguredFieldValue
Show Source
Nested Schema : ApiEntityActivityBaselineFields
Type: object
Title: ApiEntityActivityBaselineFields
Read Only: true
Show Source
  • Read Only: true
    The percentage of the activity that has been completed.
    This value is based on the formula for the selected Percent Complete Type. The Percent Complete Type can be Physical, Duration, Units, or Scope.
    Physical: The user records the percent complete manually.
    Duration: Calculated as (Planned Duration minus Remaining Duration) divided by Planned Duration, multiplied by 100.
    Units: Calculated as (Actual Labor Units plus Actual Nonlabor Units) divided by (Actual Labor Units plus Actual Nonlabor Units plus Remaining Labor Units plus Remaining Nonlabor Units), multiplied by 100.
    Scope: Calculated as Installed Quantity divided by At Completion Quantity, multiplied by 100.
  • Read Only: true
    Allowed Values: [ "ACTIVITY", "RESOURCE_DEPENDENT", "LEVEL_OF_EFFORT", "START_MILESTONE", "FINISH_MILESTONE", "WBS_SUMMARY" ]
    The type of activity. Valid values are Activity Dependent, Resource Dependent, Level of Effort, Start Milestone, and Finish Milestone.
  • Read Only: true
    The total working time from the activity Actual Start date to the Actual Finish date for completed activities, or the total working time from the Actual Start date to the data date for in-progress activities.
    The actual working time is computed using the activity's calendar.
  • Read Only: true
    The date when the activity was completed.
  • Read Only: true
    The actual cost for all labor resources assigned to the activity as stored in the associated project baseline. This field is in base currency and is calculated from actualLaborCostProject field based on the specified exchange rate.
  • Read Only: true
    The actual cost for all labor resources assigned to the activity as stored in the associated project baseline. This value is based on the project currency.
  • Read Only: true
    The number of units expended for all labor resources assigned to the activity.
  • Read Only: true
    The actual cost for all material resources assigned to the activity as stored in the associated project baseline. This field is in base currency and is calculated from actualMaterialCostProject field based on the specified exchange rate.
  • Read Only: true
    The actual cost for all material resources assigned to the activity as stored in the associated project baseline. This value is based on the project currency.???
  • Read Only: true
    The actual cost for all nonlabor resources assigned to the activity as stored in the associated project baseline. This field is in base currency and is calculated from actualNonLaborCostProject field based on the specified exchange rate.
  • Read Only: true
    The actual cost for all nonlabor resources assigned to the activity as stored in the associated project baseline. This value is based on the project currency.
  • Read Only: true
    The number of nonlabor units that have been expended on the activity.
  • Read Only: true
    The date work on the activity began.
  • Read Only: true
    The actual total cost for all labor, nonlabor, and material resources assigned to the activity as stored in the associated project baseline. This field is in base currency and is calculated from actualTotalCostProject field based on the specified exchange rate.
  • Read Only: true
    The actual total cost for all labor, nonlabor, and material resources assigned to the activity as stored in the associated project baseline. This value is based on the project currency.
  • Read Only: true
    The constraint date for the activity, if the activity has a constraint.
  • Read Only: true
    Allowed Values: [ "NONE", "START_ON", "START_ON_OR_BEFORE", "START_ON_OR_AFTER", "FINISH_ON", "FINISH_ON_OR_BEFORE", "FINISH_ON_OR_AFTER", "AS_LATE_AS_POSSIBLE", "MANDATORY_START", "MANDATORY_FINISH" ]
    The main restriction impacting the activity start or finish date.
  • Read Only: true
    The duration percent complete for the activity. Calculated as Planned Duration minus Remaining Duration divided by Planned Duration multiplied by 100.
  • Read Only: true
    The duration between the activity's duration and the at completion duration.
  • Read Only: true
    The earliest possible date the activity can finish.
    This date is calculated based on network logic, schedule constraints, and resource availability.
  • Read Only: true
    The earliest possible date the remaining work for the activity can begin.
    This date is calculated based on network logic, schedule constraints, and resource availability.
  • Read Only: true
    The current finish date for the activity.
  • Read Only: true
    The duration between the current project finish date and the baseline project finish date.
  • Read Only: true
    The amount of time the activity can be delayed before delaying the start date of any successor activity.
  • Read Only: true
    Deprecated. As of 23.6.
    The planned number of units for all labor resources assigned to the activity.
  • Read Only: true
    The difference between baseline labor units and at completion labor units.
  • Read Only: true
    The latest possible date the activity can finish without delaying the project finish date.
    This date is calculated based on activity relationships, schedule constraints, and resource availability.
  • Read Only: true
    The latest possible date the remaining work for the activity can begin without delaying the project finish date.
    This date is calculated based on activity relationships, schedule constraints, and resource availability.
  • Read Only: true
    Deprecated. As of 23.6.
    The planned units for all nonlabor resources assigned to the activities in the project.
  • Read Only: true
    The difference between the baseline nonlabor units and the at completion nonlabor units.
  • Read Only: true
    Allowed Values: [ "PHYSICAL", "DURATION", "UNITS", "SCOPE" ]
    Determines the way in which the application calculates the percent complete for the activity.
    Physical: Percent complete is manually entered by a user based on the amount of physical work completed on the activity.
    Duration: Percent complete is calculated from the actual and remaining duration.
    Units: Percent complete is calculated from the actual and remaining units.
    Scope: The percent complete for the activity is derived from the scope percent complete of the linked scope assignments.
  • Read Only: true
    The expected amount of time required to complete an activity.
    The planned working time is calculated using the activity's calendar. The duration is measured from the activity's planned start date to its planned finish date.
  • Read Only: true
    The date the activity is scheduled to finish if the activity has not started.
    This date is calculated by the project scheduler but can be updated manually by the project manager. This date is not changed by the project scheduler after the activity has started.
  • Read Only: true
    The planned cost for all labor resources assigned to the activity in the associated project baseline. This field is in base currency and is calculated from plannedLaborCostProject field based on the specified exchange rate.
  • Read Only: true
    The planned cost for all labor resources assigned to the activity in the associated project baseline. This value is based on the project currency.
  • Read Only: true
    The planned number of units for all labor resources assigned to the activity.
  • Read Only: true
    The planned cost for all material resources assigned to the activity in the associated project baseline. This field is in base currency and is calculated from plannedMaterialCostProject field based on the specified exchange rate.
  • Read Only: true
    The planned cost for all material resources assigned to the activity in the associated project baseline. This value is based on the project currency.
  • Read Only: true
    The planned cost for all nonlabor resources assigned to the activity in the associated project baseline. This field is in base currency and is calculated from plannedNonLaborCostProject field based on the specified exchange rate.
  • Read Only: true
    The planned cost for all nonlabor resources assigned to the activity in the associated project baseline. This value is based on the project currency.
  • Read Only: true
    The planned units for all nonlabor resources assigned to the activities in the project.
  • Read Only: true
    The date the activity is scheduled to start.
    This date the activity is scheduled to begin is calculated by the project scheduler but can be updated manually by the project manager. This date cannot be changed by the project scheduler after the activity has started.
  • Read Only: true
    The expected total cost of the activity and includes all resources and direct activity costs (expenses) in the associated project baseline. This field is in base currency and is calculated from plannedTotalCostProject field based on the specified exchange rate.
  • Read Only: true
    The expected total cost of the activity and includes all resources and direct activity costs (expenses) in the associated project baseline. This value is based on the project currency.
  • Read Only: true
    The total working time from the activity remaining start date to the remaining finish date.
  • Read Only: true
    The date the remaining work for the activity is scheduled to finish.
    If this activity is not started, this date is the planned finish. This date can be updated manually by the user, but it is overwritten when you schedule the project.
  • Read Only: true
    The date the remaining work for the activity is scheduled to begin.
    This date can be updated manually by the user. Before the activity is started, this date is the same as the planned start.
  • Read Only: true
    The date for the activity's secondary constraint, if the activity has a secondary constraint.
  • Read Only: true
    Allowed Values: [ "NONE", "START_ON", "START_ON_OR_BEFORE", "START_ON_OR_AFTER", "FINISH_ON", "FINISH_ON_OR_BEFORE", "FINISH_ON_OR_AFTER", "AS_LATE_AS_POSSIBLE", "MANDATORY_START", "MANDATORY_FINISH" ]
    The secondary restriction impacting the activity start or finish date.
  • Read Only: true
    The current start date of the activity.
    For started activities, this is the actual start date. For not started activities, this is the planned start date until the project is scheduled. When scheduled, the start date field is set to the remaining early start date.
  • Read Only: true
    The duration between the current project start date and the baseline start date.
  • Read Only: true
    Allowed Values: [ "NOT_STARTED", "IN_PROGRESS", "COMPLETED" ]
    Determines the status of the activity. Valid values are Not Started, In Progress, and Completed.
  • Read Only: true
    The amount of time the activity can be delayed before delaying the project finish date. Calculated as Late Start minus Early Start or as Late Finish minus Early Finish.
  • Read Only: true
    The percent complete of units for all labor and nonlabor resources assigned to the activity. Calculated as Actual Units divided by At Completion Units multiplied by 100.
  • Read Only: true
    The difference between the associated project baseline planned labor cost and the current schedule at completion labor cost. This field is in base currency and is calculated from varianceLaborCostProject field based on the specified exchange rate.
  • Read Only: true
    The difference between the associated project baseline planned labor cost and the current schedule at completion labor cost. This value is based on the project currency.
  • Read Only: true
    The difference between the associated project baseline planned material cost and the current schedule at completion material cost. This field is in base currency and is calculated from varianceMaterialCostProject field based on the specified exchange rate.
  • Read Only: true
    The difference between the associated project baseline planned material cost and the current schedule at completion material cost. This value is based on the project currency.
  • Read Only: true
    The difference between the associated project baseline planned nonlabor cost and the current schedule at completion nonlabor cost. This field is in base currency and is calculated from varianceNonLaborCostProject field based on the specified exchange rate.
  • Read Only: true
    The difference between the associated project baseline planned nonlabor cost and the current schedule at completion nonlabor cost. This value is based on the project currency.
  • Read Only: true
    The difference between the associated project baseline planned labor, nonlabor, and material cost and the current schedule at completion labor, nonlabor, and material cost. This field is in base currency and is calculated from varianceTotalCostProject field based on the specified exchange rate.
  • Read Only: true
    The difference between the associated project baseline planned labor, nonlabor, and material cost and the current schedule at completion labor, nonlabor, and material cost. This value is based on the project currency.

404 Response

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