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

A process instance after being aborted the current node (async) remains in RED

XMLWordPrintable

    • False
    • None
    • False
    • Hide
      1. Build and deploy the kjar using the attached project.
        • Note: The process contains only a human task node. 
      2. Start it through
          POST/server/containers/{containerId}/processes/{processId}/instances
      3. Abort it through 
           DELETE/server/containers/{containerId}/processes/instances/{processInstanceId}
      4. Open the diagram from business-central.

      Actual result

      You would see the human task node is still marked as RED.

      Expected result

      Human task node is highlighted as a current node - BLUE.

      Show
      Build and deploy the kjar using the attached project. Note: The process contains only a human task node.  Start it through   POST /server/containers/{containerId}/processes/{processId}/instances Abort it through     DELETE /server/containers/{containerId}/processes/instances/{processInstanceId} Open the diagram from business-central. Actual result You would see the human task node is still marked as RED. Expected result Human task node is highlighted as a current node - BLUE.
    • ---
    • ---

      A customer created a process instance and then they aborted it using the Rest API:
      /server/containers/{containerId}/processes/instances/{processInstanceId}
       
      They found that for the same application, one bpmn flow is working as expected (current node ) and the other bpmn flow is displayed as a stuck node with RED color and the process instance with an "aborted" stage. They're suspecting that the issue is reproducible on the flows which have an async event node.

            nmirasch@redhat.com Neus Miras Chueca
            rhn-support-luzrodri Luz Rodriguez
            Dominik Hanak Dominik Hanak
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: