Update an expense resource assignment for a task

patch

/fscmRestApi/resources/11.13.18.05/projectPlans/{ProjectId}/child/TaskExpenseResourceAssignments/{TaskExpenseResourceAssignmentId}

Request

Path Parameters
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Expense Resource Actual Amount
    Default Value: 0
    The actual expense cost amount of a specific expense resource assigned to the task. Default value is 0 when using POST.
  • Title: Expense Resource Current Amount
    The current expense cost amount of a specific expense resource assigned to the task. It is auto-calculated as the sum of Expense Resource Actual Amount plus Expense Resource Remaining Amount.
  • Title: Expense Resource ID
    Identifier of the expense resource assigned to the project task. You must enter either the Expense Resource Name or the Expense Resource ID when using POST or PATCH, but not both.
  • Title: Integration Source
    Indicates the task was created in a third-party application.
  • Title: Expense Resource Planned Amount
    Default Value: 0
    The planned expense cost amount of a specific expense resource assigned to the task. Default value is 0 when using POST.
  • Title: Expense Resource Remaining Amount
    Default Value: 0
    The remaining expense cost amount of a specific expense resource assigned to the task. Default value is 0 when using POST.
  • Title: Expense Resource Name
    Maximum Length: 240
    Name of the expense resource assigned to the project task. You must enter either the Expense Resource Name or the Expense Resource ID when using POST or PATCH, but not both.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : projectPlans-TaskExpenseResourceAssignments-item-response
Type: object
Show Source
  • Title: Expense Resource Actual Amount
    Default Value: 0
    The actual expense cost amount of a specific expense resource assigned to the task. Default value is 0 when using POST.
  • Title: Expense Resource Current Amount
    The current expense cost amount of a specific expense resource assigned to the task. It is auto-calculated as the sum of Expense Resource Actual Amount plus Expense Resource Remaining Amount.
  • Title: Expense Resource ID
    Identifier of the expense resource assigned to the project task. You must enter either the Expense Resource Name or the Expense Resource ID when using POST or PATCH, but not both.
  • Title: Integration Source
    Indicates the task was created in a third-party application.
  • Links
  • Title: Expense Resource Planned Amount
    Default Value: 0
    The planned expense cost amount of a specific expense resource assigned to the task. Default value is 0 when using POST.
  • Title: Expense Resource Remaining Amount
    Default Value: 0
    The remaining expense cost amount of a specific expense resource assigned to the task. Default value is 0 when using POST.
  • Title: Expense Resource Name
    Maximum Length: 240
    Name of the expense resource assigned to the project task. You must enter either the Expense Resource Name or the Expense Resource ID when using POST or PATCH, but not both.
  • Title: Expense Resource Assignment ID
    Read Only: true
    Unique identifier of the expense resource assignment to the project task. Value is auto-generated when using POST and mandatory when using PATCH.
  • Title: Task ID
    Identifier of the task to which the expense resource is assigned. Value is mandatory when using POST and must refer to a task that already exists in the project.
Back to Top

Examples

The following example shows how to update an expense resource assignment by submitting a PATCH request on the REST resource using cURL.

curl --user ppm_cloud_user -X PATCH -d @example_request_payload.json --header "Content-Type: application/json" https://your_organization.com:port/fscmRestApi/resources/11.13.18.05/projectPlans/300100124723999/child/TaskExpenseResourceAssignments/300100124762029

Request Body Example

The following shows an example of the request body in JSON format.

{
"ResourceName" : "Air",
"ActualAmount" : 100,
 "PlannedAmount" : 51
}

Response Body Example

The following shows an example of the response body in JSON format.

{
    "ActualAmount": 100,
    "CurrentAmount": 100,
    "TaskExpenseResourceAssignmentId": 300100124762029,
    "ExpenseResourceId": 1001,
    "PlannedAmount": 51,
    "RemainingAmount": 0,
    "ResourceName": "Air",
    "TaskId": 300100124764034}
Back to Top