A common problem I see again and again on projects is the drama involved in getting a project document reviewed and approved. Typically signing off a document confirms that the document contents is correct and has been accepted, this can have commercial implications or be a formal stage gate in the project management process. Many organisations use a manual approval process, sending copies of the document around by email, or worse a printed copy that jumps from in-tray to in-tray which is incredibly inefficient and is nearly impossible to track the progress of. Therefore, anything that can be done to streamline the approval process should be considered.
Enter another great feature of SharePoint, workflows. Through the use of workflows, the whole approval process can be automated, storing the document centrally in SharePoint and sending tasks and associated email alerts to the various approvers and tracking the status automatically.
In this post, I am going to demonstrate how easy it is to use this workflow capability, specifically by attaching a document approval workflow to a document library that will kick off whenever a user publishes a major version of a document.
Firstly, check that the out of the box Workflow Feature has been turned on for the site collection you will be working in via Site Collection Admin > Site Collection Features.
Secondly, check that the versioning for the document library is set up and set to Major / Minor versioning via the Library Settings > Versioning setting.
Set up the workflow
Choose the document library you want to add the workflow to and select ‘Add a Workflow’ from the Workflow settings.
Select which content types for the document library you want the workflow to be applied to, if you are unsure of the content type, choose All.
SharePoint 2010 comes complete with a number of prebuilt workflows that users can choose from. Should these not meet your requirements, new workflows can easily be built using SharePoint Designer or Visual Studio. Luckily Document approvals are one of the out of the box workflows available, so choose ‘Approval – SharePoint 2010’.
Give the workflow a meaningful name in the name field which will be used to identify the workflow once it has been created. Workflows in SharePoint use Task lists to store the tasks assigned to people and also the workflow history, you have the option to choose which lists are used to store these tasks. Finally you need to decide on when the workflow will be started, in this example we are going to kick it off whenever a major version of the document is published, so choose the ‘Start this workflow to approve publishing a major version of an item’ option.
Next you will need to set up the workflow settings, including:
- who you want to approve the document;
- whether you want the approvers to approve it sequentially or in parallel;
- what information you want included in the task / email sent to them;
- how long you want the task assigned to them to last (Duration); and
- how you want the workflow to terminate.
Now the workflow has been set up and is ready to use.
Use the workflow
The workflow we added to the library will be kicked off when a user chooses to publish a major version of a document in the workflow enabled library.
The first step of the workflow will bring up a settings screen for the user to have a chance to update some the workflow settings like the approvers and text sent in the request.
On clicking ‘Start’, the workflow will generate the relevant tasks and assign them to the approvers, in this example, Amy Strande first, then Dan Jump. Amy will be assigned a task and receive an email alert linking to the task, like the one below.
Notice that the workflow task include a link to the document to review and details from anyone that has been involved in prior steps of the workflow. Amy can then choose to Approve or Reject the task or a few other options including reassigning to another person if relevant.
- Once the task is approved, the next task will be generated, in this case for Dan Jump, as seen below.
Once Dan approves the task, the workflow will be completed and the document will be approved.
Of course the real benefit of the workflow is that you have an status screen trail that will show you the status of the workflow at any time and once it’s completed, a full audit trail of when a document is approved, by whom and when, giving you an electronic sign off record for the document as can be seen below.
In addition, through the introduction of Visio Services in SharePoint 2010, the status of the workflow can also be seen visually which is a welcome addition.
As you can see, the process of adding a workflow to a document library is incredibly simple to configure, and once in place makes the process of approving a document very simple and streamlined. Through the workflow status screen the status of the approval can be seen at a glance, seeing who has approved the document , and more importantly, who hasn’t looked at it yet.
I challenge you to implement document workflows on your next project and not see an improvement in sign off times!