Update requirement score of one team member

patch

/fscmRestApi/resources/11.13.18.05/supplierNegotiationResponses/{supplierNegotiationResponsesUniqID}/child/sections/{SectionId}/child/requirements/{RequirementId}/child/teamMemberRequirementScores/{teamMemberRequirementScoresUniqID}

Request

Path Parameters
  • 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=
  • 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=
  • This is the hash key of the attributes which make up the composite key for the Supplier Negotiation Responses resource and used to uniquely identify an instance of Supplier Negotiation Responses. The client should not generate the hash key value. Instead, the client should query on the Supplier Negotiation Responses collection resource in order to navigate to a specific instance of Supplier Negotiation Responses to get the hash key.
  • This is the hash key of the attributes which make up the composite key--- ResponseNumber, ScoringTeamMemberId and RequirementId ---for the Team Member Requirement Scores resource and used to uniquely identify an instance of Team Member Requirement Scores. The client should not generate the hash key value. Instead, the client should query on the Team Member Requirement Scores collection resource with a filter on the primary key values in order to navigate to a specific instance of Team Member Requirement Scores.

    For example: teamMemberRequirementScores?q=ResponseNumber=<value1>;ScoringTeamMemberId=<value2>;RequirementId=<value3>
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
  • Maximum Length: 4000
    Internal note added by the scoring team member while scoring the requirements in the response.
  • Score entered by the scoring team member while scoring the requirements in the response.
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 : supplierNegotiationResponses-sections-requirements-teamMemberRequirementScores-item-response
Type: object
Show Source
Back to Top