Create or update a pricing logic algorithm specification
put
https://{FusionAppsHost}/crmRestApi/atcProductCatalog/11.13.18.05/tmf-api/productCatalogManagement/v4/pricingLogicAlgorithmSpecification/{id}
Request
Path Parameters
-
id(required): string
The unique identifier of the resource item.
Supported Media Types
- application/json
Root Schema : Discriminator: @type
Type:
object
Discriminator: @type
Discriminator Values
Response
Supported Media Types
- application/json
200 Response
OK
Root Schema : Discriminator: @type
Type:
object
Discriminator: @type
Discriminator Values
400 Response
Your request couldn't be processed because it contains missing or invalid information, such as a validation error on an input field, a missing required value, and so forth.
Root Schema : Error
Type:
object
Title:
Show Source
Error
-
@schemaLocation: string
It provides a link to the schema describing a REST resource.
-
@type: string
The class type of a REST resource.
-
code(required): string
Application related code (as defined in the API or from a common list)
-
message: string
Text that provide more details and corrective actions related to the error. This can be shown to a client user.
-
reason(required): string
Text that explains the reason for error. This can be shown to a client user.
-
referenceError: string
url pointing to documentation describing the error
-
status: string
http error code extension like 400-2
401 Response
Your request isn't authorized. The authentication credentials included with this request are missing or invalid.
Root Schema : Error
Type:
object
Title:
Show Source
Error
-
@schemaLocation: string
It provides a link to the schema describing a REST resource.
-
@type: string
The class type of a REST resource.
-
code(required): string
Application related code (as defined in the API or from a common list)
-
message: string
Text that provide more details and corrective actions related to the error. This can be shown to a client user.
-
reason(required): string
Text that explains the reason for error. This can be shown to a client user.
-
referenceError: string
url pointing to documentation describing the error
-
status: string
http error code extension like 400-2
404 Response
Your request includes a resource URI that doesn't exist.
Root Schema : Error
Type:
object
Title:
Show Source
Error
-
@schemaLocation: string
It provides a link to the schema describing a REST resource.
-
@type: string
The class type of a REST resource.
-
code(required): string
Application related code (as defined in the API or from a common list)
-
message: string
Text that provide more details and corrective actions related to the error. This can be shown to a client user.
-
reason(required): string
Text that explains the reason for error. This can be shown to a client user.
-
referenceError: string
url pointing to documentation describing the error
-
status: string
http error code extension like 400-2
405 Response
HTTP action specified in the request (DELETE, GET, POST, PUT) isn't supported for this request URI.
Root Schema : Error
Type:
object
Title:
Show Source
Error
-
@schemaLocation: string
It provides a link to the schema describing a REST resource.
-
@type: string
The class type of a REST resource.
-
code(required): string
Application related code (as defined in the API or from a common list)
-
message: string
Text that provide more details and corrective actions related to the error. This can be shown to a client user.
-
reason(required): string
Text that explains the reason for error. This can be shown to a client user.
-
referenceError: string
url pointing to documentation describing the error
-
status: string
http error code extension like 400-2
500 Response
The server encountered something unexpected that prevented it from completing the request.
Root Schema : Error
Type:
object
Title:
Show Source
Error
-
@schemaLocation: string
It provides a link to the schema describing a REST resource.
-
@type: string
The class type of a REST resource.
-
code(required): string
Application related code (as defined in the API or from a common list)
-
message: string
Text that provide more details and corrective actions related to the error. This can be shown to a client user.
-
reason(required): string
Text that explains the reason for error. This can be shown to a client user.
-
referenceError: string
url pointing to documentation describing the error
-
status: string
http error code extension like 400-2
501 Response
The server doesn't support the functionality required to fulfill the request.
Root Schema : Error
Type:
object
Title:
Show Source
Error
-
@schemaLocation: string
It provides a link to the schema describing a REST resource.
-
@type: string
The class type of a REST resource.
-
code(required): string
Application related code (as defined in the API or from a common list)
-
message: string
Text that provide more details and corrective actions related to the error. This can be shown to a client user.
-
reason(required): string
Text that explains the reason for error. This can be shown to a client user.
-
referenceError: string
url pointing to documentation describing the error
-
status: string
http error code extension like 400-2
Examples
The following example shows how to create or update a pricing logic algorithm specification by submitting a PUT request on the REST resource using cURL.
cURL Command
curl -u username:password -X PUT https://{FusionAppsHost}/crmRestApi/atcProductCatalog/11.13.18.05/tmf-api/productCatalogManagement/v4/pricingLogicAlgorithmSpecification/PLAspec4 -H 'Content-Type: application/json' -D @put_plapsecification.json | json_pp
Example of Request Body
The following example shows the contents of the request body in JSON format.
{ "id": "PLAspec4", "name": "PLAspec4", "description": "description of PLA4 spec", "version": "1.0", "lifecycleStatus": "In design", "@type": "PricingLogicAlgorithmSpecOracle", "@baseType": "PricingLogicAlgorithmSpec", "productSpecCharacteristic": [ { "name": "Colour", "description": "Phone Colour", "valueType": "STRING", "configurable": true, "minCardinality": 1, "maxCardinality": 1, "isUnique": true, "extensible": false } ], "project": { "id": "SpringProject", "name": "SpringProject" } }
Example of Response Body
The
following example shows the contents of the response body in JSON
format.
{ "id": "PLAspec4", "name": "PLAspec4", "description": "description of PLA4 spec", "version": "1.0", "lifecycleStatus": "In design", "@type": "PricingLogicAlgorithmSpecOracle", "@baseType": "PricingLogicAlgorithmSpec", "productSpecCharacteristic": [ { "name": "Colour", "description": "Phone Colour", "valueType": "STRING", "configurable": true, "minCardinality": 1, "maxCardinality": 1, "isUnique": true, "extensible": false } ], "project": { "id": "SpringProject", "name": "SpringProject" }, "href": "https://{FusionAppsHost}/crmRestApi/atcProductCatalog/11.13.18.05/tmf-api/productCatalogManagement/v4/pricingLogicAlgorithmSpecification/PLAspec4", "createdBy": "booth", "created": "2020-08-24T13:43:18.000Z", "lastUpdatedBy": "booth", "lastUpdate": "2020-08-24T13:43:18.000Z" }