Events, Activities, Tasks and Subprocesses - C3 BPM

Events, Activities, Tasks and Subprocesses – C3 BPM
Events
There are three main events within business process modeling: start events, intermediate events, and
end events. Events describe something that happens. They must either catch the result of the process
or throw the results of the business flow. These two classes of events are known as "throwing" and
"catching."
Start Event
Start events are exactly what they sound like. Each process must begin with a
starting event. If the process is catching information (for example, receiving an
email),
Start event catching example

Intermediate Event
An intermediate event is any event that occurs between a start and an end event. The
intermediate event circle has a double line, and the event can catch or throw
information. Connecting objects indicate the directional flow, like whether the event
is catching or throwing. Users can find event types for intermediate events by using
the pop-up context panel that appears when you add a new BPMN shape to the
canvas.
Intermediate event catching example Intermediate event throwing example
End Event
Lastly, end events are styled with a single thick black line to indicate that it’s an end
event. End events are always thrown because there is no process to catch after the
final event.
End event throwing example
Activities
Activities are the building blocks of the BPMN 2.0 specification. Without activities, there can't be a
business process because nothing is getting done. Activities are represented as symbols that
combine with other BPMN object types to tell a larger story about the business flow. All activities
have the same rounded-corner rectangle shape. Activities are separated into 4 categories: tasks, sub-
processes, transactions, and call activities.
Tasks
A task is the most granular level of a process. There are many types of symbols
that signify the various task types.
Normal Task - A normal task is a single action that occurs in a business

process, i.e. mailing a letter.
Normal Task Example - A normal task example would be any of the tasks in
the example below. If you want to write a business process model that diagrams
the process of writing a paper, it might look something like this.
This business process model example demonstrates the tasks of brainstorming, writing a first draft,
editing the draft and presenting a final draft.
Loop Task – a loop task is a task that repeats over and over again in sequence.
Loop Task Example - If you want to incorporate a loop task example, you
might change the editing paper task to a loop task. This allows you to signal
your intention to repeatedly edit the document before submitting the final
draft.
In order to explain the conditions of the loop task you might also add an
annotation saying that you will continue to edit the paper until the teacher
says the current draft will get an A.
Multiple Instance Task – a multiple instance task is a task that happens multiple times. These
instances can happen in parallel or sequentially.
Multiple Instance Task Example
Continuing our paper writing process from above, let's

say that you were able to get several friends to look over
your draft and give you feedback on possible changes.
You would want to make it a multiple instance task
instead of a loop task. This indicates that you gave a draft to 3 different people, and that all 3 will
get back to you at the same time.
The above example shows multiple edits happening simultaneously, but you could easily show the
multiple edits happening sequentially.
Compensation Task
A compensation task is a specialized version of a task that only happens when

another specific task occurs previously. A compensation loop task is a task
that happens over and over in sequential order and involves some sort of
compensation.
Compensation Task Example - Your friends probably won't work for free, so
you can add a compensation task by paying them to edit your paper.
Compensation Loop Task
Compensation Loop Task Examples
A multiple instance compensation task would be paying each of the 3

editors. If you only had 1 editor and you paid him/her each time an edit
was made, that would be a looping compensation task.
Task Types
Business Rule Task Type
Business rule is an explicit type that was added with BPMN 2.0. Business
rules are specific types of services maintained by a business working group,
rather than an IT group. The rule shape is used to represent the
implementation of a business rule.
Manual Task Type
A manual task type is used wherever a part of a process has to be executed

manually. It can be executed without any outside help or application; for
example, loading a truck with product.
Receive Task Type
A receive task indicates that the process is relying on an incoming message

from a third party. Upon receiving a message, the task has been performed.
Script Task Type
Script tasks are executed by a business process engine. The script is written in
a language that the engine can parse, which is JavaScript in many instances.
Send Task Type
A send task is a task that sends a message to another process or lane. The
task is completed once the message is sent.
Service Task Type
A service task is any task that uses an automated application or web service
to complete the task.
User Task Type
Indicates that the task is being performed by a person and cannot be easily
broken down into simpler tasks.
Sub-Process
Even though the task and sub-process shapes are similar (a dotted line
delineates an event sub-process), an event sub-process represents one
that was triggered by an event from the parent process.
Subprocess types
Unlike a task, a subprocess represents multiple tasks that work together to perform some important
part of a total process. Whenever you see a task shape with a plus at the bottom, that’s a contracted
view of a subprocess. There are different types of subprocesses, so we’ll go through the various
symbols and what they mean.
Loop
The first sub-process type is a loop. This means that a subprocess repeats
itself in sequence. It is treated similarly to a loop task when in a collapsed
view.
Multi instance
A multiple instance subprocess is a subprocess that can run in
concurrence with other identical subprocesses. It is treated similarly to
a multi instance task when in a collapsed view.
Compensation
A compensation subprocess is typically reserved for a group of tasks that

describe some part of the compensation method, whether that's accounts
receivable or accounts payable.
Ad hoc
An ad hoc subprocess is a group of tasks that exist for the sole purpose of
completing some part of a process. For example, an ad hoc subprocess
might deal with one particular vendor who has a unique payment system.
Event Subprocess –is included in this section as well since it's a

specialized type of subprocess. Event subprocesses are used to describe
events that happen within the boundary of a subprocess. Event
subprocess are triggered by a start event, and they differ from other
subprocesses because they are not part of the regular flow. They’re self-
contained and occur within the context of a subprocess. There are 2 types
of event subprocesses: interrupting and non-interrupting. An interrupting
event subprocess interrupts the normal business flow, while a non-interrupting subprocess start
event does not. For example, if an order on a website is cancelled, the process is interrupted and all
website activity is terminated. But if the customer simply checks the shopping cart so see which
items are reserved for purchase, the process is non-interrupting.

Events, Activities, Tasks and Subprocesses - C3 BPM

Uploaded by

Copyright:

Available Formats

Events, Activities, Tasks and Subprocesses - C3 BPM

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Events, Activities, Tasks and Subprocesses - C3 BPM

Uploaded by

Copyright:

Available Formats

Events, Activities, Tasks and Subprocesses – C3 BPM

Start event catching example

Intermediate event catching example Intermediate event throwing example

End event throwing example

Normal Task - A normal task is a single action that occurs in a business

Multiple Instance Task Example

Continuing our paper writing process from above, let's

A compensation task is a specialized version of a task that only happens when

Compensation Loop Task

Compensation Loop Task Examples

A multiple instance compensation task would be paying each of the 3

Business Rule Task Type

Manual Task Type

A manual task type is used wherever a part of a process has to be executed

A receive task indicates that the process is relying on an incoming message

Script Task Type

Send Task Type

Service Task Type

User Task Type

A compensation subprocess is typically reserved for a group of tasks that

Event Subprocess –is included in this section as well since it's a

You might also like