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

dynamical boundary signal won't be triggered without providing process instance id

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.11.1.GA
    • None
    • jBPM Core
    • None
    • False
    • False
    • CR1
    • +
    • Undefined
    • Hide

      To test the dynamical signal:

      1. build a kjar for the attached bpmn.
      2. create a kie container for this kjar.
      3. start a new process instance, for example:

      curl -X POST "http://localhost:8080/kie-server/services/rest/server/containers/test02778225/processes/boundary-signal-test/instances" -H "accept: application/json" -H "content-type: application/json" -d "

      { \"signalName\": \"mySignal\"}

      "

      4. send a signal, for example:

      curl -X POST "http://localhost:8080/kie-server/services/rest/server/containers/test02778225/processes/instances/signal/mySignal" -H "accept: application/json" -H "content-type: application/json" -d "

      { \"signalName\": \"mySignal\"}

      "

      expected behavior:
      The kie-server console doesn't show any printout from the script task in the process.
      The process stays in task A.

      To test the constant signal:
      1. build a kjar for the attached bpmn.
      2. create a kie container for this kjar.
      3. start a new process instance, for example:

      curl -X POST "http://localhost:8080/kie-server/services/rest/server/containers/test02778225/processes/boundary-signal-test/instances" -H "accept: application/json" -H "content-type: application/json" -d "

      { \"signalName\": \"mySignal\"}

      "
      4. complete the task A. The process should move to task B.
      5. send a signal, for example:

      curl -X POST "http://localhost:8080/kie-server/services/rest/server/containers/test02778225/processes/instances/signal/constant" -H "accept: application/json" -H "content-type: application/json" -d "{ }"

      expected behavior:
      The kie-server console shows printout "Boundary signal Triggered"
      The process is completed.

      Show
      To test the dynamical signal: 1. build a kjar for the attached bpmn. 2. create a kie container for this kjar. 3. start a new process instance, for example: curl -X POST "http://localhost:8080/kie-server/services/rest/server/containers/test02778225/processes/boundary-signal-test/instances" -H "accept: application/json" -H "content-type: application/json" -d " { \"signalName\": \"mySignal\"} " 4. send a signal, for example: curl -X POST "http://localhost:8080/kie-server/services/rest/server/containers/test02778225/processes/instances/signal/mySignal" -H "accept: application/json" -H "content-type: application/json" -d " { \"signalName\": \"mySignal\"} " expected behavior: The kie-server console doesn't show any printout from the script task in the process. The process stays in task A. To test the constant signal: 1. build a kjar for the attached bpmn. 2. create a kie container for this kjar. 3. start a new process instance, for example: curl -X POST "http://localhost:8080/kie-server/services/rest/server/containers/test02778225/processes/boundary-signal-test/instances" -H "accept: application/json" -H "content-type: application/json" -d " { \"signalName\": \"mySignal\"} " 4. complete the task A. The process should move to task B. 5. send a signal, for example: curl -X POST "http://localhost:8080/kie-server/services/rest/server/containers/test02778225/processes/instances/signal/constant" -H "accept: application/json" -H "content-type: application/json" -d "{ }" expected behavior: The kie-server console shows printout "Boundary signal Triggered" The process is completed.
    • 2021 Week 16-18 (from Apr 19), 2021 Week 19-21 (from May 10), 2021 Week 22-24 (from May 31)

      1. boundary-signal-test.bpmn
        25 kB

            ftirados Francisco Javier Tirado Sarti
            rhn-support-ghu Gary Hu
            Antonio Fernandez Alhambra Antonio Fernandez Alhambra (Inactive)
            Antonio Fernandez Alhambra Antonio Fernandez Alhambra (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: