Updating List After Assign Multiple Assignee Task

Hi, you can use a "create an item" workflow step if you want to create a new SP list item or "Update items" workflow step to update an existing List item. To populate the item columns with your task form data, on the create/update SP step > on the column you want to update click on
1. +Insert

2. From the context menu you should see your task step name, click on it

3. "First response"

4. "Form variables"

5. Pick your Form field you want to update the SP item with

6. *Make sure to add a condition if you want to update a single SP list item

Hope this helps!

@KauaDorneles I have been trying to do this and it only updates the list once all responses have come in. Is there a way to get it to update as the responses come in?

If I assign a task to 2 people, and the first response is reject, I cannot see what their comment is until the second person replies with their response. I’d like to see their responses/comments as they come in.

Unfortunately, having the responses updated somewhere while they are coming in is impossible.
You can only run one action at a time, which in this case is the Task action.  As the task action does not have this feature, the solution cannot be achieved. The only way to achieve this is to have sequential tasks and pass on the comments from one task to the next.

Maybe I’m misunderstanding the problem here, but couldn’t this be achieved by using a Loop for each action, inside of which is a component workflow that runs concurrently with the parent workflow? Something like this:

1. In a form within the parent workflow, @bmat1962 uses a People field, set to accept multiple names, to enter the name(s) of those who need to be assigned the task.
2. A Loop for each action is used to loop through each person who was entered in the People field. Within this loop is a Call a workflow action to initiate a component workflow that runs concurrently with the parent workflow.
3. The child (component) workflow is where the task is assigned. This way each person is assigned the task individually. As they respond, the data is written to the SP list and @bmat1962 is notified (perhaps in an email that contains the desired data).

Can you share a screenshot of how this looks in Nintex?

Sure. I should state at the outset that I’m using Azure AD to obtain the users' information.

In a form (probably the initiating form of the workflow), use a People field that’s set to allow multiple selections:

At some point in here the item in the SharePoint list is to be created, and an output variable set for it. 

The next step is to insert a Loop for each action, using the collection of names from the People field:

The first action within the loop is optional (the above screenshot is from one of my actual workflows: I’m getting the full name of the selected employee and adding it to a collection). Then I use Azure AD to get all the AD details of the employee. Then the component workflow is called, passing over any data the component workflow needs to use, such as the employee’s email address (to assign the task in the component workflow) and the item ID of the SharePoint list entry (obtained from the SharePoint output variable mentioned above). In the Call a workflow action you want to keep the default setting that both workflows run concurrently. This way, all approvers are assigned the task at essentially the same time (because as soon as the component workflow is called, the loop circles back and goes to the next employee) and each can complete theirs individually.

Of course, the component workflow has to be built and published (at least to Development) before you can call it. The component workflow may contain many actions, but for the purposes of this example it must contain an Assign a task action. This task includes a form containing the data the approver needs to review, plus a place to approve/reject, enter comments, etc.

Once the approver submits the form, the SharePoint list is updated with an Update an item action. This action will (MUST) contain a condition that the item ID of the list equals the item ID that was passed over from the parent workflow. This, of course, ensures that the correct item, and only the correct item, is updated.

Then the component workflow notifies whoever needs to be notified (in this example, @bmat1962). This can be as simple as an email containing whatever this person needs to know (such as the approver’s comments).

I know I included only a couple of screenshots here. Please let me know if you have more questions.