Steps to replicate the problem
- Create a custom list
- Go to http://yourfarm/yoursite/ and click on the Lists quick launch.
- Click on the Create button
- On the Create screen, select Filter By > List > Custom List
- Enter a Name for the Custom List (e.g. “TestWorkflow”
- Click on Create button
- You should now be in the list, with the List Tools > List ribbon showing.
- Click on the List Settings ribbon button.
- This should take you to the List Settings page
- Click on the Versioning Settings link
- In the Content Approval section, click on the Yes radio button for “Require content approval for submitted items”
- Click on the Workflow Settings link on the List Settings page
- It should take you to the Workflow Settings page
- It should say “There are no workflows currently associated with this list.”
- Click on the “Add a workflow” link
- Select the “Approval – SharePoint 2010” workflow template
- Enter a unique name for this workflow: “TestWorkflow Approval”
- Uncheck the “manually started” checkbox under Start Options
- Check the “Start this workflow when a new item is created” checkbox
- Click Next
- Insert a user login in the Approvers “Assign To” picker. I typically insert my own login for testing.
- Check the Enable Content Approval checkbox.
- Click Save
- Click the list name in the navigation at the top of the page to return to the list.
- Click Add new item
- Enter some text in the Title field.
- Click Save
- You now have a list item with a workflow.
- Click on the drop down contextual menu, which has View Item, Edit Item, Approve/Reject and other menu items
- Click on the Approve/Reject menu item
- The Approve/Reject dialog appears.
- Select Approved. Enter a comment.
- Click OK
- The Approval Status in the list says approved.
- Click on the Tasks link in the quick launch side bar
- Notice that the Task Status column says “Not Started”
So, when one views the list item, and attempts to approve or reject the item, it appears that it only sets the column in the list itself and has nothing to do with the actual workflow.
Is this intentional? It doesn't appear to be very useful - users get confused thinking they have approved a request and then wonder why the user or the next stage has not gotten an appropriate mail message.









