When Alfresco released version 1.4, it made a huge leap forward in enterprise readiness. That was the release when Alfresco embedded the JBoss jBPM engine into the product, which meant that enterprises could route Alfresco repository content through complex business processes. Most content has some sort of process around it. That's why content repositories almost always have a mechanism to streamline, facilitate, and report against the business processes that produce, consume, or transform the content within them.

But before geeking out on the wonders of graph-based execution languages, let's agree on what the term workflow means. Generically, workflow is a reliably repeatable pattern of activity enabled by a systematic organization of resources...that can be documented and learned (http://en.wikipedia.org/wiki/Workflow). The term has been around since people started studying...