Update a compliance associated with the conditions of approval

patch

/fscmRestApi/resources/11.13.18.05/publicSectorConditionComplyTransactions/{publicSectorConditionComplyTransactionsUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- CoaKey and ComplyPrdId ---for the Condition of Approval Compliance Transactions resource and used to uniquely identify an instance of Condition of Approval Compliance Transactions. The client should not generate the hash key value. Instead, the client should query on the Condition of Approval Compliance Transactions collection resource with a filter on the primary key values in order to navigate to a specific instance of Condition of Approval Compliance Transactions.

    For example: publicSectorConditionComplyTransactions?q=CoaKey=<value1>;ComplyPrdId=<value2>
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 ()
The following table describes the body parameters in the request for this task.
Root Schema : schema
Type: object
Show Source
  • Title: Resolution Comments
    Maximum Length: 1000
    The comment entered at the time of resolution.
  • Maximum Length: 1
    Default Value: false
    Indicates if the compliance is applicable to the conditions of approval.
  • Title: Resolved
    Maximum Length: 10
    Default Value: ORA_APLY
    Indicates if the compliance period is resolved or applied.
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 : publicSectorConditionComplyTransactions-item-response
Type: object
Show Source
  • The unique identifier of the condition of approval.
  • Title: Resolution Comments
    Maximum Length: 1000
    The comment entered at the time of resolution.
  • Maximum Length: 20
    The identifier of the compliance associated with the conditions of approval.
  • Maximum Length: 1
    Default Value: false
    Indicates if the compliance is applicable to the conditions of approval.
  • Links
  • Title: Resolved
    Maximum Length: 10
    Default Value: ORA_APLY
    Indicates if the compliance period is resolved or applied.
Back to Top