-
Bug
-
Resolution: Done
-
Major
-
7.8.1.GA
-
False
-
False
-
Release Notes
-
-
-
-
-
-
CR1
-
+
-
Undefined
-
---
-
---
-
-
2021 Week 07-09 (from Feb 15), 2021 Week 10-12 (from Mar 8)
An signal sent by a subprocess is not captured correctly in an intermediate capture event.
To detect, you can set the scope to project instead of per process and previous instances of the project will capture the signal (as at that time they have the listener waiting for the signal)
Attached a project with signal scope "Project" and output showing that the previous instance listen to this signals
solution
To avoid problems with the action nodes (intermediate throw) I added a new metadata for the node
"executeActionAfterComplete" when is set to true the signal is process after finishing processing the current flow.(like a passthrough)
- is cloned by
-
JBPM-9632 Intermediate Throw event signal stops processing workflow before signal is processed.
- Resolved