add a decision node after the process-state and use a process variable to transfer the result
As this answer is coming from you, I guess there really is no other solution for this.
Is this something we can expect to find in jbpm's roadmap ? I've used a number of commercial products before and they allow it; in order to have a clean fit of a sub process into a super process.
Thanks for answering that fast !
i didn't mean to say that your request doesn't make sense.
we are thinking of enabling conditions on all transitions (not only the ones of a decision). then, you could combine the decision behaviour in each node implementation, also in the process-state
but i want to group the jpdl xml changes as much as possible. more nodes are due on an update.
While we are on the topic, is there a way to attach attributes to
a transistion, so that similar transistions can be grouped together by
their attributes ?
I have an use case in which I need to extract a list of possible transactions
which e.g. are marked as 'manual triggerable' (in contrast to timer triggered
transactions) to present them in some UI.
Or is there another way to achieve this behaviour ?