Create a set of compliances associated with the conditions of approval

post

/fscmRestApi/resources/11.13.18.05/publicSectorConditionComplyTransactions

Request

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.
  • 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
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • The unique identifier of the condition of approval.
  • Maximum Length: 480
    The public unique identifier of the migrated condition of approval.
  • The unique identifier of the condition of approval associated with the transaction complies.
  • Maximum Length: 480
    The public unique identifier of the migrated condition approval associated with the transaction complies.
  • 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.
  • Maximum Length: 3
    Indicates whether the transaction was created online or migrated from a legacy system.
  • 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.
  • Maximum Length: 480
    The public unique identifier of the migrated condition of approval.
  • The unique identifier of the condition of approval associated with the transaction complies.
  • Maximum Length: 480
    The public unique identifier of the migrated condition approval associated with the transaction complies.
  • 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
  • Maximum Length: 3
    Indicates whether the transaction was created online or migrated from a legacy system.
  • Title: Resolved
    Maximum Length: 10
    Default Value: ORA_APLY
    Indicates if the compliance period is resolved or applied.
Back to Top