Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1792

Retrigger on node in the process diagram produces two new node instances.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.3.0.GA
    • 7.3.0.GA
    • jBPM Runtime UI
    • None
    • CR1
    • Hide

      1. Import the evaluation example.
      2. Deploy and start the process.
      3. Open the process instance, go to tab diagram.
      4. Select the active node on the left and retrigger.
      Expected result: A new node instance with id raised by one occurs.
      Actual result: Two new node instances occur.

      Show
      1. Import the evaluation example. 2. Deploy and start the process. 3. Open the process instance, go to tab diagram. 4. Select the active node on the left and retrigger. Expected result: A new node instance with id raised by one occurs. Actual result: Two new node instances occur.

    Description

      When retriggering a node instance in the Process Diagram, two new node appear (except of one). One with the same id as the original and one with the Id raised by 1. (see the attached video).

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBPM-8087 Retrigger on node in the process diagram produces two new node instances.

          • 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

          Activity

            People

              cnicolai@redhat.com Cristiano Nicolai
              jsoltes Juraj Soltes (Inactive)
              Jan Stastny Jan Stastny
              Jan Stastny Jan Stastny
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: