Johan Björnfot
Aug 18, 2011
visibility 8138
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
Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |