I have a Flexi task that is assigned to a SharePoint group. The users in the group got the email notification but they cannot respond to it.
When they go to the task they get: "You are not authorized to respond to this task."
Have I configured this wrong? Can you not assign a flexi task to a SharePoint group instead of user?
Solved! Go to Solution.
Now, when testing this in a different environment, tasks are being created and I guess immediately deleted?
For the sake of testing, I went to a different environment, made a new SharePoint group with a few test accounts and myself. I have a WF that assigns a task to that SharePoint group. I create an item on the list, all the notifications get fired off. Every one of the test users have a task that is deleted? I have a web part on a page on the same site that shows all the tasks assigned to current user. Immediately after making a new item on the list, each test user gets an item listed on that web part that says
I've verified that the same group has contribute to the site and the list. Then I added them directly when that didn't work.
trying to go to the task gives an "unexpected error". I checked the log file. All I get is the below:
|21:32.8||w3wp.exe (0x0C7C)||0x15EC||SharePoint Foundation||Topology||e5mc||Medium||WcfSendRequest: RemoteAddress: 'http://testserver:32840/f45065911ce14c3b8738e24984b30b28/BdcService.svc/http' Channel: 'Microsoft.SharePoint.BusinessData.SharedService.IBdcServiceApplication' Action: 'http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetCacheIn...' MessageId: 'urn:uuid:054c42a0-68ac-4b66-ae6b-24a648cd0d12'|
|21:32.8||w3wp.exe (0x12CC)||0x0F08||SharePoint Foundation||Topology||e5mb||Medium||WcfReceiveRequest: LocalAddress: 'http://testserver.fulldomain.com:32840/f45065911ce14c3b8738e24984b30b28/bdcservice.svc/http' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetCacheIn...' MessageId: 'urn:uuid:054c42a0-68ac-4b66-ae6b-24a648cd0d12'|
|21:32.8||w3wp.exe (0x12CC)||0x0F08||SharePoint Foundation||Micro Trace||uls4||Medium||Micro Trace Tags: 0 nasq,0 e5mb|
|21:32.8||w3wp.exe (0x12CC)||0x0F08||SharePoint Foundation||Monitoring||b4ly||Medium||Leaving Monitored Scope (ExecuteWcfServerOperation). Execution Time=1.193813672907|
Actually, I found another part that says the item does not exist.
11/13/2017 13:19:13.20 w3wp.exe (0x0C7C) 0x15EC SharePoint Foundation Runtime tkau Unexpected System.ArgumentException: Item does not exist. It may have been deleted by another user.
at Microsoft.SharePoint.SPList.GetItemById(String strId, Int32 id, String strRootFolder, Boolean cacheRowsetAndId, String strViewFields, Boolean bDatesInUtc, Boolean bExpandQuery)
at Nintex.Workflow.NWListWorkflowContext.get_WorkflowInstance() f18f2c9e-9980-c090-ac19-21621f0d3662
This is definitely a permissions issue. When I get the SharePoint group Full Control they can access the tasks. Why would contribute permissions not be enough though?
can you check the permissions on your tasks or main list that you haven't changed the
list settings > advanced settings > item-level permissions section...?
Yea, I realized Nintex had an issue with Flexi tasks when item-level permissions were set late yesterday. That's a fun little thing to work around.