Task Responder blank for Assign a Task to Multiple user not authenticated

Yeah so I've confirmed that we lose the responder context once they access the form in an "un-authenticated" task. You're correct that the task URLs are unique for each assigned user, however there's currently nothing that prevents someone else from completing the "un-authenticated" task if they were given that URL.

Would something like a "task assignee" property that could at least show who the task was originally assigned to as part of the output facilitate your use case?

@Gavin-Adams sounds good. I'll bring this up with the PM that manages tasks for NWC and see if the "Task Assignee" is something that we can include as part of the output.

@butlerj 

Well that was painful but I got a solution.

I need to create a client app ID/token as the get tasks v2 need app auth to filter by workflowinstanceID.

I was able to take this NWC v2 connector from the gallery

Connectors - Nintex Workflow Cloud API v2

I then updated the json to support the tasks v2 model and /workflows/v2 endpoint.

And then added that as a custom Xtension.

With the new model, I use the custom List tasks action,

the loop through the tasks,

then within that I loop the array task assignments.

Then filter to the task assignment where the status = complete.

Then I can get the task assignment assignee.

Would be lovely for the out of the box actions and the output from the assign a tasks to multiple users action to support this data output natively.

Thanks for looping me in @butlerj!

Hey @Gavin-Adams,

1. Out of the box Task actions for APIv2 - this is already in one of our team's backlog. I am glad you have found our Gallery connector, though.

2. I will look into adding "Task assignee" as a parameter of the Task output. Obviously, we will need some time as we have lots of Task updates coming up, but keep an eye out on our release notes!

Thanks