Task

Intro

A task is an atomic activity within a process. In BPMN, it shares the rounded rectangle shape with sub‑processes and is used when work is not decomposed further.

Key points:

• Represents a single unit of work.
• May be performed by a user, a system, or both.
• Common use cases across EA/BPM/Data/App/Tech include user tasks, service tasks, and script tasks.
• Pitfall: modeling large chunks as one task, hiding needed detail.

Examples:

• User task: approve request.
• Service task: call payment API.
• Script task: transform data before saving.

In practice:

Decompose until each task is clear, testable, and assignable; avoid over‑granularity.

Related terms: Sub Process; BPMN; Process

FAQs:

Q: Can tasks have boundary events?
A: Yes; to handle timeouts, errors, or escalations.

Q: When to use a sub‑process instead?
A: When grouping multiple related tasks improves clarity or reuse.

‍