Alternatives to fork process without leaving current task
From a UserTask with more than one outgoing transition, I want to be able to tell the workflow engine to execute or follow one of those transitions without abandoning/completing the current UserTask. Later, I would join the flows using an InclusiveGateway.
The way I could get this to work was introducing signal boundary events to my process model. Therefore, using @cancelActivity, I was able to tell the process whether leaving the current UserTask or not.
I am not sure if the use of signals is the right approach for what I needed, and/or if there could be other alternatives for it.
Re: Alternatives to fork process without leaving current task
My current process model is similar to "MyProcess1.bpmn". With this process model I am able to execute "servicetask1" as many times as needed without abandoning "usertask1" (due to the boundary event with @cancelActivity="false").
According to your previous comment, I guess you may be suggesting something like "MyProcess2.bpmn", where a decision is made in "exclusivegateway1" based on the variable "taskOutput". If so, I would rather stick with "MyProcess1.bpmn", as it does not force the workflow to abandon "usertask1" in order to execute "servicetask1".
Is there an alternative to "MyProcess1.bpmn" where users can execute "servicetask1" (from "usertask1") without using signals and without abandoning/re-entering to "usertask1"?