Oct 7, 2009
  12253
(0 votes)

Enabling the EPiServer CMS Workflows

EPiServer CMS 5 ships with four out of the box workflows; Parallel Approval, Sequential Approval, Ready for Translation, and Request for Feedback.

The workflows are disabled by default and can easily be enabled for a CMS site by un-commenting their definitions in web.config.

If the workflows have not been enabled yet, you will see a “There are no instances or tasks related to this page available” message on the “Workflow” tab and a “There are no workflow definitions available” message in the Action Window in Edit Mode.

image 

To enable the workflows…

Open web.config and uncomment the following snippet under configuration/episerver/workflowSettings/definitions:

<!--
      <definition
        name="Sequential Approval"
        description="A sequential approval workflow for pages"
        type="EPiServer.WorkflowFoundation.Workflows.SequentialApproval,EPiServer.WorkflowFoundation"/>
      <definition
        name="Parallel Approval"
        description="A paralell approval workflow for pages"
        type="EPiServer.WorkflowFoundation.Workflows.ParallelApproval,EPiServer.WorkflowFoundation"/>
      <definition
        name="Request for feedback"
        description="Assigns request for feedback tasks to users/roles"
        type="EPiServer.WorkflowFoundation.Workflows.RequestForFeedback,EPiServer.WorkflowFoundation"/>
      <definition
        name="Ready for translation"
        description="Assigns translation tasks to users/roles"
        type="EPiServer.WorkflowFoundation.Workflows.ReadyForTranslation,EPiServer.WorkflowFoundation"/>
-->

Once enabled, the EPiServer workflows can be started from the “Workflow” tab or the “Action Window” in Edit Mode.

image

Oct 07, 2009

Comments

Sep 21, 2010 10:32 AM

Hi

I have added the above section and added 4 of the default workflows to workflow section of the admin view. Is there any other steps are that are needed?

thanks

John Burns

Feb 2, 2011 02:16 PM

Hi!

I've done a brand new installation of the Episerver CMS 5 with the demo site and I could not find that code snippet in the web.config.

Is there something that I'm missing on?

thanks & regards

Noel Fernandes

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |

Forcing Lowercase URLs in Optimizely CMS During Auto-Translation

Learn how to fix uppercase and punctuation issues in Optimizely CMS 12 URL segments caused by LanguageManager auto-translation using a custom...

Stuart | Apr 2, 2026 |

Stott Robots Handler v7 for Optimizely CMS 13

Stott Robots Handler version 7 is now available for  Optimizely PaaS CMS 13 . This is includes updates to support the switch from a Site based...

Mark Stott | Apr 2, 2026