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

Stunner - Morphing & rule evaluations issues

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 7.13.0.Final
    • None
    • Designer
    • NEW
    • NEW
    • Hide

      Consider the following scenario:

      • Two nodes A and B, which are being connected by an edge E
      • B can morph into C
      • E allows connections between A-B, but does NOT allow A-C
        So the current diagram looks like: 
        [A] --(E)--> [B]

        At this point, once clicking on B, it's morph menu appears (bottom), and the user is able to morph it into C, which results in an invalid state, as the connection A to C it not allowed

      Show
      Consider the following scenario: Two nodes A and B, which are being connected by an edge E B can morph into C E allows connections between A-B, but does NOT allow A-C So the current diagram looks like: [A] --(E)--> [B] At this point, once clicking on B, it's morph menu appears (bottom), and the user is able to morph it into C, which results in an invalid state, as the connection A to C it not allowed
    • 2018 Week 23-24

      It's allowed to morph nodes into different types, but it could result in some invalid diagram state. At least it has been reproduced by producing an invalid connection context, see steps to reproduce.

      It implies checks/fixes for:

      • The contextual morph menu(bottom() - It should be just displaying the allowed target types for the actual diagram state, making this way not possible to end up in some rule evaluation failed
      • Morphing (core) commands -> check/fix the actual implementations - those should checking all available rule contexts before execution

              tdolphin-1 Tiago Dolphine (Inactive)
              romartin@redhat.com Roger Martinez
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: