Plumber extends Umbraco's publishing model to allow creation of flexible, multi-stage approval workflows. Plumber integrates with the Umbraco backoffice to add multi-stage approval processes for content changes, allowing organisations to adopt a distributed publishing model with full confidence the right people are approving content updates prior to publishing. Alternatively, keep the final approval stage centralised, as the final step of multi-departmental an approval process.
Along with the workflow mechanism, Plumber adds helpful dashboards for your editors, and a full-featured backoffice application, with detailed analytics, documentation and configuration options. Plumber provides three workflow flavours - direct, inherited and content-type. Workflow can be configured directly on a given node, inherited from a common ancestor, or set on all nodes of a given content type. In cases where a node has multiple workflows applied (ie set directly, but also set for the content type) the workflow engine determines the most appropriate workflow to apply.
Workflow types are only scratching the surface of Plumber's features, with a suite of useful features and configuration options mean your Plumber installation can be as simple (or as complex) as your individual needs dictate.
Show me the features!
Plumber stores all workflow history, and provides a searchable, faceted interface for exploration. Need to see the workflow history for a given node, or all cancelled tasks from the last fortnight? You're covered.
Plumber looks and feels like part of Umbraco. Editors use familiar buttons, in familiar locations, to manage workflow. Conditional stages: document-type approvals include conditional stages, where a workflow group can be included based on a property state - for example, include your SEO guy only when the metadata fields are updated.
Plumber adds helpful dashboards for users to show their pending and submitted workflow tasks. Admin users also see an overview of all pending tasks Document-type approvals: configure workflows to be applied to all nodes of a content type
It's right there, in the Umbraco backoffice, updated in real-time. Explore Plumber via backoffice tours.
Notify users via email when they have pending tasks, or when their submissions have progressed through a workflow.
Plumber emits a range of useful events for developers to integrate with other systems. Want to send SMS notifications? Go for it - simply subscribe to events using familiar Umbraco patterns.
Don't want site-wide workflow? Simply exclude branches of the content tree
Explicit or implicit flow types determine how the change author is included in the workflow - an explicit flow requires all groups in the workflow approve the change, even if the original editor is a member, while implicit skips such groups, removing the need for the editor approve their own work.
Lock active content:
Optionally permit editing of content in a workflow, or freeze edits until the current workflow completes. Admin users can always modify content in a workflow, with their actions noted in the workflow history
With a little configuration work, users can approve workflow tasks without logging in to the backoffice, allowing non-editors to participate in workflows.
Changes not quite up to scratch? Workflow tasks can be rejected and sent back to the original editor for revision. Re-submission returns to the rejecting stage, encouraging conversation and collaboration.
Need a 24-step workflow? Sure, Plumber got your back. Workflow groups: workflows are group rather than user-driven, making managing staffing or responsibility changes simple.
Rather than extending Umbraco's user groups, Plumber introduces its own group mechanism, keeping out of the way of Umbraco's out-of-the-box features. Workflow section: a new backoffice section provides workflow history, audit trails, logs, access to all settings and workflow group configuration