I agree that could be useful. I'm thinking on workflow uses cases in which a graph is shown based on states rather than activities (i.e a document validation process in which the transitions between two document states is a waitstate: validate a document).
On the other side I don't see that as a priority right now but is good to keep that in mind.
i think we do need to work this out cause it can have big consequences in the engine. i've been reflecting a bit on this and there were a few implications.
mainly we need an interface (probably we can leverage the Condition interface, needed for guard conditions) that indicates wether the transition needs to continue automatically or wether it is a wait state that needs an external trigger.
i think it's best to work it out only on the pvm level with one or two test cases. then we can leave the rest of the bells and wistles for later.
it was ok. transitions as wait states are implemented