Create processing information
post
/apiManagement/processingInformation/{adapter-id}/{api-name}/{api-version}/schemas/{resource-owner}/{classifier}/{id}
Request
Path Parameters
-
adapter-id(required): string
The value for the 'adapter-id', could be the valid adapter identifier that is used in the application configuration of that adapter. Example the tmf-629 FA adapter can have sample adapter-id as Note:- Please find the more information on how to develop and work with processingInformation service, through the Extensibility Tenant Documentation. * `tmf629FA` - the value is a string. * ..
-
api-name(required): string
The value for the 'api-name', could be the valid api names that is used in the application configuration of that adapter. Example the tmf-629 FA adapter can have sample api-name as * `customerManagement` - the value is a string. * ..
-
api-version(required): string
The value for the 'api-version', could be the valid api version that is used in the application configuration of that adapter. Example the tmf-629 FA adapter can have sample api-version as * `v4` - the value is a string. * ..
-
classifier(required): string
Below are the list of valid sample values for 'classifier': * `Common`, `Customer`, `EngagedParty`, `Product`, `Resource`, `service` and `MarketingSales`, `buying`, `care`, `common` and `launch`, - the value is a string. * ..
-
id(required): string
The file name of the processingInformation to be uploaded or created will be used as {id} value. Below is sample value for {id}: * `TenantOracleCustomer` - the value is a string. * ..
-
resource-owner(required): string
Below are the list of valid sample values for 'resource-owner': * `industry`, `oracle` and `custom`- the value is a string. * ..
Supported Media Types
- application/json
Root Schema : schema
Processing information is a ECMAScript 6 run by the EDK (Extensibility Developement Kit) on an EDK based adapter as a custom code in order to perform the aftermarket extension processing. As service request body is code but not the standard json schema, hence it doesn't have the schema meta data
Response
Supported Media Types
- application/json
200 Response
OK
Root Schema : schema
Processing information is a ECMAScript 6 run by the EDK (Extensibility Developement Kit) on an EDK based adapter as a custom code in order to perform the aftermarket extension processing. As service request body is code but not the standard json schema, hence it doesn't have the schema meta data
400 Response
Bad Request
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
401 Response
Unauthorized
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
403 Response
Forbidden
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
404 Response
Not Found
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
500 Response
Internal Server Error
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension