1. OMG Issue

BPMN11 — BPMN Task Attribute "TaskType" Value-related Message Flow Restrictions

  • Key: BPMN11-86
  • Legacy Issue Number: 10657
  • Status: closed  
  • Source: Escape Velocity ( Bob Daniel)
  • Summary:

    . If a task has the TaskType value set to “None”, the task is not allowed to have incoming or outgoing message flows. This restriction should be removed. “None” would logically be interpreted as “not defined”, so the message flow restriction would be overly constraining—one might be early in an analysis and the type of task not yet defined, though a message flow in/out specified. (Note that the ProcessType attribute on Process also has the legal value “None”, and in that case the definition parenthetically states that “None” means “not defined”. Further, no restriction is placed on message flow.)

    2. The message flow connect rules in Table 8.5 do not reflect the TaskType value message flow restrictions otherwise defined in Table B.64. An annotation (footnote) should be made to the table to note the restrictions.

  • Reported: BPMN 1.0 — Thu, 8 Feb 2007 05:00 GMT
  • Disposition: Resolved — BPMN 1.1
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:57 GMT