A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More


Oct 7, 2009
  11890
(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
Looking back at Optimizely in 2025

Explore Optimizely's architectural shift in 2025, which removed coordination cost through a unified execution loop. Learn how agentic Opal AI and...

Andy Blyth | Dec 17, 2025 |

Cleaning Up Content Graph Webhooks in PaaS CMS: Scheduled Job

The Problem Bit of a niche issue, but we are building a headless solution where the presentation layer is hosted on Netlify, when in a regular...

Minesh Shah (Netcel) | Dec 17, 2025

A day in the life of an Optimizely OMVP - OptiGraphExtensions v2.0: Enhanced Search Control with Language Support and Synonym Slots

Supercharge your Optimizely Graph search experience with powerful new features for multilingual sites and fine-grained search tuning. As search...

Graham Carr | Dec 16, 2025

A day in the life of an Optimizely OMVP - Optimizely Opal: Specialized Agents, Workflows, and Tools Explained

The AI landscape in digital experience platforms has shifted dramatically. At Opticon 2025, Optimizely unveiled the next evolution of Optimizely Op...

Graham Carr | Dec 16, 2025

Optimizely CMS - Learning by Doing: EP09 - Create Hero, Breadcrumb's and Integrate SEO : Demo

  Episode 9  is Live!! The latest installment of my  Learning by Doing: Build Series  on  Optimizely Episode 9 CMS 12  is now available on YouTube!...

Ratish | Dec 15, 2025 |

Building simple Opal tools for product search and content creation

Optimizely Opal tools make it easy for AI agents to call your APIs – in this post we’ll build a small ASP.NET host that exposes two of them: one fo...

Pär Wissmark | Dec 13, 2025 |