Skip to main content
keerthik0010
keerthik0010
February 4, 2025
Solved

Task Notification Mail only once/first assignment

  • February 4, 2025
  • 8 replies
  • 0 views

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

    Best answer by mikes0011

    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.

    8 replies

    gayatria0439
    gayatria0439
    February 4, 2025

    Hi [mention:02c3f606848545c78e557c59d3379722:e9ed411860ed4f2ba0265705b8793d05] , Can you show me your process? Alternatively, try handling this with a variable by assigning it a value or making it null. This way, if it hits a second time and the logic doesn't satisfy the condition, it should directly proceed to the end or save.

    csteward
    csteward
    February 4, 2025

    A second email notification should not be generated if chaining is configured correctly, even with "Notify task assignees of new task.." enabled.

    Can you share a snipped of your process model?

    keerthik0010
    keerthik0010Author
    February 5, 2025

    I have chaining already, but task gets closed and moves to my task list.

    peter.lewis
    peter.lewis
    Employee
    February 5, 2025

    Are you missing any chaining inside of the sub-process? Since that is a synchronous sub-process, you must also chain through all of the nodes within the sub-process to ensure the chain isn't broken.

    mikes0011
    mikes0011Answer
    Brainy
    February 4, 2025

    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.

      keerthik0010
      keerthik0010Author
      February 5, 2025

      But duplicated one would be a new task with new task ID right? For reports and task escalations, it impacts.

      mikes0011
      mikes0011
      Brainy
      February 5, 2025

      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).

      Terms & ConditionsAccessibility statement