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

REST endpoint containers/{containerId}/processes/instances/{instanceId}/signals doesn't list boundary signals

XMLWordPrintable

    • DR4
    • Hide

      create a process:
      start->human task(with boundary signal) -> end

      start this process and execute:

      GET HOST:PORT/kie-server/services/rest/server/containers/CONTAINER_ID/processes/instances/PID/signals

      ACTUAL: BEHAVIOR:
      signal is not listed in the response
      EXPECTED BEHAVIOR:
      signal is listed in the response

      Show
      create a process: start->human task(with boundary signal) -> end start this process and execute: GET HOST:PORT/kie-server/services/ rest /server/containers/CONTAINER_ID/processes/instances/PID/signals ACTUAL: BEHAVIOR: signal is not listed in the response EXPECTED BEHAVIOR: signal is listed in the response
    • 2018 Week 07-08

      We have a BPMN2 process deployed to a kie-server (on OpenShift), with a boundary interrupting signal on a User Task. When we list active signals using the REST API, this signal is not returned. It would seem that only standalone signal nodes are listed.

      Workaround is to create kie-server extension, which is not acceptable in customer's view:

      My expectation is very clear: Bugs should be fixed. I don't think having to deploy extensions is a reasonable way to move past this bug. This adds heavily to our maintenance burden.

        1. org.jbpm.SignalReproducer.v1.0.bpmn2
          26 kB

              rhn-support-tsurdilo Tihomir Surdilovic (Inactive)
              rhn-support-agiertli Anton Giertli
              Lubomir Terifaj Lubomir Terifaj
              Lubomir Terifaj Lubomir Terifaj
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: