Not an out-of-the-box feature, no.
You can declare a process level datafield that acts as a flag. In the code behind the Server mail event test this flag before sending the mail. The first time the flag is tested, it would obviously not be set and the mail will be sent (and the flag set to - True). The second time around the flag will be set and the mail will not be sent.
Regards,
Ockert
Page 1 / 1
Hello,
I have an Infopath activity with a server mail event attached to it that informs the originator that an issue is being worked on. This activity can either go to a "finished" activity (End), or a "status update" activity that then loops back to the Infopath activity. However, when this "loop" path is taken it causes the server mail event to fire again and again each time.
Is there a way to specify that a certain event can only fire "once", thereby avoiding this loop/spam effect?
Thanks,
Jason
I have an Infopath activity with a server mail event attached to it that informs the originator that an issue is being worked on. This activity can either go to a "finished" activity (End), or a "status update" activity that then loops back to the Infopath activity. However, when this "loop" path is taken it causes the server mail event to fire again and again each time.
Is there a way to specify that a certain event can only fire "once", thereby avoiding this loop/spam effect?
Thanks,
Jason
Thanks for the tip. I went back and looked at the process, and did some tests, and it seems that these multiple e-mails are sent even when the loop route isn't taken in the process (i.e the server e-mail event fires 3 times even when the process path taken is linear). These three e-mails that are sent to the originator all have the exact date stamp. The mail event is called "status change e-mail" in the attached image.
It is probably because you've got 3 Destination Users declared on the 'Ticket Handling' Acitivity which will result in 3 instances of this Activity being instantiated - each containing its own 'Status Change Email' event.
You'll have to split this Activity in two - one Activity which contains the 2 server events with NO Destination users declared and on with the client event with the 3 Destination users declared.
Hope this helps,
Ockert
You'll have to split this Activity in two - one Activity which contains the 2 server events with NO Destination users declared and on with the client event with the 3 Destination users declared.
Hope this helps,
Ockert
That was exactly the issue, thanks! Once i redid it into two activities the problem went away.
Thanks,
Jason
Thanks,
Jason
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.