Task Notification Mail only once/first assignment

Question

Hi, 
 A user task with notification setting enabled - sends mail when it reaches the node. 
 This user task has a Save button, which brings the control back to the same node in the process flow. Upson save, mail notification triggers again. 
 Tried activity chaining to avoid 2nd time notification upon save, but triggers mail. Is it possible to avoid this? 
 Note: I can have a split gateway and have a mail notification smart service and disable the automatic config. But wanted to check if there is any OOTB. 
 
 Any help/ideas are appreciated. 
 Thanks, Keerthi

Mike Schmitt · Accepted Answer

AFAIK what Chris said about chaining should be true. Otherwise, if push comes to shove, you could always duplicate the task node and have subsequent instances use the duplicate, on which you set the hardcoded configuration to disable the "send email" option. I know that's not very efficient (i don't understand why they've never set it up to be parameterized), but it's at least fairly easy to do.

Mike Schmitt · Answer

it would get a new Task Instance ID, but also, so would a re-launched copy of your original one if you only have a single copy of the task node (so basically no difference there in terms of reporting, as far as I can tell).

Task Notification Mail only once/first assignment

Top Replies