Академический Документы
Профессиональный Документы
Культура Документы
Send Message
Throw Exception
Wait for x amount of time
Two Types
Throw : Produced by the Process ( End Events & some
Intermediate Events fall under this category)
Message
Start
Event
Message End
Event
Start event:
Handle SMS
Transcribe
Fax
Process
Request
Receive SMS
Fax arrived
Receive E-Mail
Parse EMail
Initiate Task
Initiate Task
Receive Task
Receive Task
End event:
Example that shows combination of Gateways and multiple End Events. Only one
of the Message End Event is reached in this example.
Another
Message
End Event
Message End
Event
Error End
Event
When an Error End Event is reached, the process or the sub-process terminates
even if all other parallel paths are still active.
Receive
Reply
Some Intermediate Events are of type Catch and some of type Throw.
Throw symbols are shaded while Catch symbols are not.
The Catch Events wait or block for appropriate signals while the Throw events
proceed after throwing the signal.
The execution is stalled and does not proceed until the event
arrives.
catch Timer
Intermediate Event .
Receive Quote
Response from
Customer
catch
Message
Intermediate
Event
Send Quote to
Customer
throw
Message
Intermediate
Event
Receive Task.
Receive Task in the middle of the process is the same as the Message Intermediate Event of
catch type .
Receive Task at the beginning of the process is the same as the Message Start Event.
Send Task at the end of the process is the same as the Message End Event.
Send Task in the middle of the process is the same as the Message Intermediate Event of throw
type.
Send Task.
Catch Timer
Intermediate Event
Send Quote to
Customer
Gateway
XOR Event
attached Error Event Catches error thrown by the activity or sub-process. Errors
have unique identifiers. There can be multiple attached Error events for catching the
various types of errors being thrown by the activity or sub-process.
attached Timer Event - Catches time-out exceptions (specialized type of error)
thrown by the activity or sub-process.
attached Message Event Catches Message sent by another participant or
process.
boundary.
They are of type Catch and referred to as Boundary or Attached
Events.
They have only 1 outgoing sequence flow that leads to Event Handling
path.
Useful for Exception and Interruption Handling.
Types
The Error and Timer boundary events are triggered if the activity
to which they are attached is not yet completed.
Exception Paths
Exception Path
Boundary Error
Event attached to
sub-process.
Exception Path
The Message, Error, Timer boundary events are not active if the activity
(task/subprocess) to which they are attached is completed.
The Exception path is taken and the Cancel Order step is executed.
The Fulfill Order sub-process listens for the Cancel Order Message
on a separate thread. The Boundary events do not block the step to
which they are attached while listening.
Message
Boundary
Event
Cancel
Order
Message
Main process
catches the
error and
follows the
exception
path.
Subprocess throws an
Order Canceled error.
Just like boundary events it listens for external signals but instead of
transferring outside of the activity it runs within the activity (process /
subprocess).
Process
ends
Error Start
Event
Event subprocess.
Event Subprocess
with None End Event.
Normal flow after
subprocess step is
taken.
corresponding
boundary event that
catches the Cancel
Order error.
Exception
Path
There can be many Event Subprocesses but only one gets activated.
In the case of Event Subprocess with None End Event, the normal flow after the subprocess step
is executed.
In the case of Event Subprocess that has an Error or Message End Event, the corresponding
boundary catch event attached to the subprocess boundary is triggered and the event handling
path is taken.
Error Start
Event
Message
Start Event
Normal
Path
Implementation of Events
Signal Event
Timer Event
Receive a message.
Receive Task can either initiate the
conversation (receive-reply) or reply
to a conversation (request-response).
It can also initiate the process
Receive Task as initiator:
Choose the initiate option.
You can either create a Service
interface on the fly (or)
Browse for an existing Service or
Process from the Business
Catalog.
Receive Task as reply:
Choose the Continues option.
It will show a list of Send Tasks
in the same process.
The Receive Task has only output
arguments.
Loop Marker
Markers or icons can be added to Tasks or Subprocesses to illustrate further semantic context
around Task behavior.
Looping
Subprocess
Parallel Multi-instance
subprocess
Sequential Multi-instance
subprocess
Marker
Multi-instance