Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-3731

DMN UX - More info overlaid on models.

    XMLWordPrintable

Details

    Description

      As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.

      Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.

      Attachments

        1. colors.png
          colors.png
          213 kB
        2. download.png
          download.png
          196 kB
        3. download (1).png
          download (1).png
          140 kB
        4. multi.gif
          multi.gif
          395 kB
        5. Screen Shot 2019-05-29 at 2.49.21 PM.png
          Screen Shot 2019-05-29 at 2.49.21 PM.png
          42 kB
        6. single.gif
          single.gif
          516 kB
        7. tmp.png
          tmp.png
          195 kB
        8. 屏幕快照 2019-06-11 下午3.02.19.png
          屏幕快照 2019-06-11 下午3.02.19.png
          208 kB
        9. 屏幕快照 2019-06-11 下午3.10.26.png
          屏幕快照 2019-06-11 下午3.10.26.png
          230 kB

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. DROOLS-3742 Implement Test scenario coverage report for DMN

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users JBPM-8257 Configurable Color coding for executed flows in Process model

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Story - Used to indicate the smallest unit of work for a team to complete and is end user-facing. Created by Jira Software - do not edit or delete. DROOLS-4257 DMN UX - overlay information about an entire simulation execution

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Story - Used to indicate the smallest unit of work for a team to complete and is end user-facing. Created by Jira Software - do not edit or delete. DROOLS-4258 DMN UX - overlay information about a single scenario run

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBPM-7719 UX design/mocks: Proposal for interacting with process instance nodes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. DROOLS-3387 Update interaction behavior to align with DMN/Stunner.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. DROOLS-3953 DMN UX - overlay validation error reporting

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DROOLS-3657 [DMN Designer] Highlight invalid DRGElements

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              tzhu@redhat.com Tao Zhu (Inactive)
              rhn-support-eclayton Elizabeth Clayton
              Jozef Marko Jozef Marko
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: