Best Practice for BPM email Alerts?

We have a series of conditions in which we send Email alerts to various internal groups. We have done some of them in Standard Data Directives, and others in pre processing method directives. I am curious as to what everyone thinks is the most reliable way to make sure scenarios do not get through the filter and emails get missed.

Our most recent Alerts involves notifying various groups when credit memos are entered, based on the reason codes. These are set up as a pre process on Update, with a check for the reason code on the CHANGED row.

I’m sure the answer is probably “It depends”, But I am curious what others think.

:slight_smile:

My preference is to do it in a Method Directive unless it can’t be done any other way.
It gives me a bit more control on how and when something is done.

Of course, that does come with it’s own drawbacks, like every once in a while, you
may have to catch something in more than one place, so then you need to look whether
a data directive makes more sense.

Long winded way of saying I prefer method directives.

“Best” would be to have the emailing part be generic and in a Function that could be called from a variety of Method or Data directives which would pass the information to the Function. There have been a few examples but I can’t say I’ve done this myself.

We have many of the “old way” pre-Functions where the BPMs do all the work of sending the email. @klincecum covered that part in his reply.