Information Technology Reference
In-Depth Information
Boundary events
Boundary events are a very practical combination of two flow objects, activities, and
events. When you assign an intermediate catch event to the border of an activity box, you
determine events specific for that activity only. They are very useful for controlling the
flow of tasks and subprocesses alike. The following diagram shows a few examples:
As the preceding diagram shows, you can capture escalations, errors, signals, and many
other types of events being sent from an activity and divert flow accordingly. You can even
have multiple boundary events on a single activity box. In the case of the preceding dia-
gram, depending on whether Activity C sends a signal before or after a specific amount of
time passes since the activity started, the flow might be diverted to two different steps.
The activity can still have a regular outgoing flow. For the first case in the preceding dia-
gram, if no escalation is sent from Activity A , the process could continue through a se-
quence flow attached to the activity box directly.
Boundary events are a good way to manage alternate flows. Like all other components that
add complexity to our processes, we must make sure that we don't make the process too
complicated to be easily maintained.
Search WWH ::




Custom Search