NextGen APIs
NextGen APIs
Breadcrumbs

POST /integration/configurations/r1/asset-characteristics-value

Http Verb

POST

Url

/integration/configurations/r1/asset-characteristics-value

Permissions required

Core Additional Parameters: Edit (fsm.core.additionalparameter.edit)

Technical Object: View (fsm.core.technicalobject.facility.view)

or

Technical Object: Edit (fsm.core.technicalobject.facility.edit)

Facility Configuration: Edit (fsm.core.technicalobject.facility.edit)

Last Modified Version

r1

Tech Tags


Available Async

No

BPMN Diagram

diagram (24).svg

Business Logic

This Integration API creates or updates an Asset Characteristic value.

System verifies Permission Required and starts the elaboration that is organized in steps.

STEP 1 - External System Validation

System takes Input fields and checks their existence in internal configuration.

API Verb: GET

Resource: External Systems

Input: externalSystemCode, active=true

Output: externalSystemId

If System can obtain the Output fields → continue to next step.

If System can’t obtain the Output fields → responds with error. Elaboration is stopped.

Error Type:

STEP 2 - Asset Existence

System takes Input fields and checks their existence in internal configuration because it’s forbidden to have multiple Assets with the same code.

API Verb: GET

Resource: Assets

Input: asset.code

Output: assetId

If System can obtain the Output fields → continue to next step.

If System can’t obtain the Output fields → responds with error. Elaboration is stopped.

Error Type:

STEP 3 - Characteristics Validation

The following steps are executed for each Characteristic in Input.

STEP 3a - Characteristic Class Validation

System takes Input fields and checks their existence in internal configuration.

System uses a specific typeId for FACILITIES.

API Verb: GET

Resource: Characteristic Classes

Input: classCode, typeId=1, active=true

Output: characteristicClassId

If System can obtain the Output fields → continue to next step.

If System can’t obtain the Output fields → responds with error. Elaboration is stopped.

Error Type:

STEP 3b - Characteristic Validation

System takes Input fields and checks their existence in internal configuration.

API Verb: GET

Resource: Characteristic

Input: characteristic.code, characteristicClassId, active=true

Output: characteristicId

If System can obtain the Output fields → continue to next step.

If System can’t obtain the Output fields → responds with error. Elaboration is stopped.

Error Type:

STEP 4 - Asset Characteristic Relationship Upsert

The following steps are executed for each Characteristic in Input.

STEP 4a - Asset Characteristic Relationship Existence

System takes Input fields and checks their existence in internal configuration.

API Verb: GET

Resource: Asset Characteristic

Input: assetId, characteristicId

Output: assetCharacteristic.id

If System can obtain the Output fields → continue to step Asset Characteristic Relationship Update.

If System can’t obtain the Output fields → continue to next step Asset Characteristic Relationship Creation.

Error Type:

STEP 4b - Asset Characteristic Relationship Creation

System takes Input fields and checks their existence in internal configuration.

API Verb: POST

Resource: Create Asset Characteristics in Batch

Input: assetId, [{characteristicId, assetId, value}]

Output: Response State

If Response State is SUCCESS → elaboration is stopped. See Response payload fields.

If Response State is ERROR → elaboration is stopped. See Response payload fields.

Error Type:

  • Others - see link in Resource

STEP 4c - Asset Characteristic Relationship Update

System takes Input fields and checks their existence in internal configuration.

API Verb: PATCH

Resource: Update Asset Characteristics in Batch

Input: assetId, [{assetCharacteristic.id, value}]

Output: Response State

If Response State is SUCCESS → elaboration is stopped. See Response payload fields.

If Response State is ERROR → elaboration is stopped. See Response payload fields.

Error Type:

  • Others - see link in Resource

Path Parameters

As their name suggests, they are included in the URL path of the endpoint.

Not applicable.

Query String Parameters

Start with a ? and includes parameters listed one after the another separated by &.

Not applicable.

Header Parameters

Parameters included in the request headers. Generally, request headers are used to keep authorization parameters.

Default.

Request Body Parameters

Request body parameters are used when clients send data to the API. They are shipped in a JSON Object only in POST, PUT, or PATCH requests.

 

Field

Description

Mandatory

Constraint

1

asset

externalSystemCode

External System Code

Y

Not Blank

2

code

Asset Code

Y

Not Blank

3

characteristics

(minOccurs=0,
maxOccurs=N)

classCode

Characteristic Class Code

Y

Not Blank

4

code

Characteristic Code

Y

Not Blank

5

value

Value

N


The objects in input could have also the extension object that allows to add additional, customized data to this API. More info here How to use APIs: Custom data via Extension.

Request example

JSON
{   
  "extension": {},
  "asset": {
    "extension": {
        "myFieldName": "myValue"
    },
    "externalSystemCode": "SAP",
    "code": "TRASF"
  },
  "characteristics": [ 
    {
      "extension": {
         "myFieldName": "myValue"
      },
      "classCode": "POW-METER",
      "code": "OILLEV",
      "value": "5"
    }
  ]
}

 

Response documentation

Response payload fields

Compliant with RFC Standard https://www.rfc-editor.org/rfc/rfc9457.html

Extension fields:

Field

Description

Note

code

Extension member of a Problem Details Object that contains the error code

Only for ERROR

Response example

JSON
{
  "type": "about:blank",
  "title": "Not Found",
  "status": 404,
  "detail": "External system string does not exist",
  "instance": "/integration/configurations/r1/asset-characteristics-value",
  "code": "IA001_001"
}

 Response error codes