Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-4747

DMN 1.1 Issue

XMLWordPrintable

      Open Problems / Concerns (will be addressed by menge)

      • We cannot set expression language everywhere (cf. tUnaryTest) it needs to be possile to use an arbitrary expression language everywhere
      • Comma seperated lists of expressions (inputValues, outputValues)
      • Extension Elements missing

      Changes

      • HTML Table style
      • Href => Qname
      • allowed values => input values & output values
      • drop itemDefinitions
      • Clarify: type references "camunda:string" or "feel:string"

      New Features

      • default output

      –

      Notes for sebastian.menski

      • priority
      • output order
      • output values
      • just do it

        This is the controller panel for Smart Panels app

            [CAM-4747] DMN 1.1 Issue

            Sebastian Menski added a comment -

            Proposal for change of name attribute

            If we are lucky and http://solitaire.omg.org/browse/DMN11-154 will be accepted we lose the name attribute and gain a label attribute instead. I would propose following
            usage:

            1. Our current input and output clause names should become labels
            2. We use the name of the output clause for our output mapping instead of camunda:output
            3. We may rename the camunda:output of the input clause to something more clear

            Current DMN table:

            Input Clause Name Output Clause Name
            Input Expression camunda:output
            Type/Allowed Values Type/Allowed Values
            Input Entry Output Entry

            DMN 1.1 table:

            Input Clause Label Output Clause Label
            Input Expression Output Clause Name
            Type/Input Values Type/Output Values
            Input Entry Output Entry

            Sebastian Menski added a comment - Proposal for change of name attribute If we are lucky and http://solitaire.omg.org/browse/DMN11-154 will be accepted we lose the name attribute and gain a label attribute instead. I would propose following usage: Our current input and output clause names should become labels We use the name of the output clause for our output mapping instead of camunda:output We may rename the camunda:output of the input clause to something more clear Current DMN table: Input Clause Name Output Clause Name Input Expression camunda:output Type/Allowed Values Type/Allowed Values Input Entry Output Entry DMN 1.1 table: Input Clause Label Output Clause Label Input Expression Output Clause Name Type/Input Values Type/Output Values Input Entry Output Entry

              sebastian.menski Sebastian Menski
              meyer Daniel Meyer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: