topic Re: Unable to signal the process in Alfresco Archive

Unable to signal the process

rajivmoghe — Wed, 13 Apr 2016 13:08:14 GMT

Hi, This has probably been asked many times before, but I am stuck and cannot figure out what the problem is.I'm using the spring boot activiti starter project (activiti v 5.17.1-SANPSHOT, and boot v 1.2.2.RELEASE) for this.I have a process as below:For the 'My Service Task' task, I have extended th

Re: Unable to signal the process

jbarrez — Wed, 20 Apr 2016 13:21:58 GMT

You are mixing the BPMN 'signal' concept with the 'signal' in the core engine.
It has nothing to do with each other. The latter is also renamed to 'trigger' in version 6.
So to continue your custom task, you simply need to call the runtimeService.signal (NOT signalEventReceived) method to continue the process (exactly the same as when using a receive task).

Re: Unable to signal the process

rajivmoghe — Wed, 20 Apr 2016 14:28:24 GMT

Hi Joram,

Thanks for this. I tried this out by using

{
  "action":"signal",
  "signalName":"Some Signal"
}

.

In the MyServiceTask.java I also have the signal method as follows:


  public void signal(ActivityExecution execution, String signalName, Object signalData) throws Exception {
   System.out.println("SignalName "+ signalName +"\n"+ "Signal Data  "+ signalData);
    leave(execution);
  }

On debug, I traced the ReST call to this routes this call to RuntimeService's signal(String execId, Map procVars) method, that creates a SignalCmd with the signalName and signalData as nulls. Which means that in my service task, I do not have access to the signal name (Or is that the triggerName in 6.0 onwards?).

Q: Is there any way I can have that, short of rewriting my own wrapper on the RuntimeService and a new ReST endpoint for this?

Re: Unable to signal the process

jbarrez — Tue, 26 Apr 2016 10:53:46 GMT

"Which means that in my service task, I do not have access to the signal name (Or is that the triggerName in 6.0 onwards?)."

Yes, signal in v5 = trigger in v6. A 'signal' in v5 speak in this context is effectively a 'go ahead' at a wait state.

"Is there any way I can have that, short of rewriting my own wrapper on the RuntimeService and a new ReST endpoint for this? "

Maybe there is a way to use process variables for this purpose? Although it doesn't match perfectly.

Re: Unable to signal the process

rajivmoghe — Wed, 27 Apr 2016 01:41:41 GMT

So I really cannot have the following ? As in here

public void signal(ActivityExecution execution, String signalName, Object signalData){
     if(signalName.equals("serviceCompletedSignal")){
      add signalData to procVars;
      leave();
     }
     else{// signalName.equals("allData is available")
      add allData to procVars;
      execute();
     }

since this signal (v6 trigger) is merely an unconditional 'continue forward' to the instance?
And also the 'signal' of the method name and 'signalName' in the paramlist refer to two different concepts?

Re: Unable to signal the process

jbarrez — Tue, 03 May 2016 11:41:51 GMT

" is merely an unconditional 'continue forward' to the instance"

Yes.

"And also the 'signal' of the method name and 'signalName' in the paramlist refer to two different concepts?"

In the default implementations shipped with the engine, yes. But you can use it for whatever purpose in your custom code of course.