Modeling Technical Errors
For an automated activity, you can model a boundary event called Technical Error. This exception is critical and is thrown when the service that is called by the automated activity throws a technical error.
You can model a reaction to a technical error with a boundary event. A technical error is, for example, a system timeout, connectivity problem, program error, or misconfiguration. You can use any WSDL faults that the service might throw to model an additional boundary event.
The boundary event Technical Error offers a list of parameters related to the thrown technical error that can be reused in the process context.
The parameter data structure contains the following information:
| Parameter Name | Description | XSD Type | Connectivity | ||
|---|---|---|---|---|---|
| Web Service | RFC | Process Integration (XI) | |||
| interfaceName | Name of the service interface | string | yes | yes | yes |
| interfaceNamespace | Namespace of the service interface | string | yes | yes | yes |
| operationName | Name of the operation | string | yes | yes | yes |
| connectivityType* | WS, RFC, or XI | string | yes | yes | yes |
| applicationName | Name of the application | string | yes | yes | yes |
| errorMessage | Exception message | string | yes | yes | yes |
| rootErrorMessage | Exception message of the root cause | string | yes | yes | yes |
| componentName | Name of the component | string | yes | yes | yes |
| messageId | Name of message ID | string | n/a | n/a | yes |
| principalName | Name of principal. If principal propagation is ON, this is the propagated principal. Otherwise, it is the BPM Service User. | string | yes | yes | yes |
| wsStyle | DOC, RPC | string | yes | n/a | n/a |
| logId | GUID of TRACE record | string | yes | yes | yes |
| startTimeMs | Time when the service was called | long | yes | yes | yes |
| returnTimeMs | Time when the error occurred | long | yes | yes | yes |
| startTime | Like startTimeMs, but represented as xsd:dateTime (UTC) | dateTime | yes | yes | yes |
| returnTime | Like returnTimeMs, but represented as xsd:dateTime (UTC) | dateTime | yes | yes | yes |
* This parameter might not be set for process definitions built with a version below SAP NetWeaver 7.3 including enhancement package 1 support package stack 06.
The technical error event is also tracked in the business log. It is a prerequisite that the log level is set at least to Failure.