CR — CMMN spec inconsistent with respect to Sentry dependencies crossing Stage boundaries

Table 5.22 says, with respect to the sourceRef attribute: "SourceRef represents a PlanItem that MUST be contained by the same PlanFragment (or Stage) that also contains theSentry that contains the PlanItemOnPart."

This implies that sentry-based dependency cannot cross stage boundaries, which is in conflict with what is suggested by the claims management example in Figure 6.63.

The solution should be to remove the constraining text from Table 5.22.

A similar constraint is found (and must be removed) on page 32 in the section 5.4.9.2 DiscretionaryItem

"When entryCriteriaRefs or exitCriteriaRefs of a DiscretionaryItem have OnParts that are PlanItem
OnParts, these OnParts MUST have a sourceRef that is contained
• in the Stage that also contains the PlanningTable that contains the DiscretionaryItem, directly or recursively
through a hierarchy of PlanningTables, or
• in the Stage that also contains the HumanTask that has the PlanningTable that contains the DiscretionaryItem,
directly or recursively through a hierarchy of PlanningTables."

Allow Sentry to cross Stage boundaries for PlanItems only (not for Discretionary Items)

• We'd like to allow sentries to cross Stage boundaries