hey business process modeling notation activity is a task

A throwing intermediate event result must be either Message, Signal, Escalation, Link, or Compensation. An intermediate event with outgoing message flow must be throwing type with Message trigger. An intermediate event with incoming message flow must be catching type with Message trigger. An Escalation boundary event on a subprocess requires a matching Escalation throw event. An Error boundary event cannot be non-interrupting. An Error boundary event on a subprocess requires a matching Error throw event. A boundary event cannot have incoming sequence flow. A boundary event trigger must be either Message, Timer, Signal, Error, Escalation, Conditional, Cancel, or Compensation. A boundary event must have an outgoing sequence flow.

A start event in a subprocess must have a None trigger. A start event cannot have an Error trigger. A start event with incoming message flow must have a Message trigger. A start event cannot have an outgoing message flow. A start event cannot have an incoming sequence flow. All flow objects other than end events and compensating activities must have an outgoing sequence flow, if the process level includes any start or end events. All flow objects other than start events, boundary events, and compensating activities must have an incoming sequence flow, if the process level includes any start or end events.

Note: for now, this list assumes the model includes no event subprocesses. All are implemented in my Method and Style Validation tool. As promised, here is my first cut at a single list of the rules of BPMN, both the official rules from the spec (prefixed BPMN) and my “method and style” rules (prefixed Style).

Hey business process modeling notation activity is a task