Workflow in the 2007 Microsoft Office System

I wish all authors (programming) could write as clearly and as understandable as this author; no hidden stuff or tricks, just straight to guts. If you are new to workflow and want to get going fast enough, get this book. I put this author in the category of authors like Stanley B. Lippman, Dr. Grimmes, Dr. Major, Dino Esposito, Ted Pattison, and John Papa.

I bought this book as a reference book, but found myself actually reading through it instead! It is very well-written and easy to understand for a non-programmer like me. It covers very simple workflow and also gets into the more complex things you can do to solve very specific business problems when you add Sharepoint Designer. Excellent coverage of workflow from beginning to end.

I agree with many of the reviews already written. This is a well organized and to the point tutorial on workflows with the Office system. I skimmed through once to get the high level overview, and dove into chapter 6 to get into designing workflows in visual studio very quickly. As was pointed out in another review, the author is 'conversational' but I didn't feel like it hurt the book at all. I guess that is a matter of personal preference. Overall, this book was very helpful and I would highly recommend it.

Having used MOSS 2007 and WF since their beta timescales I've always struggled to find a source of useful information on this topic . . . enter "Workflow in the 2007 Microsoft Office System". The book starts off basic, covering the concepts behind WF and workflows using SharePoint Designer. Then it gets down and dirty into the essentials like activity development, sequential workflows, state machine workflows, workflow forms and lots of other good stuff that you'll need to know should you want to write custom workflows for MOSS. Excellently covered and very informative and easy to follow - a must for a SharePoint developers bookshelf.

I have been creating workflows in SharePoint 2007 since early in the beta. The process is challenging and - at times - frustrating. David has done an excellent job providing the details and examples necessary for developers to be successful. You will find answers in this book that are not available from any other source.