-
Bug
-
Resolution: Done
-
Critical
-
6.1.0
-
None
Description of problem:
A signal subprocess in a process is not invoked. Signals send to the process aimed to invoke the subprocess are ignored.
Version-Release number of selected component (if applicable):
Update 3
How reproducible:
Always.
Steps to Reproduce:
1. Create a process and add a signal subprocess to it;
2. Inside the subprocess, add the signal itself, a script task to print some message to indicate that the subprocess was invoked and then an end event;
3. Use a script task to signal the process in the main process flow;
Actual results:
The process is finished without entering the subprocess;
Expected results:
It should invoke th subprocess.
Additional info:
Between update 2 and 3, the engine was updated to invoke process using the signal name, instead the id. The editor still looks for a signal with a given ID instead looking for its name. Further local tests using the branch 6.2.x seems to have solved the issue.
Attached you can find a simple process that can be used to reproduce this issue and also the diff file of the changes I made locally.
- blocks
-
RHBPMS-1106 [GSS](6.1.z)Signal subprocess is never invoked
- Verified
- is duplicated by
-
RHBPMS-1106 [GSS](6.1.z)Signal subprocess is never invoked
- Verified