CMMN 1.1 RTF Avatar
  1. OMG Issue

CR — Ambiguous OnPart references for cross-stage-boundary plan items

  • Key: CR-14
  • Legacy Issue Number: 19496
  • Status: closed  
  • Source: ( Thijs Petter)
  • Summary:

    Suppose we have the following case definition, expressed in XML.
    <case name="stages" xmlns="">
    <caseRoles />
    <input />
    <output />
    <caseFileModel />
    <casePlanModel name="casePlan">
    <planItem name="Stage1" definitionRef="Stage" />
    <planItem name="Stage2" definitionRef="Stage" />

    <planItem name="Milestone1" definitionRef="Milestone" entryCriteriaRefs="Task1Completed" />
    <sentry name="Task1Completed">
    <planItemOnPart sourceRef="Task1">

    <stage name="Stage">
    <planItem name="Task1" definitionRef="Task" />
    <milestone name="Milestone" />
    <humanTask name="Task" />

    Within this case, we have a Milestone1, with an entry criterion referring to Sentry called Task1Completed.
    Task1 is a plan item within Stage, hence can be referenced from the sentry.

    At runtime, however, there will be 2 instances of Task1: one in Stage1, and another within Stage2 (as both have the same stage definition).

    The specification does not say anything as to which instance plan item the sentry refers, making it ambiguous. Well ... in page 26, at SentryRef, the specification says that the sentry ref must refer to a plan item within the same stage. However, this is conflicting with the image on page 64, as indicated in the issue logged as "CMMN spec inconsistent with respect to Sentry dependencies crossing Stage boundaries"

  • Reported: CMMN 1.0 — Mon, 30 Jun 2014 04:00 GMT
  • Disposition: Duplicate or Merged — CMMN 1.1
  • Disposition Summary:

    Duplicate of issue CR-7


  • Updated: Tue, 29 Mar 2016 15:06 GMT