Table of Contents
camunda BPM currently does not support the BPMN 2.0 AdHoc SubProcess.
But if you have requirements like
- Only 2 out of 4 tasks must be finished - then we can continue.
- The user can decide after what task the process should continue.
- Rules determine when open tasks are no longer necessary and the process should move on.
This could be hooked in with a workaround. This snippet shows an example where the process continues after task "A" and task "B" are finished (in this case either "C" weas already finished or it is skipped):
The implementation is straightforward and uses Task Listener which check at the completion of every task the rules if the other tasks should be cancelled. You could easily extend this check and for example check only tasks in the current sub process (to be pretty close to the AdHoc SubProcess).
See EnforceAdHocRukesTaskListener.
This approach has the drawback that all possible tasks are created when the subprocess is entered. That means they all end up in the tasklist - that might not match the user experience you expect with the Adhoc Subprocess (that you will get the notification to have the Adhoc Task and decide what tasks todo in this case).
An alternative might be to use a CMMN case definition instead of the Adhoc Subprocess, see CMMN Tutorial or the Underwriting Showcase.
- Tested on camunda BPM 7.0.0
- Tested only as JUnit test case
- Clone this repo and build the project using Maven
- Run the Unit Test
- Deploy the resulting WAR on the container (tested only with JBoss AS 7)
This is a pretty rough example hacked in a couple of minutes between two appointments. So it is neither a really sophisticed nor the best solution for this approach!
Feel free to discuss it in our forum: http://camunda.org/community/forum.html