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

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/

Ateeq pasha
Ateeq pasha 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
Opti ID overview

Opti ID allows you to log in once and switch between Optimizely products using Okta, Entra ID, or a local account. You can also manage all your use...

K Khan | Jul 26, 2024

Getting Started with Optimizely SaaS using Next.js Starter App - Extend a component - Part 3

This is the final part of our Optimizely SaaS CMS proof-of-concept (POC) blog series. In this post, we'll dive into extending a component within th...

Raghavendra Murthy | Jul 23, 2024 | Syndicated blog

Optimizely Graph – Faceting with Geta Categories

Overview As Optimizely Graph (and Content Cloud SaaS) makes its global debut, it is known that there are going to be some bugs and quirks. One of t...

Eric Markson | Jul 22, 2024 | Syndicated blog

Integration Bynder (DAM) with Optimizely

Bynder is a comprehensive digital asset management (DAM) platform that enables businesses to efficiently manage, store, organize, and share their...

Sanjay Kumar | Jul 22, 2024

Frontend Hosting for SaaS CMS Solutions

Introduction Now that CMS SaaS Core has gone into general availability, it is a good time to start discussing where to host the head. SaaS Core is...

Minesh Shah (Netcel) | Jul 20, 2024

Optimizely London Dev Meetup 11th July 2024

On 11th July 2024 in London Niteco and Netcel along with Optimizely ran the London Developer meetup. There was an great agenda of talks that we put...

Scott Reed | Jul 19, 2024