Content Services allows more than one workflow engine.
The following figure shows the high‐level architecture for workflow.
You can design workflow definitions using a graphical workflow designer that supports BPMN 2.0 or write the XML BPMN 2.0 process definition directly using an XML editor. Many workflow editors support BPMN 2.0 but might not understand some of the features of Content Services workflow. We recommend the use of the Activiti eclipse designer plug‐in for Eclipse that is Content Services-aware.
You can deploy a workflow using the Content Services Workflow Console, or by using a Spring Bean.
Content Services process definitions can include JavaScript, and this in turn can access content models in the repository so that you can provide your own specialized tasks for a workflow and access their properties. Process definitions have script node access which allows you to access objects in the repository, such as documents and folders. Your workflow can access and modify document objects, for example marking documents as approved, or signed off.
Content Services allows you to access your own Java Classes through the delegate handler to support automation in your workflows. The following diagram shows these features: