Lifecycle / Workflow
A lifecycle describes the states a content (or a business object) goes through during its existence: draft, under review, approved, published, archived. It sets the transitions allowed between those states, and what must happen at each one.
The workflow is the other side of the same mechanism: where a transition calls for a human decision, it sends a task. Lifecycle and workflow are therefore not configured separately: each lifecycle state can issue a task, and accepting or rejecting that task moves the content to the next state.
Transitions
A transition can be triggered directly by the user, from the Lifecycle menu of the content, or result from a workflow task. Each transition can carry actions (send a task, notify, transform the document, have it signed) and conditions that determine whether it is offered.
Tasks
A task hands a decision to a user or a group: approve a document, review it, sign it. Its recipients are named explicitly or computed from a metadata. It follows an acceptance rule (all recipients, a single one, or one per group) and can be delegated, typically when someone is away.
The course of a workflow is traceable end to end in the audit trail.
Going further
- Lifecycle · Workflow: the user side
- Lifecycles module · Workflow task module