Create child requirements
post
/fscmRestApi/resources/11.13.18.05/requirements/{RqmtId}/child/ChildRequirements/{RqmtId2}/child/ChildRequirements
Request
Path Parameters
- RqmtId(required): integer(int64) Unique identifier of the project requirement in the requirement hierarchy.
- RqmtId2(required): integer(int64) The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
Header Parameters
- Metadata-Context: string 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".
- REST-Framework-Version: string 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.
- Upsert-Mode: string 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
- application/json
Root Schema : schema
Type:
Show Source object- Owner: string Title:
Requirement OwnerName of the requirement owner. - OwnerEmail: string Title:
Requirement Owner E-MailEmail of the requirement owner. - ParentRqmtCode: string Title:
Parent Requirement CodeUnique code of the parent requirement. - ParentRqmtId: integer (int64) Title:
Parent Requirement IDDefault Value:111Unique identifier of the parent requirement. - ParentRqmtName: string Title:
Parent Requirement NameName of the parent requirement. - Priority: string Title:
Requirement PriorityPriority of the requirement. - PriorityCode: string Title:
Requirement Priority CodeMaximum Length:30Default Value:MEDIUMUnique code of the requirement priority. - ProductName: string Title:
Product NameName of the product. - RqmtCode: string Title:
Requirement CodeMaximum Length:30Unique code of the requirement in the requirement hierarchy. - RqmtName: string Title:
Requirement NameMaximum Length:100Name of the requirement. - Status: string Title:
Requirement StatusStatus of the requirement. - StatusCode: string Title:
Requirement Status CodeMaximum Length:30Default Value:DRAFTUnique code of the requirement status.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
- Metadata-Context: 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".
- REST-Framework-Version: 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.
Root Schema : requirements-ChildRequirements-ChildRequirements-item-response
Type:
Show Source object- links: array Links Title:
LinksThe link relations associated with the resource instance. - Owner: string Title:
Requirement OwnerName of the requirement owner. - OwnerEmail: string Title:
Requirement Owner E-MailEmail of the requirement owner. - ParentRqmtCode: string Title:
Parent Requirement CodeUnique code of the parent requirement. - ParentRqmtId: integer (int64) Title:
Parent Requirement IDDefault Value:111Unique identifier of the parent requirement. - ParentRqmtName: string Title:
Parent Requirement NameName of the parent requirement. - Priority: string Title:
Requirement PriorityPriority of the requirement. - PriorityCode: string Title:
Requirement Priority CodeMaximum Length:30Default Value:MEDIUMUnique code of the requirement priority. - ProductCode: string Title:
Product CodeRead Only:trueMaximum Length:30Unique code of the product. - ProductName: string Title:
Product NameName of the product. - ReleaseName: string Title:
Release NameRead Only:trueMaximum Length:50Name of the product release. - ReleaseNumber: string Title:
Release NumberRead Only:trueMaximum Length:30Unique number of the product release. - RqmtCode: string Title:
Requirement CodeMaximum Length:30Unique code of the requirement in the requirement hierarchy. - RqmtId: integer (int64) Title:
Requirement IDRead Only:trueUnique identifier of the project requirement in the requirement hierarchy. - RqmtName: string Title:
Requirement NameMaximum Length:100Name of the requirement. - Status: string Title:
Requirement StatusStatus of the requirement. - StatusCode: string Title:
Requirement Status CodeMaximum Length:30Default Value:DRAFTUnique code of the requirement status.
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source Nested Schema : link
Type:
Show Source object- href: string Title:
hyperlink referenceThe URI to the related resource. - kind: string Title:
kindAllowed Values:[ "collection", "item", "describe", "other" ]The kind of the related resource. - name: string Title:
nameThe name of the link to the related resource. - properties: object properties
- rel: string Title:
relationAllowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source object- changeIndicator: string Change indicator or the ETag value of the resource instance.
Examples
The following example shows how to create a child requirement 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.17.08/requirements/{RqmtId}/child/ChildRequirements/{RqmtId2}/child/ChildRequirements Example of Request Body
The following example shows the contents of the request body in JSON format
{ "RqmtName": "Requirement_433", "OwnerEmail": "prj_mark_taylor_in_grp@oracle.com", "Owner": "Mark Taylor", "StatusCode": "DRAFT", "PriorityCode": "MEDIUM" } Example of Response Body
The following example shows the contents of the response body in JSON format.
{ "RqmtId": 300100114013930, "RqmtName": "Requirement_433", "OwnerEmail": "prj_mark_taylor_in_grp@oracle.com", "Owner": "Mark Taylor", "RqmtCode": "9062", "StatusCode": "DRAFT", "Status": "Draft", "PriorityCode": "MEDIUM", "Priority": "Medium", "ParentRqmtId": 111, "ParentRqmtCode": "1", "ParentRqmtName": "All Requirements", "ReleaseNumber": null, "ReleaseName": null, "ProductCode": null, "ProductName": null, "links": [... ] }