We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-12910 Integrate Scala DMN Engine
  3. CAM-12922

In DMN Wrapper, provide replacement for DmnTransformListener

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • scala-dmn
    • None

      AT

      • Identify proper replacement for DmnTransformListener
        • Listener could be called in wrapper implementation of DmnEngine#parse

      Reasoning

      • The DmnTransformListener is present in the legacy DMN Engine and can be seen analogous to the BPMNParseListener in the Process Engine
      • It provides the parsed result of the DMN model
      • It makes migrating from the legacy DMN Engine to the Scala DMN Engine more smooth

      Scope/Solution Ideas

      • Minimum: Notify listener after decision was parsed => Stop supporting more fine-grained listener methods of notation elements (e.g., table input, etc.)
      • Maximum: Minimum + notify listener after table input, table output, table rule, and drg was parsed  => this is the status quo with the legacy DMN Engine
        • Traverse parsed result to check if respective notation elements are present

      See https://docs.google.com/document/d/1fvp2qf75W7VBSFjfHVz3iRN4Ynq349R6qtq3eP62opw/edit#bookmark=id.fsntanj8mayn

        This is the controller panel for Smart Panels app

            Loading...
            Uploaded image for project: 'camunda BPM'
            1. camunda BPM
            2. CAM-12910 Integrate Scala DMN Engine
            3. CAM-12922

            In DMN Wrapper, provide replacement for DmnTransformListener

              • Icon: Sub-task Sub-task
              • Resolution: Unresolved
              • Icon: L3 - Default L3 - Default
              • None
              • None
              • scala-dmn
              • None

                AT

                • Identify proper replacement for DmnTransformListener
                  • Listener could be called in wrapper implementation of DmnEngine#parse

                Reasoning

                • The DmnTransformListener is present in the legacy DMN Engine and can be seen analogous to the BPMNParseListener in the Process Engine
                • It provides the parsed result of the DMN model
                • It makes migrating from the legacy DMN Engine to the Scala DMN Engine more smooth

                Scope/Solution Ideas

                • Minimum: Notify listener after decision was parsed => Stop supporting more fine-grained listener methods of notation elements (e.g., table input, etc.)
                • Maximum: Minimum + notify listener after table input, table output, table rule, and drg was parsed  => this is the status quo with the legacy DMN Engine
                  • Traverse parsed result to check if respective notation elements are present

                See https://docs.google.com/document/d/1fvp2qf75W7VBSFjfHVz3iRN4Ynq349R6qtq3eP62opw/edit#bookmark=id.fsntanj8mayn

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        tassilo.weidner Tassilo Weidner
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:

                              Unassigned Unassigned
                              tassilo.weidner Tassilo Weidner
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              2 Start watching this issue

                                Created:
                                Updated: