You have now seen how Alfresco leverages the embedded JBoss jBPM engine to provide advanced workflow capability. Let's take a look at how advanced workflows compare to basic workflows, so you can make good decisions about which one is more appropriate in a given situation.

Basic workflows are nice end-user tools. Basic workflows use folders and a "forward step/backward step" model to implement serial processes. When a piece of content is dropped in a folder, a rule is triggered that associates a forward step and a backward step (one or the other or both) with the content. These steps are tied to Alfresco actions such as Set a property or Move the content to a specified folder. End users can then click on the appropriate step for a given piece of content.

For example, suppose there are requirements for a simple submit-review-approve process in which content is submitted, then reviewed, and then approved or rejected. One way to implement this with basic workflows...