Documentation Center

Types of workflow

Tridion Sites offers various ways of using workflow functionality, intended for different purposes.

Technically speaking, workflow always works the same: zero or more items traversing a Process. But to make workflow implementation easier, a number of additional workflow concepts have been introduced.

Bundle workflow
Bundle workflow makes it easy to assemble multiple content items, which may not be located in the same organizational item, in a container (the Bundle), and then put the entire container and its contents through workflow. Before the Bundle goes into workflow, users can add or remove items. Putting a Bundle in workflow is an explicit step, and depending on the Process Definition being used, it may still be possible to add or remove items even after the Process has started.
Task workflow
Tasks are intended to be lightweight Processes that can be started by end users for simple tasks to be performed. One Process Definition is designated as the Task Process, and Tridion Sites ships with a default Task Process that consists of only two Activities: one to perform the task, and one to review it. When a user creates a Task in one of the user interfaces, they cannot associate any content items with it.
Programmatic workflow
You can use the TOM.NET API or the Core Service to perform workflow operations from your custom code. This includes starting a Process and adding one or more items to it.
Classic editing workflow
For Components, Pages, Component Templates and Page Templates, classic 'editing workflow' as it existed prior to SDL Tridion 2013, is still supported. Unlike Bundle or Task workflow, which are explicitly started, editing workflow starts implicitly when a user creates or modifies items of these types (if there is a Process Association in place for them). Note that an item cannot be in editing workflow and Bundle workflow at the same time.