DMN 1.2 RTF Avatar
  1. OMG Issue

DMN12 — Decision Service Cannot be Shown in DRD

  • Key: DMN12-136
  • Status: closed  
  • Source: Sapiens Decision NA ( Mr. Gil Ronen)
  • Summary:

    The DMN Element Metamodel (Fig. 18 in the specification) shows that Decision Services are NOT a subclass of DRGElement. The definition of the DRD requires its components to be DRGElement (“A Decision Requirements Diagram (DRD) is the diagrammatic representation of one or more instances of DRGElement and their information, knowledge and authority requirement relations “). I think the Decision Service should be part of the DRD, especially if it is a callable unit within the DRD (that is, can be linked to a BKM as per DMN12-10/DMN12-135).

  • Reported: DMN 1.1 — Thu, 23 Feb 2017 13:16 GMT
  • Disposition: Duplicate or Merged — DMN 1.2
  • Disposition Summary:

    fixed by invocable decision service DMN12-10

    In the current MM (e.g. see the Ballot13 convenience doc) the DecisionService class extends Invocable which extends DRGElement.

  • Updated: Wed, 3 Oct 2018 14:17 GMT