Create acceptance criteria
post
/fscmRestApi/resources/11.13.18.05/requirements/{RqmtId}/child/BacklogItems/{BacklogItemId}/child/AcceptanceCriteria
Request
Path Parameters
-
BacklogItemId(required): integer(int64)
Unique identifier of the backlog item.
-
RqmtId(required): integer(int64)
Unique identifier of the project requirement in the requirement hierarchy.
Header Parameters
-
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.
-
Upsert-Mode:
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
-
CriteriaName: string
Title:
Acceptance Criteria
Maximum Length:140
Condition that must be fulfilled for considering the backlog item to be complete.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context(required):
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(required):
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-BacklogItems-AcceptanceCriteria-item-response
Type:
Show Source
object
-
CriteriaId: integer
(int64)
Title:
Acceptance Criteria ID
Read Only:true
Unique identifier of the acceptance criteria under the backlog item. -
CriteriaName: string
Title:
Acceptance Criteria
Maximum Length:140
Condition that must be fulfilled for considering the backlog item to be complete. -
links: array
Links
Title:
Links
The link relations associated with the resource instance.
Nested Schema : Links
Type:
array
Title:
Links
The link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object
-
href: string
Title:
hyperlink reference
The URI to the related resource. -
kind: string
Title:
kind
Allowed Values:[ "collection", "item", "describe", "other" ]
The kind of the related resource. -
name: string
Title:
name
The name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relation
Allowed 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 acceptance criteria 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/BacklogItems/{BacklogItemId}/child/AcceptanceCriteria
Example of Request Body
The following example shows the contents of the request body in JSON format
{ "CriteriaName" : "Criteria one" }
Example of Response Body
The following example shows the contents of the response body in JSON format.
{ "CriteriaId": 300100114014087, "CriteriaName": "Criteria one", "links": [... ] }