Assign a task is used to assign an approval activity to a manager. We know the workflow works, because it works on some users, but not all. We have checked the AD groups and everything looks fine. I have also checked the individual user profiles in the SharePoint Admin centre and that all looks fine for the users in question. Is there anything else I haven't checked as to why this is not working? Thanks.
When you say it doesn't work - what actually happens? Do the users it doesn't work for have a value for manager in their profiles? Why don't you log in history list the value of the manager so you can see what is being pulled back for the flexi task? You could then use run if to assign only if manager is not blank?
Thanks for feedback. The issue is that nothing happens. I don’t get any error messages, it just looks like the workflow stops and doesn’t create the task for certain users. All the affect users have a ‘manager’ in their AD profile, and I can also see it in their SharePoint Users profile.
I think I have found the issue though. The list and workflow are situated in our root site, and I think some users have restricted permissions under that root site so the workflow fails because of a permissions issue. I have recreated the workflow under a subsite where everyone has edit rights and the workflow now works perfectly, so far.
Tim Riley | Operations Manager
2.2 / 394 Lane Cove Road,
Macquarie Park, NSW, 2113
<https://www.xcentral.com.au/our-blog> <http://www.linkedin.com/company/252977> <https://www.facebook.com/XCentral> <https://twitter.com/XCentralAU> <https://plus.google.com/103243803127970641586/posts>
t 1300 881 113 d +61 2 9098 3823 m +61 405 567 911
e email@example.com<mailto:firstname.lastname@example.org> w xcentral.com.au<https://www.xcentral.com.au/>
FINALIST: MICROSOFT GLOBAL SERVER PLATFORM PARTNER OF THE YEAR 2013
WINNER: MICROSOFT AUSTRALIA SMALL BUSINESS PARTNER OF THE YEAR 2013 & 2014
WINNER: MICROSOFT AUSTRALIA MANAGED SERVICE PARTNER OF THE YEAR 2015
You can try to impersionate your workflow.
Add an action set and put every workflow action in the action set und configure "Run as Workflow Owner".
After that publish the workflow as a site collection administrator and so you don't have to worry about permissions.
This is a good way to work around the permissions issue, but may need to scale it back. Depending what other actions are going on, you may want to limit it to only to task creation/assignment and any other actions that cause updates.
Hope this helps!
Only actions at the root path of the workflow will have the "Run as Workflow Owner" option. If you have an action in any branch, this option will not be available.