nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Start SubProcess using a Signal?

dognose

Hello,

my Process should contain some subprocesses that can be started at any time under given conditions.
The Task that is "triggering" the Sub-Process needs to remain active. (Therefore i can not use a normal flow to the
subprocess, because this flow is only executed if the task is completed)

So i tried to achieve this, using signals, where I send a signal like this:

runtimeService.signalEventReceived("invokeSubProcessC");
‍‍‍

I defined ImmediateSignalCatchingEvents for the Subprocesses like this:

CatchEvent -> [ Subtask ]

<intermediateCatchEvent id="catch_invokeSubProcessC" name="SignalCatchEvent">
  <signalEventDefinition signalRef="invokeSubProcessC"></signalEventDefinition>
</intermediateCatchEvent>
…
<sequenceFlow id="flow9" name="" sourceRef="catch_invokeSubProcessC" targetRef="subProcessC"></sequenceFlow>
…
<subProcess id="subProcessC" name="Sub Process">

</subProcess>
‍‍‍‍‍‍‍‍‍‍‍

However, the subprocess is not created, i.e. no instance for the task following the subprocess' start event is created.

What am I doing wrong?

—-

The Activiti Eclipse Designer lacks of "Message" Objects - are they supported by activiti?
(I assume using messages instead of signals would be what i'm looking for)

Currently i'm using a workaround and "forking" the outflow of taskA, so that the subprocess is started and a "new" taskA is created.
However he changes his ID and therefore may not work as expected in a multi-user environment.

Got it:
Signal needs an incoming flow to entering the "waiting" State (so i added a Gateway right afer the Main-Process-Start-Event to send all Subprocesses in the "Waiting-for-signal"-State.

Find more posts tagged with

Comments

frederikherema1

Can't you add a non-interupting signal-boundary event on your task, and have this flow to a call-activity or subprocess? because of the "cancelActivity" being true, the task WILL NOT end…

<br><boundaryEvent id="boundary" attachedToRef="task" cancelActivity="false">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <signalEventDefinition signalRef="invokeSubProcessC"/><br></boundaryEvent><br>

dognose

Maybe i'm a bit confused about the BoundarySignalEvents.

I Always thought the "Other Way round" and assumed, that a SignalBoundaryEvent is NOT The trigger, but the handler,
so you can "stop" (or update) a task, if conditions change. So a signal is triggered somewhere in the process and the BoundaryEvent
will catch that Signal even when the associated Task is already running.

(Because it also has the same look like a ImmediateSignalCatching event and looks different than a Throwing Event.)

To go with a Example from the Docu:

[img]http://www.activiti.org/userguide/images/bpmn.boundary.signal.event.png[/img]

Here i Assume that the task will be active until the "Alert" Signal is triggered from Somewhere else - right?

And thats basically …

I start to understand: You mean i should simple throw the signal "Alert" inside the "do Something" task in Order to proceed with the flow "on Alert".

Well, i dunno if theres a difference to my current solution, which looks (simplified) like this:

[img]http://www.abload.de/img/capturemrsil.png[/img]

Both cases require the "signal" to be thrown programmatically I assume?

Ofc, even if those mehtods are funcitonaly equal, yours is clearer to understand, because you can see, where the signal's coming from.
(if you dont throw the same signal at other tasks)

jbarrez

Yes, as far as I understand you reasoning it is correct. The task will remain active until the signal is thrown.

frederikherema1

But if you use the "cancelActivity=false" on the boundary-event, the task WILL NOT be cancelled once the signal is thrown.

Example in our test cases. Consider this process, a task with a signal boundary-event on it:

<br><?xml version="1.0" encoding="UTF-8"?><br><definitions id="definitions" xmlns="<a href="http://www.omg.org/spec/BPMN/20100524/MODEL" rel="nofollow noopener noreferrer">http://www.omg.org/spec/BPMN/20100524/MODEL</a>"<br>&nbsp; xmlns:activiti="<a href="http://activiti.org/bpmn" rel="nofollow noopener noreferrer">http://activiti.org/bpmn</a>" targetNamespace="Examples"><br><br>&nbsp; <signal id="alertSignal" name="alert" /><br><br>&nbsp; <process id="nonInterruptingSignalEvent"><br><br>&nbsp;&nbsp;&nbsp; <startEvent id="theStart" /><br><br>&nbsp;&nbsp;&nbsp; <sequenceFlow id="flow1" sourceRef="theStart" targetRef="theUserTask" /><br><br>&nbsp;&nbsp;&nbsp; <userTask id="theUserTask" name="My User Task" /><br><br>&nbsp;&nbsp;&nbsp; <boundaryEvent id="signal" attachedToRef="theUserTask" cancelActivity="false"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <signalEventDefinition signalRef="alertSignal" /><br>&nbsp;&nbsp;&nbsp; </boundaryEvent><br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; <sequenceFlow id="flow2" sourceRef="theUserTask" targetRef="theEnd" /><br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; <endEvent id="theEnd" /><br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; <sequenceFlow id="flow3" sourceRef="signal" targetRef="theUserTask2" /><br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; <userTask id="theUserTask2" name="My Second User Task" /><br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; <sequenceFlow id="flow4" sourceRef="theUserTask2" targetRef="theEnd2" /><br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; <endEvent id="theEnd2" /><br>&nbsp; </process><br><br></definitions><br>

And, after signaling the process, the task is still present and signal flow is taken as well:

<br>@Deployment<br>&nbsp; public void testNonInterruptingSignal() {<br>&nbsp;&nbsp;&nbsp; ProcessInstance pi = runtimeService.startProcessInstanceByKey("nonInterruptingSignalEvent");<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; List<Task> tasks = taskService.createTaskQuery().processInstanceId(pi.getProcessInstanceId()).list();<br>&nbsp;&nbsp;&nbsp; assertEquals(1,&nbsp; tasks.size());<br>&nbsp;&nbsp;&nbsp; Task currentTask = tasks.get(0);<br>&nbsp;&nbsp;&nbsp; assertEquals("My User Task", currentTask.getName());<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; runtimeService.signalEventReceived("alert");<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; tasks = taskService.createTaskQuery().processInstanceId(pi.getProcessInstanceId()).list();<br>&nbsp;&nbsp;&nbsp; assertEquals(2,&nbsp; tasks.size());<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; for (Task task : tasks) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (!task.getName().equals("My User Task") && !task.getName().equals("My Second User Task")) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fail("Expected: <My User Task> or <My Second User Task> but was <" + task.getName() + ">.");<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>&nbsp;&nbsp;&nbsp; }<br><br>&hellip;<br>

Source: org.activiti.engine.test.bpmn.event.signal.SignalEventTest

dognose

helpfull post

basically that was the Function i assumed. However this way, it won't work.

I get the exception:

<br>[org.activiti.engine.impl.interceptor.CommandContext] (http-localhost-127.0.0.1-8090-11) Error while closing command context: org.activiti.engine.ActivitiException: Execution '1008' has not subscribed to a signal event with name 'startSubProcessAfromX'.<br> at org.activiti.engine.impl.cmd.SignalEventReceivedCmd.execute(SignalEventReceivedCmd.java:52) [activiti-engine-5.10.jar:5.10]<br> at org.activiti.engine.impl.cmd.SignalEventReceivedCmd.execute(SignalEventReceivedCmd.java:29) [activiti-engine-5.10.jar:5.10]<br>&hellip;<br>

currently i designed it like this:

[img]http://download.dog-net.org/easyshare/pictures/20121024110950.jpg[/img]

using 2 Signals startSubProcessAfromY and startSubProcessAfromX

XML:

<br><definitions &hellip;><br>&nbsp; <signal id="startSubProcessAfromX" name="startSubProcessAfromX"></signal><br>&nbsp; <signal id="startSubProcessAfromY" name="startSubProcessAfromY"></signal><br>&nbsp; &hellip;<br>&nbsp; <process id="processP" name="processP"><br>&nbsp;&nbsp;&nbsp; &hellip;<br>&nbsp;&nbsp;&nbsp; <userTask id="TaskX" &hellip;></userTask><br>&nbsp;&nbsp;&nbsp; <boundaryEvent id="boundarysignal1" cancelActivity="false" attachedToRef="TaskX"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <signalEventDefinition signalRef="startSubProcessAfromX"></signalEventDefinition><br>&nbsp;&nbsp;&nbsp; </boundaryEvent><br>&nbsp;&nbsp;&nbsp; <userTask id="TaskY" &hellip;></userTask><br>&nbsp;&nbsp;&nbsp; <boundaryEvent id="boundarysignal2" cancelActivity="false" attachedToRef="TaskY"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <signalEventDefinition signalRef="startSubProcessAfromY"></signalEventDefinition><br>&nbsp;&nbsp;&nbsp; </boundaryEvent><br>&nbsp;&nbsp;&nbsp; &hellip;<br>&nbsp;&nbsp;&nbsp; <sequenceFlow id="flow34" name="" sourceRef="boundarysignal1" targetRef="exclusivegateway1"></sequenceFlow><br>&nbsp;&nbsp;&nbsp; <sequenceFlow id="flow35" name="" sourceRef="boundarysignal2" targetRef="exclusivegateway1"></sequenceFlow><br>&nbsp;&nbsp;&nbsp; &hellip;<br>

The Task themselves are made of a form, where a button "triggers" the signal:

<br>public void triggerSubProcessAButtonClicked(BusinessProcess businessProcess){<br>&nbsp; &hellip;<br>&nbsp; runtimeService.signalEventReceived("startSubProcessAfromX", businessProcess.getProcessInstanceId());<br>&nbsp; &hellip;&nbsp; <br>}<br>

And exactly at this line, the exception is thrown. (And yes, i'm definitly triggering The Signal "…fromX" inside Task X)

Only difference is that i just send the signal to the current instance, not to all instances.

ps.: If the above code contains typos and/or case-issues - they are not there i just replaced the names for better understanding 🙂

frederikherema1

Try signaling the exact execution instead of the process-instance… Try querying the task and use the executionId you get from there.

dognose

Try signaling the exact execution instead of the process-instance… Try querying the task and use the executionId you get from there.

ops: Should have tried that – works.

<br>//send signal to current task only.<br>String taskId = Helper.getContextHelper().getParameter(RequestConstants.TASK_ID_PARAMETER_NAME);<br>runtimeService.signalEventReceived(TaskConstants.TRIGGER_SUBPROCESS_SIGNAL_NAME, taskId);<br>

Sir ThxAlot checked in at forums.activiti.org :ugeek: