Take the community feedback survey now.

Johan Björnfot
Aug 18, 2011
  7623
(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.


Please login to comment.
Latest blogs
Get last run of a scheduled job in Optimizely CMS

Learn how to get the last execution time of a scheduled job in Optimizely CMS.

Tomas Hensrud Gulla | Sep 20, 2025 |

Replacement Language Settings

Hi, Today I would like to share my learnings about the Replacement Language option in Optimizely CMS and Commerce. Replacement language is used to...

Harinarayanan | Sep 20, 2025

Locating Blocks Stored in “For This Page” When Retiring Block Models

When maintaining a long-lived Optimizely CMS site, you’ll eventually need to deprecate block types. The usual approach is to remove the block class...

Pär Wissmark | Sep 19, 2025 |

World Login is Moving to Opti ID

Starting Wednesday, September 24th, (at 2:00 PM EST) world.optimizely.com will require Opti ID for all logins. This change brings World in line wit...

Satata Satez | Sep 19, 2025