Johan Björnfot
Aug 18, 2011
visibility 8286
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
Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

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

Giving Optimizely 13 Content Types Meaningful Icons and Thumbnails

When working with an Optimizely CMS solution that has evolved over time, it is common to end up with many content types. As the number grows, the...

Pär Wissmark | Sep 16, 2026 |

force-dynamic vs connection() for Optimizely Graph

If you have built an Optimizely CMS SDK site, you already know getContentByPath on a catch-all. This post is about the part that file never says ou...

Chirag Khanna | Sep 16, 2026 |