fix a signal creation bug

fix a bug where for the second process
you start, signal processing would happen differently
(e.g. scope would always be null)

Author: robert-gurol-ebcont

modules/flowable-engine/src/main/java/org/flowable/engine/impl/dynamic/AbstractDynamicStateManager.java

@@ -1549,9 +1549,6 @@ protected void processCreatedEventSubProcess(EventSubProcess eventSubProcess, Ex
                         SignalEventDefinition signalEventDefinition = (SignalEventDefinition) eventDefinition;
                         BpmnModel bpmnModel = ProcessDefinitionUtil.getBpmnModel(eventSubProcessExecution.getProcessDefinitionId());
                         Signal signal = bpmnModel.getSignal(signalEventDefinition.getSignalRef());
-                        if (signal != null) {
-                            signalEventDefinition.setSignalRef(signal.getName());
-                        }
 
                         ExecutionEntity signalExecution = processEngineConfiguration.getExecutionEntityManager().createChildExecution(eventSubProcessExecution.getParent());
                         signalExecution.setCurrentFlowElement(startEvent);

modules/flowable-engine/src/main/java/org/flowable/engine/impl/util/ProcessInstanceHelper.java

@@ -453,9 +453,6 @@ protected void handleSignalEventSubscription(EventDefinition eventDefinition, St
         SignalEventDefinition signalEventDefinition = (SignalEventDefinition) eventDefinition;
         BpmnModel bpmnModel = ProcessDefinitionUtil.getBpmnModel(parentExecution.getProcessDefinitionId());
         Signal signal = bpmnModel.getSignal(signalEventDefinition.getSignalRef());
-        if (signal != null) {
-            signalEventDefinition.setSignalRef(signal.getName());
-        }
 
         ExecutionEntity signalExecution = processEngineConfiguration.getExecutionEntityManager().createChildExecution(parentExecution);
         signalExecution.setCurrentFlowElement(startEvent);