Loading...

XML

Word

Printable

Fix Build:
CR1
Git Pull Request:
https://github.com/kiegroup/jbpm/pull/987
Steps to Reproduce:
Hide

Create a process with
start->script->signal->end

with one process variable "signalName" String.

script content:
kcontext.setVariable("signalName',"mySignal");

signalRef attribute will have this value # {signalName}
*deploy this process onto kie-server
*run it
* call GET /kie-server/services/rest/server/containers/{containerId}/processes/instances/{pInstanceId}/signals
* it will return #{signalName}

expected behavior is that it will return 'mySignal'
Show
Create a process with start->script->signal->end with one process variable "signalName" String. script content: kcontext.setVariable("signalName',"mySignal"); signalRef attribute will have this value # {signalName} *deploy this process onto kie-server *run it * call GET /kie-server/services/rest/server/containers/{containerId}/processes/instances/{pInstanceId}/signals * it will return #{signalName} expected behavior is that it will return 'mySignal'

Following API

/kie-server/services/rest/server/containers/

{containerId}

/processes/instances/

{pInstanceId}

/signals

returns list of active signals. If signal name is #{expression], then this expression is not resolved in the response - i.e. literally '#

{expression}

' is returned, instead of real runtime value.

clones

RHPAM-121 Kie Server rest Signals API does not resolve mvel expressions