Johan Björnfot
Aug 18, 2011
visibility 8315
star star star star star
(2 votes)

Source code for the CMS6R2 built in workflows

EPiServer CMS6 R2 is shipped with four built in workflows (the same workflows that has been shipped with CMS since version 5). The workflows that are built in are two variants of page approval workflows, on request for feedback workflow and one request for translation workflow.

We share the source code for the built in workflows both so partners can change the behavior of the workflows and also serve as an inspiration for your own implementations.

Here is the source code for the CMS 6R2 versions of the workflows.

In the old post where the CMS5 versions of the source code where shared there is also a document that describes how to deploy them to a site. That document is still valid except for some namespace changes.

Aug 18, 2011

Comments

Jeff Wallace
Jeff Wallace Aug 18, 2011 02:36 PM

Nice! Thanks for posting an update. :)

smithsson68@gmail.com
smithsson68@gmail.com Aug 18, 2011 04:37 PM

Just wanted to supplement this with a link to Mark Everard's blog where he shows you how to create custom workflows for EPiServer CMS:

http://www.markeverard.com/blog/2010/09/29/developing-a-custom-workflow-in-episerver-part-one/

Dec 11, 2012 08:10 AM

Hi,
Can you please let me know how to integrate the workflow in existing Episerver CMS R2.

Following things I Changed.
1) in EPiserver.config file.


name="Sequential Approval_New" description="A sequential approval workflow for pages _New" />

2) Uploaded Dll files in the bin folder.
3) Able to view the Workflow, but when triggering. getting the below error in start parameter.

Could not load the given control from/util/WorkflowsUI/WorkflowApprovalStart.ascx:Unknown server tag 'EPiServerWorkflow:History'.

Thanks in advance.


error Please login to comment.
Latest blogs
Connect Your AI Agents Directly to Optimizely CMS

Connect any AI agent to Optimizely CMS and Commerce via Epicweb Agent API, reusing CMS-aware tools, instructions, and permissions to automate SEO,...

Luc Gosso (MVP) | Oct 1, 2026 |

Why Your CMS 12 and CMS 13 Sites Can't Share a Graph Instance

If you're planning your Optimizely CMS 13

Adnan Zameer | Oct 1, 2026 |

Bulk Catalog Import in Optimizely Commerce. Part 1: Why the DTO API

Why bulk catalog writes in Optimizely Commerce belong on the DTO API rather than IContentRepository — measured 2.7-3.3x faster, and what it costs you.

Stanisław Szołkowski | Sep 30, 2026 |

I Put Claude in Charge of GitHub Copilot During an Optimizely Upgrade

How we used Claude to plan and review an Optimizely CMS 11 to CMS 12 migration while GitHub Copilot handled the code changes, including the...

Dom Reilly | Sep 29, 2026 |