Skip to main content
Nintex Community Menu Bar

Using NWC ... building a workflow that includes an “Assign Task to Multiple Users” action.

 

I want to store to store the list of USERS with their email address in a SharePoint list.  That way users who participate in any given “group / task” assignments can be updated as needed without needing to modify the workflow in NWC.

 

So far, I have built a SharePoint list of usernames with email address; then successfully used a QUERY LIST action and LOOP action to extract the names in the list and build a TEXT variable of the email address list in typical email fashion (list separated by comma and/or semi-colon).

 

I then tested this dynamic TEXT variable using a SEND MAIL action in the workflow and the formatted text variable works great for sending messages from the workflow. 

 

But that same variable CANNOT be used for Task Assignments even though an email address is a viable data element when assigning a task.

 

Note: An email “GROUP” (distribution group) will not work for this scenario because we need to collect a distinct RESPONSE from each assigned user.

 

Has anyone else been able to accomplish this idea?

 

So far, I have built a SharePoint list of usernames with email address; then successfully used a QUERY LIST action and LOOP action to extract the names in the list and build a TEXT variable of the email address list in typical email fashion (list separated by comma and/or semi-colon).

Hi ​@TomBnm,
Are you using a comma or semi-colon?

The reason I ask is that the help files advise that for the send an email action you can use either but the assign a task to multiple users help files advises semi colons only. I haven’t tested this but it may be worth a try. If the issue persists I suggest contacting Nintex Support.

On a side note, you may want to look at using a Nintex table to store your reference data for better integration. https://help.nintex.com/en-US/nwc/Content/Dashboard/Data.htm

So far, I have built a SharePoint list of usernames with email address; then successfully used a QUERY LIST action and LOOP action to extract the names in the list and build a TEXT variable of the email address list in typical email fashion (list separated by comma and/or semi-colon).

Hi ​@TomBnm,
Are you using a comma or semi-colon?

The reason I ask is that the help files advise that for the send an email action you can use either but the assign a task to multiple users help files advises semi colons only. I haven’t tested this but it may be worth a try. If the issue persists I suggest contacting Nintex Support.

On a side note, you may want to look at using a Nintex table to store your reference data for better integration. https://help.nintex.com/en-US/nwc/Content/Dashboard/Data.htm

 

Thanks. I went back last evening and rebuilt the process using a semi-colon in the TEXT variable … and Yes, it was finally successful.

One observation … the “Assign Task...” ACTION in designer will still show an “Orange” indicator that it is not fully configured, but after the first test run it will clear that indicator.  I was also told by support to try and use a pure “Collection” object (which is the result you get with the QUERY list action).  I am going to try that as well and see if I can use that COLLECTION “as is” without needing to use a Loop and build a TEXT variable.

I will report back the results.

Final Update.

Confirmed today that a “Collection” works well as the source of “Assignee” for a Task assignment. (Thanks to Nintex Support)

 

Using the first step of “Query a List” (SharePoint), I used the same LOOP construct to go back through the results of that query and used an “Add to Collection” action to build a NEW collection which will just contain EMAIL address (or whatever field needed)

 

This new collection that is created inside this loop can then be used as the Source of ASSIGNEE(S) for a multi-user task assignment.

 

Result worked very well.

 

 

Reply


Sidebar Buttons
Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
Terms & ConditionsCookie Settings