Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-7719

UX design/mocks: Proposal for interacting with process instance nodes

    Details

    • Sprint:
      2018 Week 33-35, 2018 Week 36-38, 2018 Week 39-41
    • Story Points:
      3
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      Based on the findings of JBPM-7496 and JBPM-7631, create wireframes for a proposed designed.

      The main requirement is around the administration capabilities for certain nodes, node instances and timer instances. So adding interaction to the actual nodes using a modeless overlay sounds like a good fit.

      When selecting a node, there is only basic information available like name, id and type. Some basic nodes won't have a name, like start node, split node, etc.
      The only operation available for a node is "Trigger", which means starting a new node instance.

      For each node selected, you have a list of node instance or times instances associated.
      The data available for a node instance and operations:
      Data:

      • id
      • name
      • work item id
      • start date
      • completed
      • sla compliance
        Operations
      • Cancel node instance
      • Re-trigger node instance

      As for timers we've:

      • name
      • id
      • activation time
      • last-fire-time
      • next-fire-time
      • delay
      • period
      • repeat limit

      Operations

      • update timer - by process instance id and timer id - updates timer expiration of active timer. It updates the timer taking into consideration time elapsed since the timer was scheduled. For example: In case timer was initially created with delay of 1 hour and after 30 min it's decided to update it to 2 hours it will then expire in 1,5 hour from the time it was updated. Allows to update

      delay - duration after timer expires
      period - interval between timer expiration - applicable only for cycle timers
      repeat limit - limit the expiration to given number - applicable only for cycle timers

      • update timer relative to current time - by process instance id and timer id - similar to regular update time but the update is relative to the current time - for example: In case timer was initially created with delay of 1 hour and after 30 min it's decided to update it to 2 hours it will then expire in 2 hours from the time it was updated.

      Verification conditions:

      • Document research/review findings.

        Gliffy Diagrams

          Marvel

          Marvel Prototype Add-On for Confluence Server written by David Simpson.

            Attachments

            1. Instance-interaction2.png
              Instance-interaction2.png
              149 kB
            2. Instance-interaction4.png
              Instance-interaction4.png
              166 kB
            3. Instance-interactions.png
              Instance-interactions.png
              123 kB
            4. instance-interactions5.png
              instance-interactions5.png
              196 kB
            5. instance-interactions6.png
              instance-interactions6.png
              173 kB
            6. instance-interactions8.png
              instance-interactions8.png
              133 kB
            7. instance-interactions9b.png
              instance-interactions9b.png
              140 kB
            8. node_selecton.png
              node_selecton.png
              59 kB
            9. Zoom1@2x.png
              Zoom1@2x.png
              239 kB
            10. Zoom2@2x.png
              Zoom2@2x.png
              258 kB

              Issue Links

                Activity

                  People

                  • Assignee:
                    uxdlc Elizabeth Clayton
                    Reporter:
                    uxdlc Elizabeth Clayton
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    5 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: