Allow entry of SharePoint group and/or AAD Security group to Assignee field of Task Assignment actions of NWC.
Since this is critical and urgent that affects our NWC implementation, can you please consider the feature improvement?
We're currently using Nintex for Office365 and going to implement Nintex Workflow Cloud. Our current template with Nintex for Office365 is supporting SharePoint Group because the template is using start a task process action and the action is supporting a SharePoint Group in Participant field. This action have “Assign a task to each member within groups” option.
However in current NWC, we cannot enter a group to Assignee field of task assignment actions. It only allows entry of individual user(s).
We need it to be able to enter SharePoint Group in Assignee field in NWC as well.
ADMIN RESPONSE
Sep 7, 2022
This is now supported by the use of actions to retrieve relevant assignees, direct access to AD groups is something still be assessed.
This is critical to adoption of NWC, both onPrem and Nintex for o365 support task assignment to Sharepoint Groups. It would be impractical to a modify the WF everytime some joins/leaves the Sharepoint site.
We use multiple Sharepoint online groups to easily manager task assignment to teams of users.
looks like NWC is back on the shelf until there is an answer to this...
Due to the lack of SharePoint group support, I had to break down SharePoint group of approvers into group members by custom javascript of Nintex Forms classic form. But this workaround doesn't work for a group that contains more than 10 members now. This limitation is a severe problem for my customer who use workflow for technical review where the assignees are selected by a group of subject specific experts (>20 members). And my workflow design is complex and number of actions is over 200. These actions should be simplified by a single "Assign a task to multiple users".
Please consider lifting the upper limit of # of assignees for "Assign a task to multiple users" action. As of now, the max limit is 20. For example, a voting workflow application needs to involve more assignees in an enterprise group.
Additionally, the action should be able to canceled by "Nintex Workflow Cloud - Complete a task". As I explained in another idea;
as of now, Nintex Workflow Cloud connector actions can't process any tasks generated by "Assign a task to multiple users" action. It could be a problem in a case where an operator wants to terminate unanswered tasks without stopping a workflow instance.
-- update Dec.21th
By calling NWC API task v2 from Call Web Service action, I could query tasks generated by "Assign a task to multiple users".
To confirm to make sure I am communicating this correctly to customers. If there are 50 users in the AD group, and we call this proposed AD group method to retrieve the users for a AD group, will all 50 users be in the group to aprove the task? Or will the task action limited this to the first 10 or 20 returned users in something like alphabetical order?
It would also be great if users in the group could see the tasks under My Tasks.
It would be impractical to a modify the WF everytime some joins/leaves the Sharepoint site.
We use multiple Sharepoint online groups to easily manager task assignment to teams of users.
looks like NWC is back on the shelf until there is an answer to this...
Additionally, the action should be able to canceled by "Nintex Workflow Cloud - Complete a task". As I explained in another idea;
https://nintex.uservoice.com/forums/430063-5-nintex-workflow-cloud/suggestions/44307258-enable-action-nintex-workflow-cloud-get-tasks
as of now, Nintex Workflow Cloud connector actions can't process any tasks generated by "Assign a task to multiple users" action. It could be a problem in a case where an operator wants to terminate unanswered tasks without stopping a workflow instance.
--
update Dec.21th
By calling NWC API task v2 from Call Web Service action, I could query tasks generated by "Assign a task to multiple users".