I've noticed strange thing - when I put "Start a Task Process" in a loop (n-times), participants got n-emails with Task Assigned notification and n-1 emails with Task Canceled notification.
Settings for "Start a task process" are:
-"Assignment Behavior" set to "parallel (all at once)"
-"Assign a task to each member within groups" checked
-"Wait for task completion" unchecked
Example: I've got loop with 2 iterations (razy, dwazy) and I received 3 email - 2 with task notification (for "razy" and "dwazy" task) and 1 with task canceletion (for "razy" task).
Obviously task "razy" is canceled/deleted (no item on Workflow tasks list).
Solved! Go to Solution.
Hi! I have some additional questions to you:
How many approvers are indicated per each "start task action"?
What completion rule have you set? Wait for all approvals, first approves, etc...?
Hi Maciej Flis,
Please check this section in your Task configuration wizard.
- Assignee options
Bashya Rajan A
Maciej Flis frankly speaking I'm a bit confused I have imported your workflow, run it several times, even setting the "Due Date" and manipulating with the "Escalations".
When I use the "Assign a task" action I have always been receiving only the "razy" and "dwazy" emails, no cancellation (and unfortunately, no escalation emails...).
Now when I switched into "Start a task process" action and I assigned 2 users to it, I noticed also a weird behavior - like the Nintex is assigning the task only to one (random) person from the set and is automatically canceling the others:
I suppose this is related to the fact, that "Wait for task completion" is unchecked- notice, that if you have this checkbox marked, Nintex generates a task for each assignee, but once one approves, the other tasks are being removed. As in such configuration Nintex is not waiting I understands it is simply removing additional tasks leaving only the firs/ last one created.
The other thing I also noticed and this is it might be a bug (and possibly this is a reason why those "overdue" and "escalation" emails are not being send is the fact, that the "Date/Time" variable I'm setting, even though I have a proper TimeZone set in SharePoint Regional Settings is set to probably the timezone where the Nintex Workflow Service is hosted. For example, the "d" variable you created, in the workflow is set to ex. 11:00. However, when I log the value as a string it seems that it is set to 20:00 (8pm) and when I output it as ISO then I receive 18:00 (6pm) - dunno why
Possibly another reason why these "reminding" emails are not sent is again the fact, workflow is not paused until the approval is made and it get completed before then so like its... done
So anyway - I don't know if my investigations going to help you, but it seems it's working like designed. But I'm only suspecting why it does so.
That is exactly what I've done and investigated too.
Thank you for your commitment!
I've opened a ticket on Nintex Support. We had a live session where I showed and described those two issues (with "Start a task process" and "Assign a task" actions).
I waiting for information from Nintex evangelist