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

Not able to signal SignalBopundaryEvent of HumanTask which is in MultiInstance subprocess

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • 7.12.0.GA
    • 7.11.1.GA
    • jBPM Core
    • False
    • None
    • False
    • Hide
      • Build and deploy attached project.
      • Start process instance using below REST API
      /kie-server/services/rest/server/containers/ContainerID/processes/SignalIssueProject.testProcess/instances
      • Wait for IntermedidateTimer to complete(delay 30 secs)
      • After timer node execution ThrowingSignalEvent will be executed, its expected that it will signal the SignalBoundaryEvent of HumanTask but we can see humanTask is active.
      • Try to signal process using REST API but still we can see HT is active.
      http://localhost:8080/kie-server/services/rest/server/containers/ContainerID/processes/instances/$pid/signal/signalName 

       

      Actual behaviour:

      Not able to signal SignalBoundaryEvent from MI subprocess through throwing signalEvent or through REST API.

       

      Expected behaviour:

      User should be able to signal SignalBoundaryEvent from MI subprocess through throwing signalEvent or through REST API.

      Show
      Build and deploy attached project. Start process instance using below REST API /kie-server/services/ rest /server/containers/ContainerID/processes/SignalIssueProject.testProcess/instances Wait for IntermedidateTimer to complete(delay 30 secs) After timer node execution ThrowingSignalEvent will be executed, its expected that it will signal the SignalBoundaryEvent of HumanTask but we can see humanTask is active. Try to signal process using REST API but still we can see HT is active. http: //localhost:8080/kie-server/services/ rest /server/containers/ContainerID/processes/instances/$pid/signal/signalName   Actual behaviour: Not able to signal SignalBoundaryEvent from MI subprocess through throwing signalEvent or through REST API.   Expected behaviour: User should be able to signal SignalBoundaryEvent from MI subprocess through throwing signalEvent or through REST API.
    • ---
    • ---

      Not able to signal SignalBopundaryEvent of HumanTask which is in MultiInstance subprocess through another throwing signal event or through REST API

      /kie-server/services/rest/server/containers/DeploymentId/processes/instances/signal/signalName

        1. MISubSignalTest.bpmn
          21 kB
        2. MISubSignalTest-Project.zip
          193 kB
        3. SignalIssueProject_fixed.zip
          96 kB
        4. SignalIssueProject.zip
          92 kB

              mputz_jira Martin Weiler (Inactive)
              rhn-support-abhumbe Abhijit Humbe
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: