Throw
|
Allows you to create an error along a specific BP path.
|
Terminate Process
|
Allows you to terminate an entire BP before it reaches an end node.
|
Intermediate Events
|
Provides a dropdown menu that lists the following elements. These elements
handle exceptions that might occur during a BP or that compensate for exceptions
that do occur.
|
Timer
Event
|
Specifies either a duration-based or deadline-based condition that determines
which branch a BP takes. A duration-based condition is satisfied after a specified
elapsed time. A deadline-based condition is satisfied at a specified time.
A timer event is used in conjunction with an event-based decision.
|
Message Event
|
Similar to a receive activity, but occurring only in the middle of a
process and only with event-based decisions. Each message event can be a different
message.
|
Catch Named Exception
|
Handles named exceptions. Each automated (backend) system or web service
can publish their possible error codes (for instance, fault 15 is “bad
data”), and those codes can be mapped to exception handlers. Each exception
handler is connected to the Scope that surrounds one or more steps in a BP.
The components within that Scope throw the exceptions when errors occur. The
exception handler automatically initiates the appropriate process to handle
the problem.
|
Catch All Exceptions
|
Handles un-named exceptions that occur in
a Scope or across a BP.
|
Compensation Handler
|
Allows you to design the process and circumstances in which compensation
takes place. This used when a part of a BP fails and requires a rollback of
upstream activities (such as money has to be returned to the customer account).
Automatically, upstream steps in the BP are notified that the failure has
occurred and certain transactions need to be reversed, sometimes in a sequential
order.
|