Current Limitations on Event Sub-process

[silvioneto]

Hi everybody,

From the Activiti User Guide v5.13 (about Event Sub-Process):

"Activiti only supports interrupting Event Sub-Processes.
Activiti only supports Event Sub-Process triggered using an Error Start Event or Message Start Event."

Is there any plans to
1) support non-interrupting Event Sub-Process?
2) trigger event sub-process using other start event types? I'm especially interested on Signal Start Event.

My use case is similar to the example on activiti user guide for signal event. There, when the policy conditions change the instance is signaled and it always go back to "calculate contract conditions". In my use case I'd like to evaluate the change on a business rule and, if the policy change affects that particular instance, than the instance must go back to a human task. Like this:

[img]http://www.icolabora.com.br/temp/signal1.png[/img]

I belive I can accomplish the same using embedded sub-process inside another embedded sub-process like above:

[img]http://www.icolabora.com.br/temp/signal2.png[/img]

But, this second options doesn't seem easy to a business user understand.

Thanks,

Silvio Neto

[frederikherema1]

Support for non-interupting event sub-processes is planned for the near future and supporting multiple event-types as start is also on the roadmap if I'm not mistaken.

[silvioneto]

Frederik, I found the [http://jira.codehaus.org/browse/ACT-1598] that maybe will aim signal event on embedded subprocess. I've voted for that.

But about non-interruping event subprocess, I found [http://jira.codehaus.org/browse/ACT-1478], where David Moser proposed an implementation that was closed by you on last January. Do you remember that? What can be done to revisit that issue?

[frederikherema1]

David was going to add the implementation as a pull-request on github. At least, that was my understanding. You can always reopen the issue and comment accordingly or check with David what his plan is…