Best BPMN Practices

Home

Themes
- Themes
- Default
- Bootswatch Themes
- Cerulean
- Cosmo
- Cyborg
- Darkly
- Flatly
- Journal
- Lumen
- Paper
- Readable
- Sandstone
- Simplex
- Solar
- Slate
- Spacelab
- Superhero
- United
- Yeti

Translations of this page

Register Log In

You are here
Home
Welcome to BPMNbox

Sidebar

Chapters

Rules
Tools
Glossary
Recent Changes

Top-10

Check subprocess result on exit (5)
Use collapsed subprocesses (3)
Make parallel merge explicit (3)
Rules of "Good" BPMN (3)
Glossary (3)
A subprocess and a control branch may be used as an alternative to the attached event (2)
Avoid double negations (2)
End event name should answer the question "how did the case end?" (2)
Model handover by a sequence flow (2)
Bizagi Modeler (2)

Tags

attached_event collaboration conditional_event conditional_flow default_flow end_event error_event event event_gateway exclusive_gateway flow gateway happy_path inclusive_gateway intermediate_event lane legacy link_event loop message_event message_flow mixed_gateway naming parallel_gateway pool process sequence_flow start_event subprocess task terminate_event timer_event visual_style

Help

Tips for beginners
Formatting Syntax
Hints on good style

Resources

BPMN 2.0.2 Specification

Show pagesource
Old revisions
Backlinks
Copy this page
Back to top

Share via
- Share via...
- Twitter
- LinkedIn
- Facebook
- Pinterest
- Telegram
- WhatsApp
- Yammer
- Reddit
- Teams
Recent Changes
Send via e-Mail
Print
Permalink

This is an old revision of the document!

Welcom to BPMNbox

BPMNbox is the collection of best BPMN practices, patterns and antipatterns.

Last modified: 2023-09-10 15:20
by Anatoly Belaychuk

Except where otherwise noted, content on this wiki is licensed under the following license:
CC Attribution 4.0 International