Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 6 Working with Events : Throw and Catch Error Events

Throw and Catch Error Events
An error event attached to a task boundary can be set to catch any error, or errors thrown by the task to which it is attached.
For example:
When attached to a reusable or embedded sub-process task, the event can catch errors thrown by any of the following:
Configuring Error Events
Error events are configured in the Properties view:
For a catch error event, you can do the following:
Catch All Errors  (default) Catches any error thrown by any event.
Catch Named Errors  To do this, click Select Error and select the Select Unspecific Error By Name Only checkbox. The dialog lists the catchable error codes. Select the error codes that you want to catch. This configures the event to catch the selected error from any activity.
Catch Specific Errors from Specific Activities  Click Select Error and deselect the Select Unspecific Error By Name Only checkbox. The dialog lists events and activities that throw error codes. Expand the desired event or activity to catch a specific error thrown by a specific activity. For example:
Catch Specific WSDL Fault  WSDL faults are caught in the same ways as other errors (either named WSDL faults, or specific errors from a specific service task). For example:
In this example, the catch error event is attached to the service task. The error is thrown by a process in a different project (see Creating References in the Project Properties).
Fixing Invalid Error Events
After configuring a catch error event, the event that throws the error code is deleted, invalidating the catch error event as shown in the Properties view.
 
Other causes of invalid error events include:
To fix the error event, click Select Error. If possible TIBCO Business Studio identifies the closest match to the originally selected error code. Select an error code and click OK.
Mapping Error Data
Click the Map From Error tab to map error parameters to process data.
For example:
The process data available on the right side of the tab is either all data or a subset of data as specified on the selection on Interface tab.
The content of the left side of the Map From Error tab depends on the configuration of the General tab:
Catch All / Catch Named Errors  Only the automatically provided error code can be used for mapping as shown in the previous example. Typically, this error code is mapped to a process text data field or parameter for display to the user. At run time, the text data field or parameters is populated with the error code name when the error is caught.
Catch Specific Error Thrown By Sub-Process End Error Event  All parameters with a mode of Out or In/Out that are associated with the throw error end event (on the Interface tab) are displayed for mapping:
Catch Specific WSDL Fault  WSDL fault message parameters are displayed on the left side and can be mapped as normal.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved