Exception processing configuration
Integrating with external systems can introduce additional problems such as network errors involving firewalls, incorrect authentication or credentials, or system failures. An application that handles exceptions properly is critical to the success of any application.
Many errors can be anticipated at design time and addressed with specific actions to help ensure positive customer interaction. But unexpected errors may still occur and are just as important to address promptly.
Exception processing is critical to catch errors and exceptions during execution of a service rule so that they can be communicated to the client application cleanly. Best practice requires you to configure clipboard property values to communicate service errors to the calling application.
Many service types, including SOAP, have an exceptions or faults tab where you can define what the application does when a service error or exception is encountered. When the service encounters a processing error, and a condition evaluates to true, the application returns a defined error message to the calling application. The following conditions are available for defining an error response message.
|When||The specified when rule returns true.|
|Queue When||If the specified when rule returns true, the request is queued and a Pega-specific SOAP fault that includes the queue ID of the request is returned. Useful when processing errors are due to temporary issues, such as item locking.|
|Mapping Error||An error occurs while mapping incoming data from the request message to the clipboard.|
|Security Error||Authentication fails.|
|Service Error||A valid instance of the service activity cannot be found.|
If the mapping, security, and service errors are not defined, the system returns standard exceptions, such as an AuthenticationException if the supplied credentials are not valid.
For more information about configuring the Fault tab of a service, consult the Help topic Service SOAP form - Completing the Faults tab.