-
Bug
-
Resolution: Done
-
Major
-
7.13.3.GA
-
The following rest api is supposed to signal multiple process instances with a specified signal name.
POST
{containerId}
/server/containers//processes/instances/signal/
{signalName}However, it doesn't work with a dynamical boundary signal specified by a process variable.
It only works for a signal with constant value.It works only if a list of process instance ids is provided.
This issue is not addressed by https://issues.redhat.com/browse/BAPL-1801
I've also back ported pr-1909 [1] for jbpm-9691 [2] to rhpam 7.9.1 but the issue remains.
I'm attaching a bpmn file that could reproduce the issue.
[1] https://github.com/kiegroup/jbpm/pull/1909/commits/89bae53c13a95741f9cdcc0937eab795de54140d
The following rest api is supposed to signal multiple process instances with a specified signal name. POST /server/containers/ {containerId} /processes/instances/signal/ {signalName} However, it doesn't work with a dynamical boundary signal specified by a process variable. It only works for a signal with constant value. It works only if a list of process instance ids is provided. This issue is not addressed by https://issues.redhat.com/browse/BAPL-1801 I've also back ported pr-1909 [1] for jbpm-9691 [2] to rhpam 7.9.1 but the issue remains. I'm attaching a bpmn file that could reproduce the issue. [1] https://github.com/kiegroup/jbpm/pull/1909/commits/89bae53c13a95741f9cdcc0937eab795de54140d [2] https://issues.redhat.com/browse/JBPM-9691
-
False
-
False
-
-
-
-
-
-
CR1
-
+
-
Undefined
-
-
2021 Week 16-18 (from Apr 19), 2021 Week 19-21 (from May 10), 2021 Week 22-24 (from May 31)
- clones
-
RHPAM-3603 dynamical boundary signal won't be triggered without providing process instance id
- Closed
- is cloned by
-
JBPM-10188 RHPAM-3603 has come back to 7.13.x. dynamical boundary signal won't be triggered without providing process instance id
- Resolved
- relates to
-
RHPAM-4498 Boundary signal not triggered without providing process instance id
- Closed