Monday, July 24, 2006
more basics
So, for the masses to leverage this toolkit, we need tools like visio, word, excel and the browser itself to be able to support workflow creation, deployment, management, initiation, participation and reporting.
Sharepoint is doing a good job by providing the widely used workflow processes out-of-the-box. then we have sharepoint designer to help implementing higher level of functionality than these workflows. After that we have to resort to VS.NET or notepad using WF.
I guess there is a lot of room for ISVs and SIs to play here. Nintex has a sharepoint only toolkit for workflows. I have worked with Sharepoint integration components from vendors like K2, and Captaris. These vendors will upgrade and expand their offerings in this space - no doubt about that.
I also think there is a lot of room for small players to come up with solutions in this space. now that barrier to entry has been lowered by this unfied API. SaaS is the other are where Workflow can work for the small players in a big way.
Friday, July 21, 2006
the workflow wave
Whether BAM will also evolve to support WF as a suite of product is unknown. MS does have most of the components of a Workflow platform in place. So, whether they combine and make it a platform offering or not is an interesting question. This will change the landscape for ISVs who currently bridge the gap in the workflow / BPM area.
Microsoft's scorecards and Performance point also has a part to play in the Business Process Management arena. Imagine one day all WF processes could be managed from a central place and integrated in to corporate reporting would be a great capability. This won't be for free and MS will need many years to deliver this.


