Yeah i have been looking and reading about it - seems like a lot of overhead for something that should be choice/descision and role/user driven

seems a class that could have instructions for where to direct info after a descision would be the easiest - or am i missing something ? - workflows usually only go forward with the rejection of something forcing the item to a loop back to person

I think i am oversimplifying it but thats a lot of what i get out of what MS has published on WF

Well really you could make it very robust - basically you could make an interface like iactionable - admitedly this goes in the core or adds to it

then you could have it call assemblies as part of the inteface and those could be defined and each one would have something like a  dowork function that would interact with the database and stored procs - basically any workflow is going to be when this module does this do these actions behind the scenes - so almost an on event type of functionality

okay not enough sleep today to think to hard of this