Which Edit Style to Choose: BPMN-Centric or BPEL-Centric?

ActiveVOS Designer User’s Guide

Which Edit Style to Choose: BPMN-Centric or BPEL-Centric?

Both BPMN and BPEL edit styles generate 100% validated, executable BPEL XML code. Both styles are diagramming notations for process descriptions. You can choose which visual style is easier for you and your team.

Highlights of BPMN-Centric

The edit style uses standard BPMN terminology
The ActiveVOS extension activity, break, can be implemented with a terminate activity within a scope, for Each or while structured activity. The break implementation allows breaking out of the closest scope or loop.
The ActiveVOS extension activity, continue, is not supported because no notation in BPMN has the exact Continue semantics
The error catch event is used for the catch and catch all fault handlers
The error throw event is used for the throw and rethrow activities
Annotations include icons for data objects, collections and stores
An annotation can be linked to an activity
A control flow structure, like a Conditional Pattern or Repeat Pattern, can be ungrouped into separate activities.

Highlights of BPEL-Centric

The style uses BPEL terminology for constructs and includes some common BPMN constructs. Not all BPEL constructs are visible. Some are hidden in order to produce a cleaner, clearer diagram.
The style includes the ActiveVOS extension activities break and continue
Catch and catch all fault handlers are represented separately
Throw and rethrow activities are represented separately