If the workflow hasn't gotten to that task, that new user will be included. But you are right, if it already hit the flexi-task they wouldn't be included. Now, if there is a user in the task that the new user would be replacing he could delegate his task to the new user. And that wouldn't change the workflow.
I do have dynamic approvers using the SharePoint List to query names and I've used SharePoint Groups also. But that isn't the scenario we are looking to address.
It issue is once Nintex hits the Flexi-Task Action, it will create the individual tasks for the approvers at that time. If the list of approvers is updated before that task is completed, SharePoint won't add them in the mix. I have the same issue with "Not wanting to restart workflows because it will resend emails and cancel old tasks and resend new tasks" and it causes confusion.
I didn't know about the OTB sharepoint workflows allow for in-process-approver changes. I will take a look at that and see if I can work of that or at least see how it works.
Exactly, and delegation wouldn't work here since its a new user. In delegation I will have to assign someone else's task to a new person. I was looking at the OOB workflow to see how it accomplished, when I add the approvers/reviewers, it adds the task to the workflow tasks list and associates the workflow ID automatically, I tried to do it with nintex and its content type, it doesn't associate the workflow and creates an orphan task. Not sure how to proceed. Will have to wait and see what support suggests.
Thanks for your help.
OK, but when it is ON the flexi task and if you add a user to the list, does it create a task for the newly added person? It doesn't work for me. If I add a person to the list before it reaches the flexitask it works fine. but the second it reaches the flexi task and the task notifications go out. It wouldn't send new task emails anymore for newly added users.
Got an update from Nintex Support., unfortunately its not possible which is troubling to me, as this should be better than OOB workflows.
Thank you for your patience. From our testing looks like there is currently no way to do this and no workaround is found at this time.
We have tried it with many of our "Task" actions and none of them will work in the way that you would like.
This feature has been requested already for our development team to take a look at. You may find it here with status as well as vote for it to be implemented.
(I have voted for this as well)