Catch 22 for Approval Workflow in SharePoint Designer

–I began blogging on this, and found someone else’s blogpost from Dec 2010 who also blogged on this exact topic.  Though I never saw his blog post prior to writing this, credit to Lars Nielson

I ran into an interesting dilemma while working on my most recent project.  The project involved a number of document libraries that required content approval as well as versioning.

The scope of work greatly limited the amount of customizations that could be made to SharePoint (i.e. building workflows in Visual Studio).

This introduced an interesting problem based on our initial game plan.  The workflow is basically a document goes through a change process and committee approvals before it is published.  End Users cannot see changes until an approved document is published.

The change process was the complicated piece to this because the organization had a number of variables within the process, so the only solution was to require each step in the workflow to be manually kicked off.

When I made it to the approval stage, we initially had content approval on in the libraries.  And here is where the catch 22 comes in, trying to set content approval status to Approved in a document library that requires a document to be checked out and content approval is on.

To set the content approval status from Designer, ok easy enough, there is an action for that….uh oh, the document must first be checked out.  ok, check out document, set approval status….uh oh, I get an error that says content approval status cannot be set while a document is checked out.

Catch 22.  Basically to set content approval status in designer, the document must be checked out, but content approval status cannot be changed while a document is checked out.

Possible work-around – We did not go this route, we basically turned off content approval, and used a workflow to notify approvals, and once approval was granted, a user would publish a major version of the document.  This was acceptable for this engagement.

I was going to explain the workaround here, but I ran across a blog post while getting my info together of someone who already documented it.  So in the spirit of giving credit where credit is due, Lars gets credit for this solution.  Lars Nielson blogged on this exact topic in late 2010.

The bottom line in this is that for highly complex workflows, you really need Visual Studio.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.