So far you've learned the definition of workflow, specifics around the jBPM engine, and how to deploy processes. But the discussion up to this point hasn't been specific to Alfresco. In Alfresco, web client users need to:
Start workflows
Add one or more pieces of content to a workflow ("Approve this piece of web content", for example)
Assign tasks to users and/or groups, and work with the tasks assigned to them
Provide process-specific metadata for a specific workflow such as due dates, priority, special processing instructions, or any other custom metadata you can think of
JBoss jBPM is just an engine—it is up to the application embedding the engine to expose the capabilities of the engine to the user interface. Alfresco's already done that work for you. Figuring out how to wire your custom workflows into the Alfresco web client UI is just a matter of following Alfresco's framework.
Alfresco uses the same mechanism to model workflow process data and the corresponding...