Sunday, June 25, 2006
the basics
It gives us automation, tracking, control, reporting and insight. This insight comes through the graphical nature of the process (self) documentation and from the tracking, monitoring, reporting and the possible mining of the data associated with these collected over a period of time.
Other key aspect here is integration. Typically we automate a manual process. The pre-requisite for automation is the thing exist in a manual form :) and this process be it human based or not, spans more than one business domain. hence the integration across those business domains is required and typically an assumed feature. Hence the tools that provide the workflow capability has some out-of-the-box support for integration.
Integration is also required for storage, security and reporting components.
windows workflow
But, this would mean that the workflow improvements may have to wait for the the framework releases. It will be much slower. given the importance of this technology tying it to the framework means that one day we could even see language constructs to help workflow style processing. although I like the xaml approach it would be cool to have a WF# offering as well :)
anway, looking at the Office 2007 beta, we can see WF manifesting itself through sharepoint and the standard applications like word and excel. It is already there in the Team Edition of VS.NET 2005.
I dont know whether Vista will have some OS level tools built on WF. May be as a showcase. Reading through the 5 or so articles on the Microsoft Architecture Journal edition 7 themed "Generation Workflow" it is clear that MS has looked at many applications for the WF. Not just the Human workflow.
I am still waiting to see Biztalk's tac on WF. Should be interesting.


