BPMN 1.1 MAILINGLIST Avatar
  1. OMG Issue

BPMN11 — Provide ExpressionLanguage attribute for the element Expression

  • Key: BPMN11-54
  • Legacy Issue Number: 9937
  • Status: closed  
  • Source: oose Innovative Informatik eG ( Markus Klink)
  • Summary:

    BPMN expressions are defined as:

    "An Expression MUST be entered to provide a mathematical expression to be either tested as True or False or to be evaluated to update the value of Properties (e.g., assignment)."

    whereas the diagram has an ExpressionLanguage attribute which is defined as:

    "A Language MAY be provided so that the syntax of expressions used in the Diagram can be understood. "

    Expressions are used either in the boolean sense (e.g. as Conditions for Conditional flow) or in the imperative sense where expressions are evaulated to update values (e.g. as used in the element Assignment). Hence this can be conflicting with the default settings by the diagram, and is in conflict with the notion of BPMN as a human readable language it is suggested that each expression may contain an expressionlanguage field of type String. While BPMN will still mandate that certain expressions must deliver specific results, it will not standardize the expressionlanguages capable of achieving this goal.

  • Reported: BPMN 1.0b1 — Mon, 17 Jul 2006 04:00 GMT
  • Disposition: Resolved — BPMN 1.1
  • Disposition Summary:

    see above

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