Title: Signal calls ~~~ /runtime/{deploymentId}/signal/{signalCode} ~~~ Its an invalid REST API, if we try with this it fails with 404 exception. Describe the issue: Suggestions for improvement: [POST] /runtime/{deploymentId}/signal This operation takes a signal and a event query parameter. - The signal parameter value is used as the name of the signal. This parameter is required. - The event parameter value is used as the value of the event. This value may use the number query parameter syntax described above. Example: ~~~~ /runtime/{deploymentId}/signal?signal={signalCode} ~~~~ Additional information:
Thanks Abhijit I have made the change and this can be verified here [1]. Moving to ON_QA. If you are happy with the change, I will push it live. [1] https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.0/html-single/Development_Guide/index.html#sect-Runtime_calls
Vikram, the changes are alright. Could you please also modify the following example where is the same problem? Example 13.10. REST request body with the Integer mySignal parameter /rest/runtime/business-central/process/org.jbpm.test/instance/2/signal?mySignal=1234i Since the signal type needs to be String, I would recommend to use a different example like starting a process with integer parameter: /rest/runtime/business-central/process/org.jbpm.test/start?map_var1=1234i
Sorry Ivo for the late reply. The example has been changed as suggested and can be verified here [1]. Moving back to ON_QA. [1] https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.0/html-single/Development_Guide/index.html#sect-Runtime_calls
Verified in BPMS 6.0 Development Guide and BPMS 6.1 Development Guide.