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.
Bug
Major