{"id":1747,"date":"2014-11-20T13:29:31","date_gmt":"2014-11-20T13:29:31","guid":{"rendered":"http:\/\/www.stuartroberts.net\/?p=1747"},"modified":"2014-11-20T13:29:31","modified_gmt":"2014-11-20T13:29:31","slug":"workflow-app-permissions","status":"publish","type":"post","link":"https:\/\/www.stuartroberts.net\/index.php\/2014\/11\/20\/workflow-app-permissions\/","title":{"rendered":"Workflow App Permissions"},"content":{"rendered":"

With the new 2013 workflows there are a few scenarios that can cause issues which may not be obvious to those coming from 2010. One such scenario is configuring list items to have Create and Edit access<\/em> set to Create items and edit items that were created by the user<\/em> and have a user who did not create the item initiate a 2013 workflow. By default, this will result in the workflow failing due to unauthorised access exceptions.<\/p>\n

Lets walk through the scenario in more detail.<\/p>\n

Start with creating a new custom list and then in SharePoint Designer, publish a simple List workflow to it.<\/p>\n

\"Publish<\/a><\/p>\n

As you can see, a very simple workflow \ud83d\ude42<\/p>\n

Configure the list to allow users to only edit items that they created.<\/p>\n

\"List<\/a>
\n
\nFor testing this scenario, configure the workflow to Allow this workflow to be manually started by an authenticated user with Edit Item permissions<\/em><\/p>\n

\"Workflow<\/a><\/p>\n

Create a new item and initiate the workflow. Assuming no errors in the workflow itself and it completes with no user interaction, i.e. no tasks, etc. the workflow will successfully run and finish.<\/p>\n

\"Successful<\/a><\/p>\n

As a different user, initiate the same workflow against the same list item.<\/p>\n

\"Failed<\/a><\/p>\n

This time, with the item being created by me and not SPDev Member, the workflow fails and is cancelled. Looking through the ULS logs, there are a few items that will help to indicate why. These include:<\/p>\n