You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

On this Page:

Related Pages:
With the <<Logger>> adapter you can write into the log file of the service. Use action log in this case.

The following picture shows the usage of the <<Logger>> adapter:

Tag action of the logger adapter needs to be set to log. The following input can be provided:

Object NameTypeDescriptionAllowed Values / Example
levelStringSpecify one of the error log levels described in the log level guidelines on Bridge Server Log Levels of an xUML Service.One of Fatal, Error, Warning, Info, and Debug.
typeStringSpecify a custom error domain.Stock_Synchronization
codeStringSpecify a custom error code.SYNC001
descriptionStringSpecify a description for the log entry.Item ID could not be found.
detailsAnyRuntime 2020.6 Builder 7.8.0 Specify an object of complex type (class or array) that contains additional details. The contents of this object will be flattened and appended to the description.an error detail object

Example

PinValue
levelError
typeStock_Synchronization
codeSYNC001
descriptionItem ID could not be found.
details
  1. An error detail object:
    { "element": "AF-1201", "value": "Adapter" }
  2. An array of objects:
    [
           { "element": "AF-1201", "value": "Adapter" },
           { "element": "CD-2000", "value": "Connector" }
    ]

The output after running the example can be found in the standard xUML service log of the xUML service:

...[Error][Internal][Stock_Synchronization][Item ID could not be found. Detail: e2e:type='ErrorDetail', element='AF-1201', value='Adapter']

In case of an array, the output would look something like:

... Detail: e2e:type='ErrorDetail', [0].element='AF-1201', [0].value='Adapter', [1].element='CD-2000', [1].value='Connector'

  • No labels