Thanks both for your replies. I got a bit further today and have uploaded a very basic working example to github here: https://github.com/jugglingcats/tjbpm.
https://raw.github.com/jugglingcats/tjbpm/master/diagram.png
This works fine, but it's a really simple workflow and already quite cumbersome. Applying unit tests isn't really an option, because projects can configure workflows on the fly.
Ashish, is there documentation anywhere on programatically creating tasks, etc? Maybe this is ultimately the way to go, but it seems to me that a lot of work has gone into the SemanticModule implementations such as ProcessSemanticModule and BPMNSemanticModule and that these are (or should be) extensible with higher level semantics - but there is a fair amount of complexity in these implementations so hard to see where to start. What I'm after is a way to roll together the saved and saveTransitions (and outgoing sequence flow constraints) into a single construct, eg:
<myns:state id="x" name="saved">
<myns:transition name="reject" to="review"/>
<myns:transition name="approve" to="published"/>
</myns:state>
The idea of using (or even extending) existing visual editors with this type of extension is probably unrealistic...
Am suffering from wanting to make common scenarios in our environment really simple but still allow the power of BPMN when needed.
Regards, Alfie.
