Workflow is usually so much more than an object state. You might have required documents or a proof of work that go in attach to the state change, some state ch

Workflow is usually so much more than an object state. You might have required documents or a proof of work that go in attach to the state change, some state change roles might be asymmetrical (i.e. only this role can roll back a state transfer) so permission need to be dynamic depending on object states, and then you have good ole transformative batches on top which are squisitely custom. I mean, I know the problem quite a lot, sice one of my many backburner ideas is a workflow centric self service crud builder :D