Update a participant for change order
patch
/fscmRestApi/resources/11.13.18.05/changeOrders/{ChangeDocumentId}/child/ChangeParticipants/{ParticipantId}
Request
Path Parameters
-
ChangeDocumentId(required): integer(int64)
Unique identifier of a project change order. Mandatory for PATCH operation.
-
ParticipantId(required): integer(int64)
Unique identifier of the change order participant.
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.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object-
ApproveComments: string
Title:
Approval or Rejection CommentsMaximum Length:2000Approval or rejection comments by participant for a change order. Mandatory for rejecting the change order. -
ApproveFlag: boolean
Title:
Approver IndicatorMaximum Length:2Default Value:falseIndicates whether a participant is an approver on the change order. Valid values are Y, N, and R. The default value is N. -
ApproveStatus: string
Title:
Approver StatusMaximum Length:30Default Value:NApproval status of participant for a change order. Valid values are In Progress, Completed, and Rejected. -
AssessmentComments: string
Title:
Assessment CommentsMaximum Length:2000Assessment comments by participant for a change order. -
AssessmentFlag: boolean
Title:
Assessor IndicatorMaximum Length:2Default Value:falseIndicates whether a participant is an assessor on the change order. Valid values are Y and N. The default value is N. -
AssessmentStatus: string
Title:
Assessor StatusMaximum Length:30Default Value:NAssessment status of assessor for a change order. Valid values are In Progress and Completed. -
ImplementationComments: string
Title:
Implementation CommentsMaximum Length:2000Implementation comments by participant for a change order. -
ImplementationFlag: boolean
Title:
Implementor IndicatorMaximum Length:2Default Value:falseIndicates whether a participant is an implementor on the change order. Valid values are Y and N. The default value is N. -
ImplementationStatus: string
Title:
Implementor StatusMaximum Length:30Default Value:NImplementation status of participant for a change order. Valid values are In Progress and Completed. -
RejectDate: string
(date)
Title:
Rejection DateDate when change order was rejected. Calculated by application. -
RejectType: string
Title:
Rejection Reason CodeMaximum Length:30The code of the rejection type for a change order. Mandatory for rejecting the change order. Valid values are INSUFFICIENT_INFORMATION, OTHER, SCOPE_REDUCTION, and UNACCEPTABLE_RISK. -
ReviewComments: string
Title:
Review CommentsMaximum Length:2000Review comments by participant for a change order. -
ReviewFlag: boolean
Title:
Reviewer IndicatorMaximum Length:2Default Value:trueIndicates whether a participant is a reviewer on the change order. Valid values are Y and N. The default value is N. -
ReviewStatus: string
Title:
Reviewer StatusMaximum Length:30Default Value:NReview status of participant for a change order. Valid values are In Progress and Completed.
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 : changeOrders-ChangeParticipants-item-response
Type:
Show Source
object-
ApproveComments: string
Title:
Approval or Rejection CommentsMaximum Length:2000Approval or rejection comments by participant for a change order. Mandatory for rejecting the change order. -
ApproveFlag: boolean
Title:
Approver IndicatorMaximum Length:2Default Value:falseIndicates whether a participant is an approver on the change order. Valid values are Y, N, and R. The default value is N. -
ApproveStatus: string
Title:
Approver StatusMaximum Length:30Default Value:NApproval status of participant for a change order. Valid values are In Progress, Completed, and Rejected. -
AssessmentComments: string
Title:
Assessment CommentsMaximum Length:2000Assessment comments by participant for a change order. -
AssessmentFlag: boolean
Title:
Assessor IndicatorMaximum Length:2Default Value:falseIndicates whether a participant is an assessor on the change order. Valid values are Y and N. The default value is N. -
AssessmentStatus: string
Title:
Assessor StatusMaximum Length:30Default Value:NAssessment status of assessor for a change order. Valid values are In Progress and Completed. -
ImplementationComments: string
Title:
Implementation CommentsMaximum Length:2000Implementation comments by participant for a change order. -
ImplementationFlag: boolean
Title:
Implementor IndicatorMaximum Length:2Default Value:falseIndicates whether a participant is an implementor on the change order. Valid values are Y and N. The default value is N. -
ImplementationStatus: string
Title:
Implementor StatusMaximum Length:30Default Value:NImplementation status of participant for a change order. Valid values are In Progress and Completed. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
ParticipantEmail: string
Title:
Participant EmailEmail of the change order participant. -
ParticipantId: integer
(int64)
Title:
Participant IdRead Only:trueUnique identifier of the change order participant. -
ParticipantName: string
Title:
Participant NameName of the change order participant. -
ParticipantResourceId: integer
(int64)
Title:
Participant Resource IdResource identifier of the change order participant. -
RejectDate: string
(date)
Title:
Rejection DateDate when change order was rejected. Calculated by application. -
RejectType: string
Title:
Rejection Reason CodeMaximum Length:30The code of the rejection type for a change order. Mandatory for rejecting the change order. Valid values are INSUFFICIENT_INFORMATION, OTHER, SCOPE_REDUCTION, and UNACCEPTABLE_RISK. -
ReviewComments: string
Title:
Review CommentsMaximum Length:2000Review comments by participant for a change order. -
ReviewFlag: boolean
Title:
Reviewer IndicatorMaximum Length:2Default Value:trueIndicates whether a participant is a reviewer on the change order. Valid values are Y and N. The default value is N. -
ReviewStatus: string
Title:
Reviewer StatusMaximum Length:30Default Value:NReview status of participant for a change order. Valid values are In Progress and Completed.
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 update a participant 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/changeOrders/300100152034699/child/ChangeParticipants/300100152034701
Note:
You cannot add, update, or delete participants or impacts to a change order that is approved or in implementation stage.Request Body Example
The following shows an example of the request body in JSON format.
{
"ApproveFlag":"Y",
"ApproveStatus":"Completed"
}
Response Body Example
The following shows an example of the response body in JSON format.
{
"ParticipantId": 300100125631274,
"ParticipantResourceId": 300100024326751,
"ChangeDocumentId": 300100125631273,
"AssessmentFlag": true,
"AssessmentStatus": "InProgress",
"ReviewFlag": false,
"ReviewStatus": null,
"ApproveFlag": true,
"ApproveStatus": "Completed",
"ImplementationFlag": false,
"ImplementationStatus": null,
"AssessmentComments": null,
"ReviewComments": null,
"ApproveComments": null,
"ImplementationComments": null,
"RejectType": null,
"RejectDate": null,
"ParticipantName": "Abraham Mason",
"ParticipantEmail": "prj_wf_in_grp@oracle.com"
}