In a skimpy 238 (including index etc) A5-ish pages, this book describes what workflow is about, using the example of life assurance, and explains the concepts of tasks, stages etc. It describes a notation. It then spends a lot of time discussing entity modelling.
I'm a techie, I wanted tips on how to design a workflow engine. The book claims to present a 'method', a large part of which is standard entity modelling, but really only sketches the outline of a method and a notation, you would have to fill in a lot of gaps. It will take considerable effort for me to work out the advantages of this notation over the standard Petri nets and state transition notations, the authors should have attempted to do this.
There are a few useful nuggets for me in two of the nine chapters, but I already had some idea of what workflow is and already know how to design a relational database, so I feel I didn't get my money's worth. I suppose the relevant bits may reward re-reading and turn out to be worth it.
However, if money is no object, or if you are a non-IT person wanting to buy a workflow system, then it's worth a look. Would be a very, very good book for a university library, though.