Windows Workflow Foundation

I recently went to go and see a presentation on Microsoft Workflow Foundation.  They are coming out with a workflow engine at some point and I was going along to see if they had any good ideas for Kontinuum.
As Workflow Foundation is just a set of DLLs and programming interfaces i.e. it is just an engine I did not feel that it would compete in the same space as Kontinuum. 

The guy presenting Workflow Foundation was about 5 minutes into his presentation (btw he couldn’t actually demo the beta do to some sort of error) but he told us that Workflow Foundation can only handle two types of workflow sequential and non-sequential.  This means it can only do A->B->C or you can do A, B or C at any time.  In all the workflow systems I have been involved with maybe only 20% fit into these two categories.  The vast majority have other things happen in them that control behaviour. 

1) Most have decisions i.e. if A is done due B or C depending on some result from A.
2) Most have some points that are combinations of sequential and non-sequential i.e. once A is done you can do B or C, but you can not do D until both b and c have been completed.
3) Some have loop back mechanisms i.e. continue to do instances of B until some condition is met
4) Some spawn 1 or more sub workflows

and those are just the bare bones basics….

 Editors Note:  Apparrently the above paragraph is not correct however I am leaving it in here as some of the comments that follow refer to this paragraph

I am not sure where Microsoft is going with workflow foundation.  I suppose it is just meant for extremely simple single user workflows that are designed by people just getting comfortable with web browsers, but if that is the case then why is there only a programming interface.  My main gripe however is the acronym WWF.  Which in my mind is either the World Wrestling Federation or the World Wildlife Fund.  The WWF acronym is overcrowded already.

Editors Note: It appears that since I posted this article Windows Workflow Foundation is now being abbreviated as just WF.  Although if you query google on “Windows Workflow Foundation” or “Workflow Foundation” you get pretty much the same number of hits.


3 thoughts on “Windows Workflow Foundation

  1. Just reading through this post, I must say you have completely misunderstood what WF can and cannot do…infact all the 4 points you mention are “very easily” doable – in fact very essential for the workflows we envision to enable. Have you had a chance to look at the framework yourself before this blog entry?

  2. To Comment 1
    I was told during the presentation it was Windows Workflow Foundation. If it is now called WF I will start to refer to it as such.

    For Comment 2
    I was just retelling what I was told at the presentation. To be honest I have not had a chance to adequetly check out the product for more then a couple of hours and as I said the presenter of the software was unable to get his example working during his demo. But again I was simply re-iterating what I was told during a presentation. If I have caused any confusion I apologize but I am not sorry for only repeating what I have been told.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s