Create a set of compliances associated with the conditions of approval
post
/fscmRestApi/resources/11.13.18.05/publicSectorConditionComplyTransactions
Request
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:
When set to true, the server will perform an Upsert operation instead of a Create. In an Upsert operation the server attempts to find an existing resource that matches the payload. If found, the server updates the existing resource instead of creating a new one. If not found, or when set to false (the default), a Create is performed.
Supported Media Types
- application/json
The following table describes the body parameters in the request for this task.
Root Schema : schema
Type:
Show Source
object-
CoaKey: integer
(int64)
The unique identifier of the condition of approval.
-
Comments: string
Title:
Resolution CommentsMaximum Length:1000The comment entered at the time of resolution. -
ComplyPrdId: string
Maximum Length:
20The identifier of the compliance associated with the conditions of approval. -
EnabledFlag: boolean
Maximum Length:
1Default Value:falseIndicates if the compliance is applicable to the conditions of approval. -
Status: string
Title:
ResolvedMaximum Length:10Default Value:ORA_APLYIndicates if the compliance period is resolved or applied.
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 : publicSectorConditionComplyTransactions-item-response
Type:
Show Source
object-
CoaKey: integer
(int64)
The unique identifier of the condition of approval.
-
Comments: string
Title:
Resolution CommentsMaximum Length:1000The comment entered at the time of resolution. -
ComplyPrdId: string
Maximum Length:
20The identifier of the compliance associated with the conditions of approval. -
EnabledFlag: boolean
Maximum Length:
1Default Value:falseIndicates if the compliance is applicable to the conditions of approval. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
Status: string
Title:
ResolvedMaximum Length:10Default Value:ORA_APLYIndicates if the compliance period is resolved or applied.
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.