Create a dependency between two tasks of a project

post

/fscmRestApi/resources/11.13.18.05/projectPlans/{ProjectId}/child/TaskDependencies

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.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Dependency Type
    Maximum Length: 30
    Default Value: fs
    The type of dependency that exists between project elements. Valid values are fs, if, sash, sf. Default value is fs if not provided when using POST.
  • Title: Integration Source
    Indicates the task was created in a third-party application.
  • Title: Lag
    Default Value: 0
    Number of days that exist between project elements before the dependency is activated. Default value is 0 if not provided when using POST.
  • Title: Predecessor Task ID
    Unique identifier of the predecessor project element. Value is mandatory when using POST.
  • Title: Successor Task ID
    Unique identifier of the successor project element. Value is mandatory when using POST.
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-TaskDependencies-item-response
Type: object
Show Source
  • Title: Dependency ID
    Read Only: true
    Identifier of the dependency that exists between two tasks. Value is auto-generated when using POST and mandatory when using PATCH.
  • Title: Dependency Type
    Maximum Length: 30
    Default Value: fs
    The type of dependency that exists between project elements. Valid values are fs, if, sash, sf. Default value is fs if not provided when using POST.
  • Title: Integration Source
    Indicates the task was created in a third-party application.
  • Title: Lag
    Default Value: 0
    Number of days that exist between project elements before the dependency is activated. Default value is 0 if not provided when using POST.
  • Links
  • Title: Predecessor Task ID
    Unique identifier of the predecessor project element. Value is mandatory when using POST.
  • Title: Successor Task ID
    Unique identifier of the successor project element. Value is mandatory when using POST.
Back to Top

Examples

The following example shows how to create a dependency between two tasks by submitting a POST request on the REST resource using cURL.

curl --user ppm_cloud_user -X POST -d @example_request_payload.json --header "Content-Type: application/json" https://your_organization.com:port/fscmRestApi/resources/11.13.18.05/projectPlans/300100071625059/child/TaskDependencies

Request Body Example

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

{

"PredecessorTaskId" : 300100071849086,
"SuccessorTaskId": 300100071849089
}

Response Body Example

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

{
  "DependencyId" : 300100169228615,
  "DependencyType" : "fs",
  "Lag" : 0,
  "PredecessorTaskId" : 300100071849086,
  "SuccessorTaskId" : 300100071849089
}
Back to Top