Skip to main content
Skip table of contents

log() Operation

To write log messages to the standard log of the xUML service, use the log() function. It provides the same functionality as the Log Adapter.

Syntax
NONE
log(level, type, code, description);
log(level, type, code, description, details);
SemanticsThe input consists of error level, type, code, and description. Valid log levels are: Fatal, Error, Warning, Info, and Debug as described in the log level guidelines on Bridge Server Log Levels of an xUML Service.
SubstitutableslevelString literals Fatal, Error, Warning, Info, or Debug.
typeString literal, usually containing the application name where the error occurred.
codeString literal, usually containing the error number.
descriptionString literal, usually containing the error description.
detailsRuntime 2020.6 Builder 7.8.0 (Optional) Object of complex type (class or array) that contains additional details. The contents of this object will be flattened and appended to the description.
Examples

Error Detail Object:

CODE
{
	"element": "AF-1201",
	"value":   "Adapter"
}

Log Statement:

NONE
log("Error", "Stock_Synchronization", "SYNC001", "Item ID could not be found.", errorDetail);

Content of the Log File (Class):

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

Content of the Log File (Array):

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

Example File (Builder project E2E Action Language/Operating):

<your example path>\E2E Action Language\Operating\uml\logger.xml
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.